52672 - Arrow up/down can move cursor to left/right as well.

Status: VERIFIED DUPLICATE of bug 51136

(Core :: DOM: Selection, defect, P3)

Description

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Not sure of the component, but it was suggested this might be bug for mjudge...

To reproduce:

1. Open a page that has multiline text field, for example the page for this bug.
2. Type/pase in the field at lest 3 lines of text, for example:
Some text
Other prose
Third line
3. Place the cursor somewhere in the middle line.
4. Press arrow up/down

Result:
The cursor will move up/down, and also right.

Expected results:
When you press the up/down arrows in a multile text field, the expected result 
is that the cursor moves one line up/down, but does not move sideways.

If you then press the arrow key to the opposite direction, it moves as it 
should. For example, if you do: DOWN (see bug), UP, DOWN, UP, DOWN,... you see 
the bug only during the first key press.

Now, if you take selection into this picture, we can move even more sideways (in 
the above cases you should see a movement of only one character). If you select 
text with keyboard (holding down the shift), you can move a lot more sideways. 
For example:

1. Place cursor on the middle line, between "t" and "h".
2. Holding down shift, press RIGHT arrow 2 times (you have selected "he")
3. Press UP (selection cleared, cursor moves to the beginning of the selection)
4. Press UP again

Result:
Cursor moves onto the first line, into the beginning of the word "text". It 
stepped 3 characters to the right.

You can try different combinations of selection direction and up/down arrow. For 
example, if you select from right to left, press down, press down, you will move 
down and left.

Comment 1

[anthonyd]

I can reproduce this, and while its probably an easy fix (PeekOffset is the most 
probably culprit), this is still being futured.

anthonyd

Comment 2

[Kathleen :Brade]

is this a duplicate of #51136?

Comment 3

[Kathleen :Brade]

I think this is a duplicate of #51136 (which has now been fixed)


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

Comment 4

[Blake Ross]

verified.