Active state isn't set when mousedown content is editable
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
People
(Reporter: masayuki, Unassigned)
References
()
Details
(Keywords: parity-chrome, parity-safari)
Attachments
(1 file)
|
276 bytes,
text/html
|
Details |
We don't set active state to editable content and its ancestors.
https://searchfox.org/mozilla-central/rev/e0eb861a187f0bb6d994228f2e0e49b2c9ee455e/dom/events/EventStateManager.cpp#5455-5462
However, the other browsers do. So, perhaps, we should take same behavior for web-compat.
Note that this was done in bug 924087 to make links non-interactive. But according to bug 924087 comment 5, Blink/WebKit have changed their behavior in this 6 years.
https://jsfiddle.net/d_toybox/43rufdb7/3/
In this testcase, "+" is non-editable button created with a <span> element (it's same as anonymous buttons of built-in UI of our editor). When you mousedown on them, it and ancestors are activated, but when you mousedown around the button and in the second or third <div> (they are editable), it does not cause them activated.
|
Reporter | |
Comment 1•5 years ago
|
||
emilio: This must be more important for web-compat of layout than DOM. So, could you set proper priority and severity?
|
||
Comment 2•5 years ago
|
||
It seems the blink behavior is more subtle. They only skip matching editable links as :active or something, see the incoming test-case.
|
|
||
Comment 3•5 years ago
|
||
Description
•