Closed
Bug 1264291
Opened 8 years ago
Closed 8 years ago
initEvent must unset the stop propagation flag
Categories
(Core :: DOM: Events, defect)
Core
DOM: Events
Tracking
()
RESOLVED
FIXED
mozilla51
Tracking | Status | |
---|---|---|
firefox51 | --- | fixed |
People
(Reporter: ayg, Assigned: ayg)
Details
(Whiteboard: btpp-active)
Attachments
(1 file)
800 bytes,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
Bug 852115 comment 2 says we already do this, but http://w3c-test.org/dom/events/Event-initEvent.html says we don't (even after fixing bug 1263937). Chrome 49 passes the test, IE 11 does not.
Assignee | ||
Comment 1•8 years ago
|
||
Note that this makes little practical difference unless bug 1263937 is fixed, because currently the end of dispatch unsets the flag anyway. So currently this only is detectable if you call .stopPropagation() when the event is not currently being dispatched, which is a bit strange.
Assignee | ||
Comment 2•8 years ago
|
||
Tests now upstream: https://github.com/w3c/web-platform-tests/pull/3472
Assignee | ||
Comment 3•8 years ago
|
||
Attachment #8782413 -
Flags: review?(bugs)
Assignee | ||
Comment 4•8 years ago
|
||
Green try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=25c82b5414a4da3db926f31fc914079c305e2310
Updated•8 years ago
|
Attachment #8782413 -
Flags: review?(bugs) → review+
Pushed by ayg@aryeh.name: https://hg.mozilla.org/integration/mozilla-inbound/rev/0cca69a389fc initEvent must unset the stop propagation flag; r=smaug
Comment 6•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0cca69a389fc
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox51:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
You need to log in
before you can comment on or make changes to this bug.
Description
•