Uh oh!
There was an error while loading. Please reload this page.
events: add stop propagation flag to Event.stopImmediatePropagation - #39463
Conversation
33c4ebc to
23744d2CompareI didn't want to make a description too long, but feel like a bit more context could be interesting: When Event and EventTarget are available in Node js, the choice was to extend them to provide what was needed (bubbling in dispatchEvent). But since Event had everything needed I didn't think it would be required there, except for that tiny missing line in |
mikemadest
commented
Jun 26, 2023
Should this be closed? |
No this fix looks correct it was just missed - apologies this is our bad. |
nodejs-github-bot
commented
Jun 26, 2023
No worries, thank you for the answer! |
527ff4d to
53f073dComparemikemadest
commented
Jun 27, 2023
Pull request updated: |
benjamingr
commented
Jun 27, 2023
Thank you for your patience we truly don't deserve it and apologies for the contribution experience. Let's run CI and land this as soon as it's green. |
nodejs-github-bot
commented
Jun 27, 2023
53f073d to
d7de14dComparec4739fa to
d2b2e2cComparenodejs-github-bot
commented
Aug 10, 2023
d2b2e2c to
d712a39Comparenodejs-github-bot
commented
Aug 14, 2023
nodejs-github-bot
commented
Aug 14, 2023
Commit Queue failed- Loading data for nodejs/node/pull/39463 ✔ Done loading data for nodejs/node/pull/39463 ----------------------------------- PR info ------------------------------------ Title events: add stop propagation flag to Event.stopImmediatePropagation (#39463) Author Mickael Meausoone (@mikemadest, first-time contributor) Branch mikemadest:stop-immediate-propagation-flags -> nodejs:main Labels needs-ci Commits 1 - events: add stop propagation flag to Event.stopImmediatePropagation Committers 1 - Mickael Meausoone PR-URL: https://github.com/nodejs/node/pull/39463 Refs: https://dom.spec.whatwg.org/#dom-event-stopimmediatepropagation Reviewed-By: James M Snell Reviewed-By: Benjamin Gruenbaum ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/39463 Refs: https://dom.spec.whatwg.org/#dom-event-stopimmediatepropagation Reviewed-By: James M Snell Reviewed-By: Benjamin Gruenbaum -------------------------------------------------------------------------------- ⚠ Commits were pushed since the last approving review: ⚠ - events: add stop propagation flag to Event.stopImmediatePropagation ℹ This PR was created on Tue, 20 Jul 2021 08:02:57 GMT ✔ Approvals: 2 ✔ - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/39463#pullrequestreview-710658397 ✔ - Benjamin Gruenbaum (@benjamingr) (TSC): https://github.com/nodejs/node/pull/39463#pullrequestreview-1569362103 ✘ Last GitHub CI failed ℹ Last Full PR CI on 2023-08-14T09:35:27Z: https://ci.nodejs.org/job/node-test-pull-request/53301/ - Querying data for job/node-test-pull-request/53301/ ✔ Last Jenkins CI successful -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/5859369572 |
Spec mention stopImmediatePropagation should set both flags: "stop propagation" and "stop immediate propagation". So the second is not supported by Node as there is no hierarchy and bubbling, but the flags are both present as well as stopPropagation. It would makes sense to follow specs on that. Refs: https://dom.spec.whatwg.org/#dom-event-stopimmediatepropagation
d712a39 to
991ae2eComparenodejs-github-bot
commented
May 11, 2024
nodejs-github-bot
commented
May 12, 2024
aduh95
commented
May 12, 2024
Landed in 04cf8c2 |
Spec mention stopImmediatePropagation should set both flags: "stop propagation" and "stop immediate propagation". So the second is not supported by Node.js as there is no hierarchy and bubbling, but the flags are both present as well as stopPropagation. It would makes sense to follow specs on that. Refs: https://dom.spec.whatwg.org/#dom-event-stopimmediatepropagation PR-URL: #39463 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Spec mention stopImmediatePropagation should set both flags: "stop propagation" and "stop immediate propagation". So the second is not supported by Node.js as there is no hierarchy and bubbling, but the flags are both present as well as stopPropagation. It would makes sense to follow specs on that. Refs: https://dom.spec.whatwg.org/#dom-event-stopimmediatepropagation PR-URL: #39463 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Spec mention stopImmediatePropagation should set both flags: "stop propagation" and "stop immediate propagation". So the second is not supported by Node.js as there is no hierarchy and bubbling, but the flags are both present as well as stopPropagation. It would makes sense to follow specs on that. Refs: https://dom.spec.whatwg.org/#dom-event-stopimmediatepropagation PR-URL: nodejs#39463 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Spec mention stopImmediatePropagation should set both flags:
"stop propagation" and "stop immediate propagation".
So the second is not supported by Node as there is no hierarchy and bubbling,
but the flags are both present as well as stopPropagation.
Would it make sense to follow specs on that?
Refs: https://dom.spec.whatwg.org/#dom-event-stopimmediatepropagation