Closed
Bug 1155933
Opened 10 years ago
Closed 7 months ago
Absolutely positioned children of contentEditable elements get a 'draggable' UI
Categories
(Core :: DOM: Editor, defect, P5)
Tracking
()
RESOLVED
FIXED
People
(Reporter: phurst, Unassigned)
References
Details
Attachments
(1 file)
|
135 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.118 Safari/537.36
Steps to reproduce:
Put an absolutely-positioned div inside a contentEditable div (testcase attached)
Actual results:
The element had a UI that made it look like it could be dragged and resized (though neither worked).
Expected results:
It should use the usual contentEditable UI that it'd get if it was positioned normally.
Comment 1•4 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
Comment 2•7 months ago
|
||
It's hard to tell what the problem was here, with no screenshots, but I don't see any unusual UI in the test case. This might be resolved.
Flags: needinfo?(sefeng)
Comment 3•7 months ago
|
||
Yeah, agreed that it's hard to tell what the problem was here.
I think we can just close this.
Status: UNCONFIRMED → RESOLVED
Closed: 7 months ago
Flags: needinfo?(sefeng)
Resolution: --- → INVALID
Comment 4•7 months ago
|
||
Ah, the reporter must have reported about the legacy Gecko specific UI for absolutely positioned elements. Currently, it's disabled by default (web apps can enable it with execCommand). Therefore, this should not be a problem for normal web apps.
Depends on: 1449564
Resolution: INVALID → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•