Ctrl+up/down does not work properly in contentEditable on Windows
Reported by
syed.ali...@pearson.com,
Sep 8 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.14 Safari/537.36 Steps to reproduce the problem: On windows platform, open simple html page containing the following content with firefox, <!DOCTYPE html> <html lang="en"> <head> </head> <body> <h2>Content Editable</h2> <div style="width: 500px; height: 250px; border: 1px solid black" contenteditable="true"> This is the first paragraph. (paragraph 1). <br/>This is the second paragraph. (paragraph 2). </div> </body> </html> move the cursor to the end of paragraph 2 and press ctrl+up , similarly move the cursor to the beginning of paragraph 1 and press ctrl+down What is the expected behavior? ctrl+up should move cursor to the beginning of the current paragraph and subsequently to the beginning of each of the previous paragraphs, whilst ctrl+down should always move to the beginning of the next paragraph. For comparison start Word Pad , enter the same paragraph and navigate through the same key combination . What went wrong? Observe that the caret does not move to the start of the previous and the start of the next paragraphs as it should, but it moves to seemingly random positions within the previous and next paragraphs. Did this work before? No Chrome version: 54.0.2840.14 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Sep 9 2016
Able to reproduce the issue and is a non regression since seeing this behavior on chrome from version 35.0.1849.0 for Windows 10. Previous versions of chrome do not move cursor when used cntrl+up or cntrl+down. Issue is also seen on MAC (Cmd+Up & cmd+down) and Ubuntu OS. Untriaging it so that it gets addressed and removing bisect label. Thanks.!
,
Sep 9 2016
,
Sep 12 2016
Sample: https://jsfiddle.net/0wnah5t1/ Note: Edge and Firefox doesn't support "paragraph" granularity for Selection#modify()
,
Sep 29 2016
Hi, yosin, can you assign this bug to someone, fixing this issue is of vital importance to our project
,
Sep 29 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 3 2017
,
Oct 3
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ligim...@chromium.org
, Sep 8 2016