Open
Bug 1210568
Opened 9 years ago
Updated 3 years ago
With contentEditable, setting cursor position with range/selection fails
Categories
(Core :: DOM: Editor, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: ilkkah, Unassigned)
Details
Attachments
(1 file)
2.11 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2520.0 Safari/537.36 Steps to reproduce: 1. Click "Title..." 2. Press "key down" 3. The cursor should jump to the first paragraph. 4. Actually it does, but something is wrong: try to type something and you will see. 5. Press "key up". The cursor jumps back to title which it shouldn't do. Actual results: Typing into paragraph produces weird results. The cursor is "stuck" in position 0. Expected results: Typing should be normal (like it is in Chrome).
Comment 1•9 years ago
|
||
This is not a recent regression. At least I can reproduce the behavior on Firefox3.6. Chrome's behavior also differs from IE's. FYI, It works as expected(like IE and Edge) if add |article.focus();| to function setCursorAtArticle. function setCursorAtArticle() { article.focus(); ...
Component: Untriaged → Editor
Product: Firefox → Core
Reporter | ||
Comment 2•9 years ago
|
||
Thanks for the work around. Though, it doesn't do quite the same thing as range/selection as the input seems to go to straight under article, while the range/selection places the cursor in the first paragraph (or anywhere one needs to place it). So at this point my work around is to disable the behavior for Firefox, by looking at navigator object.
Comment 3•3 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
•