Open
Bug 1459231
Opened 6 years ago
Updated 4 months ago
[meta] Follow the spec better regarding activation behavior
Categories
(Core :: DOM: Events, enhancement, P2)
Core
DOM: Events
Tracking
()
NEW
People
(Reporter: smaug, Assigned: vhilla)
References
(Depends on 4 open bugs, )
Details
(Keywords: meta)
Need to review the spec and check where we don't follow it
Updated•6 years ago
|
Priority: -- → P2
This related to, or blocking bug 588927. Also, see https://bugs.chromium.org/p/chromium/issues/detail?id=912892#c8 - an interoperability issue reported to Chrome that seems to be a Firefox and Edge (irrelevant at this point) issue - Basically, when two activation targets are nested <button><label>a</label></button>, Firefox picks the outermost element (<button>), Chrome picks the innermost element (<label>). Interestingly, Edge diverged from Internet Explorer (which behaved like Chrome).
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Assignee | ||
Comment 2•9 months ago
|
||
This should be resolved with my changes for bug 1658996.
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Assignee: nobody → vhilla
Assignee | ||
Updated•8 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•