Open
Bug 1137686
Opened 9 years ago
Updated 3 years ago
Erratic behavior of the programmatic API in some situations
Categories
(Core :: DOM: Selection, defect, P5)
Tracking
()
NEW
People
(Reporter: julienw, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(1 file)
1.73 KB,
text/html
|
Details |
STR: 1. load the attachment 2 [review]. click the button "focus after iframe" and notice it works fine. 3. click in the editable element, in the text 4. click the button "focus after iframe" and notice it still works fine. 5. click in the editable element, in the text 6. press "home" to put the cursor at the start of the line 7. click the button "focus after iframe" and notice the cursor does not move => KO Note that if we use the button "focus just before text" instead of pressing home at step 6, then it works fine. However, if we use this button before "focus after iframe" at step 7, then it doesn't work either. That means a wrong state is likely set when moving the cursor manually compared to when we move the cursor programmatically. Note that we'd need this in the SMS/MMS application in B2G, when editing messages with attachments, to properly control when an attachment is deleted by the user (bug 991835).
Reporter | ||
Comment 1•9 years ago
|
||
Comment 2•3 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.
If you have reason to believe this is wrong (especially for the severity), 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
•