19405 - Text Areas improperly handle hard returns

Status: VERIFIED DUPLICATE of bug 16715

(Core :: Layout: Form Controls, defect, P3)

Description

[Igor]

Overview Description: When typing in a text box such as this one, if the user
types a hard return at the end of a line it does not return to the next line but
requires a second hard return to go to the next line.  When the user begins
typing on the next line after two hard returns the line suddenly moves down one
after which the user needs to hit backspace to delete one of the extra
backspaces or else have an extra.

Steps to Reproduce:
1)open the bugzilla URL above.
2)Click in the Description area and begin typing.
3)After typing a few words hit <ENTER>
4)Hit <ENTER> again.
5)Begin typing.

Actual Results:  The first <ENTER> does not forward the cursor to the next line.
 but for some reason leaves it on the current line but somehow inserts a
carraige return line feed after the cursor.  Hitting return again moves the
cursor to the next line.  When the user begins typing the text is inserted after
both of the hard returns.  The result is not a what you see is what you get.
Two hard returns are entered though the cursor only moves as if one had been
inserted.  When the user begins to type the cursor finally moves to the proper
position at the end of the two hard returns and the user has to delete one of them.

Expected Results:  The cursor should move with the hard returns.  When a hard
return is inserted by pressing <ENTER> in step 3 the cursor should move to the
next line.

Build Date: 11/18/99  Red Hat Linux 2.2.12-20

Additional Information:  It seems that the main problem is that the cursor on
the screen is just not getting moved after the first <ENTER> though internally
it seems to be, so that after the second hard return when the user starts typing
the internal cursor location determines where the text should be inserted so it
is inserted after both hard returns though the user only sees that the cursor
has moved one line for two hard returns.

Comment 1

[karnaze (gone)]

Reassigning to Steve.

Comment 2

[Sean Richardson]

This looks like a DUPLICATE of bug 16715, "[DOGFOOD] Do not see blinking or
still cursor after hitting the Enter/Return key", [PDT+], REOPENED, currently
being worked on, fix due any day now.

To confirm: type *anything but* another <ENTER> after the first <ENTER>;
if it shows up on the next line, that's 16715.

Comment 3

[rubydoo123]

Kin -- I believe that you are already working on this

Comment 4

[rubydoo123]

reassigning to jfrancis

Comment 5

[leger]

Setting QA Contact.

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

*** Bug 18976 has been marked as a duplicate of this bug. ***

Comment 7

[Joe Francis]

dup of 16715


*** This bug has been marked as a duplicate of 16715 ***

Comment 8

[Myk Melez [:myk] [@mykmelez]]

[VerifyDay] Marking this verified duplicate of 16715.  Bug 19324 is also a
duplicate of this bug (despite being marked as a duplicate of bug 10683).