| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I 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 stopImmediatePropagation and it felt like maybe this should be here? |
Sorry, something went wrong.
|
Should this be closed? |
Sorry, something went wrong.
|
No this fix looks correct it was just missed - apologies this is our bad. |
Sorry, something went wrong.
Sorry, something went wrong.
No worries, thank you for the answer! |
Sorry, something went wrong.
|
Pull request updated: |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
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 |
Sorry, something went wrong.
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
Sorry, something went wrong.
Sorry, something went wrong.
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>
| Back | FazBrowse Home | New Git URL |
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