Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.3k
events: setting event cancelBubble calls stopPropagation#50405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Deokjin Kim <[email protected]>
anonrig commented Oct 26, 2023
Can you add a test? |
benjamingr left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a test, changes lgtm
mertcanaltin commented Nov 12, 2023 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
ı added a test |
| thrownewERR_INVALID_THIS('Event'); | ||
| if(value){ | ||
| this.stopPropagation(); | ||
| this.#propagationStopped =true; |
jeanbernNov 16, 2023 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is setting cancelBubble supposed to be one-way? The proposed change doesn't modify this.#propagationStopped when value is false
nvm: For anyone else wondering the same thing see here: whatwg/dom#211
nodejs-github-bot commented Dec 9, 2023
nodejs-github-bot commented Dec 25, 2023
mertcanaltin commented Dec 30, 2023
I wonder if I should do an update here? |
nodejs-github-bot commented Dec 31, 2023
nodejs-github-bot commented Jan 1, 2024
nodejs-github-bot commented Jan 2, 2024
mertcanaltin commented Jan 6, 2024
I guess flakky was the test 🤔 💭 |
nodejs-github-bot commented Jan 6, 2024
nodejs-github-bot commented Jan 9, 2024
nodejs-github-bot commented Jan 17, 2024
nodejs-github-bot commented Jan 21, 2024
mertcanaltin commented Jan 21, 2024
passed 🎉🚀 |
mertcanaltin commented Jan 25, 2024
@benjamingr I would be very happy if you can make an update here, now it seems to have passed all the tests |
mhdawson left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
mhdawson commented Feb 26, 2024
@mertcanaltin I'm getting this warnings when landing - Can you take a look? I'll land anyway but would be good to get that fixed up. |
PR-URL: #50405 Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Deokjin Kim <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
mhdawson commented Feb 26, 2024
Landed in 399654f |
mertcanaltin commented Feb 27, 2024
I am very sorry for the late response, thank you very much for correcting me @mhdawson ❤️ 🚀 |
PR-URL: #50405 Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Deokjin Kim <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
PR-URL: #50405 Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Deokjin Kim <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
PR-URL: #50405 Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Deokjin Kim <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
PR-URL: nodejs#50405 Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Deokjin Kim <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
issue: #50401
In this issue, we addressed the problem where setting cancelBubble to true unintentionally called the stopPropagation method. The solution ensures that stopPropagation is only called when cancelBubble is explicitly set to false, as it should be. This change prevents the method from being called when cancelBubble is true or not explicitly set