Closed
Bug 1117544
Opened 9 years ago
Closed 5 years ago
multiple FocusEvents for focus change within the same ShadowRoot
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mail, Unassigned, NeedInfo)
References
Details
(Keywords: testcase)
Attachments
(1 file)
2.86 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:34.0) Gecko/20100101 Firefox/34.0 Build ID: 20141125180439 Steps to reproduce: 1. create a ShadowDOM structure (see attached test case) 2. bind focus event listener to document 3. focus element within the ShadowRoot 4. focus another element within the ShadowRoot Live test case: http://medialize.github.io/ally.js/tests/browser-bugs/gecko-shadow-dom-multiple-events.html Actual results: I received two focus events, both naming the first ShadowHost as the event.target. Also reproducible in Firefox Nightly 37.0a1 (2015-01-04). Expected results: There should have been only a single focus event dispatched, because from the document's perspective nothing changed, the focus is still on / in the ShadowRoot. The second event, should've had event.target === event.relatedTarget and should have thus not have been dispatched according to http://w3c.github.io/webcomponents/spec/shadow/#retargeting-focus-events Possibly related issues: * https://bugzilla.mozilla.org/show_bug.cgi?id=1117535 * https://bugzilla.mozilla.org/show_bug.cgi?id=962251
Updated•9 years ago
|
Updated•9 years ago
|
Flags: needinfo?(wchen)
Comment 1•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Comment 2•5 years ago
|
||
2019-03-06
This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.
The request for information has not been answered, and we can't move forward on the bug so we are closing it.
If the defect is still present, please reopen this bug with an updated report.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•