65933 - moving between lines causes insertion point to end up at the end of the line

Status: VERIFIED DUPLICATE of bug 51136

(Core :: DOM: Editor, defect)

Description

[Joseph Wang]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.0-2mdk i586; en-US; m18) Gecko/20010118
BuildID:    2001011821

The insertion mark always seems to end up in the wrong place
in the previous or next line if I move the mark up and down
with the arrow keys.

Reproducible: Always
Steps to Reproduce:
Type in several lines of text into a form text box.
Then move the cursor in the middle of one of the lines.
Hit the up or down arrow.



Actual Results:  One would expect that in moving between lines that the insertion
mark would stay in the same relative position in each line, but it
doesn't.

There seems to be a variable that isn't getting cleared properly.
I start a line and type

mark

then up arrow and the insertion mark ends up four characters from
the end of the previous line.  I go back and backspace over mark
and retype it, press up arrow and the mark ends up eight characters
from the end of the previous line.  Do it again and it ends up
twelve characters.

Expected Results:  If I am between the third and fourth characters of a line and I
press up or down arrow, I should stay between the third and
fourth characters of a line.

Seems to have appearred just now.  Didn't see this in previous builds.

Comment 1

[Stephan Niemz]

Confirming with build 2001011820 on NT4, although I see this somewhat different:

Type several lines in a textarea form field, like the additional comments on
this page.  Move the cursor in the middle of one line.  Press cursor up or down.

Expected: cursor is in the same column one line above or below, respectively.
Actual: cursor moves also one position to the right.

This only happens when pressing up or down for the first time.  On subsequent
up or down key strokes, the cursor stays in the same column as I would expect.
After moving the cursor by some other means (right, left, entering some text,
mouse) and hitting up or down again, the weird behaviour returns.

Comment 2

[Blake Ross]

pretty sure this is a dup
-> sfraser

Comment 3

[janne hayrynen]

probably a dup of bug 51136

Comment 4

[Simon Fraser [no longer active]]

-> anthonyd

Comment 5

[Stephan Niemz]

Yes, probably a dup of bug 51136, although I don't get the behaviour described
there. But Mozilla does it wrong anyway.

Comment 6

[Stephan Niemz]

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

Comment 7

[Kathleen :Brade]

I agree; I think this is a duplicate


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

Comment 8

[sujay]

verified in 1/22 build.