Open
Bug 903976
Opened 12 years ago
Updated 4 years ago
Caret position for up/down caret movement between lines is not as per the OS text editor's behavior.
Categories
(Core :: DOM: Editor, defect, P5)
Tracking
()
NEW
People
(Reporter: arpitabahuguna, Unassigned)
Details
Attachments
(1 file)
|
119 bytes,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212
Steps to reproduce:
Load the attached testcase editingBehavior.html.
Place the caret anywhere on the second line but not at the beginning of the second line.
Press the "up" arrow key. Caret moves to the first line, offset by an amount equivalent to the start position's offset on the second line.
Next, press the "up" arrow key again. Caret moves to the start of the first line.
Now, press the "down" arrow key.
Actual results:
Caret moves to the start of the second line.
This behavior is not in accordance with the default text editor behavior on various platforms such as mac, windows and linux.
Expected results:
The default text editor behavior on these platforms is to maintain the 'x' co-ordinate of the starting caret position and when the "down" arrow key is pressed, the caret goes back to its original/start position on the second line.
Pressing the down arrow key further would move the caret to the following lines while still maintaining the 'x' co-ord value.
Moving the caret to the 'start' of the line by pressing the "up" arrow key (when further lines are not available in the upward direction) and vice versa, should not reset the 'x' of the start position.
Even on the text editors on linux, mac and windows, similar behavior is observed and the browser too should behave in accordance with the default OS behavior.
WebKit based browsers do follow the OS behavior and thus work correctly for this scenario.
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Component: Untriaged → Editor
Ever confirmed: true
Product: Firefox → Core
Comment 1•5 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•