Open
Bug 1349292
Opened 7 years ago
Updated 2 years ago
In a contenteditable document, button element doesn't work as it should.
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
NEW
People
(Reporter: email, Unassigned)
Details
(Keywords: testcase-wanted)
Attachments
(1 file)
2.44 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce: Created a Button element in a contenteditable document. Actual results: The Button element is not editable - even enclosing it in a Span with contenteditable="false", and setting the Button itself to contenteditable="true" only made it partially editable - the problem being that images or spans within the Button element weren't correctly detected (event.target always returns Button, even if you click on an image or span). Expected results: It should work like in every other modern web browser and be genuinely editable.
Could you provide a testcase, please.
Component: Untriaged → Editor
Flags: needinfo?(email)
Keywords: testcase-wanted
Product: Firefox → Core
Reporter | ||
Comment 2•7 years ago
|
||
Images in attached file won't work... But concentrate on the Button element: It mostly works (but only if contained within a Span with contenteditable="false" - try removing the Span!!) BUT - even if you click on the span inside the Button, event.target returns 'Button' - images are similarly not recognised, if you can introduce one. Many thanks Tony
Flags: needinfo?(email)
Comment 3•7 years ago
|
||
Although the behavior is different to Blink, I cannot find spec for correct behavior. This seems to be event target. If this should handle editor, you can back to editor.
Component: Editor → DOM: Events
Comment 4•7 years ago
|
||
Stone, can you determine where we're going wrong here (if we are)? Thanks!
Flags: needinfo?(sshih)
Comment 5•7 years ago
|
||
Looks like we didn't support 'contenteditable' for button element. Did hit test and always got the button element as the event target.
Flags: needinfo?(sshih)
Comment 6•7 years ago
|
||
(In reply to Ming-Chou Shih [:stone] from comment #5) > Looks like we didn't support 'contenteditable' for button element. Did hit > test and always got the button element as the event target. Can't find the spec says that button element does not support contenteditable and can't find the spec says the children of button element are anonymous to users neither. Also tested it on Edge and it behaved the same as Chrome.
Comment 7•7 years ago
|
||
(In reply to Ming-Chou Shih [:stone] from comment #6) > (In reply to Ming-Chou Shih [:stone] from comment #5) > > Looks like we didn't support 'contenteditable' for button element. Did hit > > test and always got the button element as the event target. > > Can't find the spec says that button element does not support > contenteditable and can't find the spec says the children of button element > are anonymous to users neither. Maybe Anne can help?
Flags: needinfo?(annevk)
Comment 8•7 years ago
|
||
Hit testing is bug 1089326. For contenteditable I recommend we try to match the other browsers (or at least a majority of them). There's some standardization effort going on, but it's not based on thousands of tests so I'm not convinced it's going to be very useful.
Flags: needinfo?(annevk)
Comment 9•7 years ago
|
||
(In reply to Anne (:annevk) from comment #8) > > For contenteditable I recommend we try to match the other browsers So this is more of a Core::Editor thing?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(annevk)
Priority: -- → P2
Updated•7 years ago
|
Component: DOM: Events → Editor
Flags: needinfo?(annevk)
Comment 10•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•