TextArea with grow sizes incorrectly based on the value of the TextArea

[jared.rodriguez]

If the user types something into the text area that has a tag that can render as HTML, then the sizer is all screwy.

For instance, the user types the following into the text area:

I am < Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus aliquet accumsan nunc, eget luctus arcu aliquam sit amet. Etiam feugiat quam eget nisi fringilla at fringilla neque consequat. Proin nisl nisl, rutrum ut cursus consequat, posuere quis lorem. Donec massa ligula, tempus quis placerat vel, bibendum a ligula. Sed nibh nulla, fermentum at fringilla eu, molestie vel nulla. Sed quam justo, auctor eget hendrerit et, mollis et libero. Duis ac ipsum mi, ac malesuada neque. but am > 7

Then only 7 characters are processed for length as everything between the < and > are ignored.

A good fix would be to change Ext.layout.component.field.TextArea where it pulls the value from the input element. That value is already processed by the adjustForGrow routine to replace line feeds with <br/>. Additional processing to replace the < and > characters would fix the problem.

[mitchellsimoens]

What Ext JS 4 version are you seeing this in and what browser? Just tested in Chrome with out latest code and the textarea grows as expected.

[jkennedy]

EXT 4.0.7 and Chrome 16.0.912.77

It depends what you type to get the grow to not work. If you have a bunch of text within a <> then it will not grow appropriately. My example might have been off, the content between the <> in my case has no white space, which could make the difference.

[mitchellsimoens]

This produced this bug:

I am <Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus aliquet accumsan nunc, eget luctus arcu aliquam sit amet. Etiam feugiat quam eget nisi fringilla at fringilla neque consequat. Proin nisl nisl, rutrum ut cursus consequat, posuere quis lorem. Donec massa ligula, tempus quis placerat vel, bibendum a ligula. Sed nibh nulla, fermentum at fringilla eu, molestie vel nulla. Sed quam justo, auctor eget hendrerit et, mollis et libero. Duis ac ipsum mi, ac malesuada neque. but am> 7

[evant]

I can see how that makes sense. It sends the text off to TextMetrics to measure it, which could cause problems if the markup is invalid.

[jared.rodriguez]

My fix was to add the following lines to Ext.layout.component.field.TextArea


value = value.replace (/</g, '_');
value = value.replace (/>/g, '_');

I put them right before the existing line of:


value = value.replace(/\n/g, '<br>');