It would be swell to just use TEXTAREA if we could manage it somehow... <br><br><div class="gmail_quote">On Mon, Sep 14, 2009 at 7:08 PM, P T Withington <span dir="ltr"><<a href="mailto:ptw@pobox.com">ptw@pobox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On 2009-09-14, at 18:48, Henry Minsky wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, Sep 14, 2009 at 6:41 PM, P T Withington <<a href="mailto:ptw@pobox.com" target="_blank">ptw@pobox.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
That rules out my theory that it is the change from INPUT to TEXTAREA, but<br>
there must be some skew between what the inputsprite does for an INPUT vs.<br>
TEXTAREA when it creates them. If you recall, earlier when the cursor was<br>
wrong for single-line input's, it was right for multiline. Now it seems we<br>
have fixed single and broken multi?<br>
<br>
Question: Why do we use two different DOM elements? Can't we have a<br>
TEXTAREA that is only 1-line high?<br>
</blockquote>
<br>
<br>
If you have a one line high textarea, can you make it so that when the user<br>
enters a newline that<br>
it is ignored, or asking another way is there a way to restrict a text area<br>
to a maximum of one<br>
line of input?<br>
</blockquote>
<br></div>
Oh, right. I don't know. Maybe that's why.<br>
<br>
But, I guess I'd compare the setup for INPUT and TEXTAREA in the sprite and look for differences that could explain the lossage.<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Henry Minsky<br>Software Architect<br><a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com</a><br><br><br>