Open Bug 1326831 Opened 6 years ago Updated 2 years ago
Ctrl+A in contenteditable element doesn't work and breaks caret if I canceled loading of page
(Core :: DOM: Editor, defect, P5)
(Reporter: arni2033, Unassigned)
>>> My Info: Win7_64, Nightly 49, 32bit, ID 20160526082509 STR_1: 1. Open url  in a new tab 2. Type "ok.ru" in urlbar in tab from Step 1 3. Press Enter, then IMMEDIATELY Escape (to stay on the page with contenteditable) 4. Select text "test", drag it on the ~center of contenteditable element. 5. Click between "s" and "t" in "test" contenteditable 6. Type "a" 7. Press Ctrl+A (bonus) - there's already a bug, but it gets worse 8. Type "b" 9. Switch to another application (e.g. Notepad++), then back to Firefox 10. Type "c" 11. Press Shift+Right, then Delete key 12. Press Ctrl+A, press Del AR: 4. Caret disappears in contenteditable (OK, just like always. Actually, not OK...) 5. Caret appears in contenteditable [OK] 6. Letter "a" appears between "s" and "t" in "test" [OK] 7. No visible action [not ok] 8. No visible action [not ok] 9. No caret visible [not ok] 10. "c" appears in the beginning of text in contenteditable [not ok](because no caret was visible) 11. Next letter is selected and deleted, but no caret is visible after the letter is deleted 12. No visible action ER: Text editing should work in a normal way. More precisely: Steps 7,12: Text selection should work Steps 8,12: Text editing should work Steps 9-12: Caret should be visible Note: I often drag links from urlbar to contenteditable field on the most popular russian social network (which is also a Facebook clone), - site https://vk.com . So I see this bug happening. >  data:text/html,<span></span><div contenteditable>asdf zxcv asdf zxcv asdf zxcv</div><span></span><br>_ test _
6 years ago
Priority: -- → P3
2 years ago
Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.