-
Notifications
You must be signed in to change notification settings - Fork 303
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
Event::ComposedPath doesn't handle this.currentTarget == null
#1343
Labels
Comments
Is there a case where event's path is non-empty and currentTarget is null? |
After reading the spec some more I don't think this can actually happen. |
Would adding an assert help? |
Yeah, that seems reasonable. |
annevk
added a commit
that referenced
this issue
Feb 10, 2025
annevk
added a commit
that referenced
this issue
Feb 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the issue with the DOM Standard?
Steps 4 and 5 of Event::composedPath say to
composedPath
is asequence<EventTarget>
, butcurrentTarget
is aEventTarget?
, per the Event idl interfaceIt is unclear to me what should happen when
currentTarget
isnull
.The text was updated successfully, but these errors were encountered: