On 2009-09-14, at 18:48, Henry Minsky wrote:
On Mon, Sep 14, 2009 at 6:41 PM, P T Withington <[email protected]> wrote:
That rules out my theory that it is the change from INPUT to
TEXTAREA, but
there must be some skew between what the inputsprite does for an
INPUT vs.
TEXTAREA when it creates them. If you recall, earlier when the
cursor was
wrong for single-line input's, it was right for multiline. Now it
seems we
have fixed single and broken multi?
Question: Why do we use two different DOM elements? Can't we have a
TEXTAREA that is only 1-line high?
If you have a one line high textarea, can you make it so that when
the user
enters a newline that
it is ignored, or asking another way is there a way to restrict a
text area
to a maximum of one
line of input?
Oh, right. I don't know. Maybe that's why.
But, I guess I'd compare the setup for INPUT and TEXTAREA in the
sprite and look for differences that could explain the lossage.
