Disabled fieldset should not stop event propagation
Categories
(Core :: DOM: Events, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox116 | --- | fixed |
People
(Reporter: turand, Assigned: saschanaz)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0
Steps to reproduce:
This is the same bug, that I has been fixed in chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1422547
(1) open the codepen: https://jsfiddle.net/vxr45h3c/
(2) click RUN
(3) click disabled - click me
Actual results:
Nothing - no alert is shown.
Expected results:
The event should be propagated up to the document -> alert should be show.
Fieldset elements themselves aren't actually supposed to be disabled
form controls, they are just supposed to make their descendant field
control elements disabled:
https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#concept-fe-disabled
Comment 1•1 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: Events' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 years ago
|
||
Looks Kagami has been on this issue already.
Assignee | ||
Comment 3•1 years ago
|
||
I think I'll wait until it reaches the Chrome stable channel to see if the approach is web compatible. I hope that makes sense.
Reporter | ||
Comment 6•1 years ago
|
||
@K(In reply to Kagami [:saschanaz] from comment #3)
I think I'll wait until it reaches the Chrome stable channel to see if the approach is web compatible. I hope that makes sense.
I reported this to Chromium as soon as they have broken it recently in stable channel. The requested behavior is original behavior of chromium, so it is "Web compatible"
Assignee | ||
Comment 7•1 years ago
|
||
The thing is that Blink is experimenting to change their general disabled form element behavior. If they decide the whole approach is not web-compatible then we'll need to discuss more and may need to implement some other approach. So I'd like to see the conclusion before doing something here.
That said, I think fixing this specific issue would be simple enough and probably shouldn't be affected even if we decide to try some other approach. A patch will be welcome.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 8•1 year ago
|
||
At this point both WebKit TP and Chrome stable have this, we can make the change with reasonable confidence.
Assignee | ||
Comment 9•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 10•1 year ago
|
||
Comment 12•1 year ago
|
||
Backed out for fieldset related mochitest failures.
Failure logs:
- https://treeherder.mozilla.org/logviewer?job_id=419118898&repo=autoland
- https://treeherder.mozilla.org/logviewer?job_id=419119290&repo=autoland
Backout link: https://hg.mozilla.org/integration/autoland/rev/f883b9662835d8b740f8ae5174e3c4a82ab448f3
Comment 14•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 15•1 year ago
|
||
Oh no, forgot to enable dom.forms.fieldset_disable_only_descendants.enabled
for tests to prevent beta simulation failure.
Assignee | ||
Comment 16•1 year ago
|
||
Comment 17•1 year ago
|
||
Comment 18•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/fbc03cb5c0eb
https://hg.mozilla.org/mozilla-central/rev/bdbd72f04035
Description
•