-
Notifications
You must be signed in to change notification settings - Fork 29k
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
events: reset event state after dispatch #54642
base: main
Are you sure you want to change the base?
Conversation
|
Review requested:
|
| assert_equals(event.target, target); | ||
| assert_equals(event.currentTarget, null); | ||
| assert_array_equals(event.composedPath(), []); | ||
| }, "A constructed EventTarget implements dispatch correctly"); |
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.
This is the test that checks the behavior. Afaict event.target -> not reset after dispatch; event.currentTarget -> reset after dispatch.
e1c386d
to
79f91be
Compare
|
Could you either drop the WPT update (if so, it'll be done in #54468), or split this into two commits? Thank you |
This comment was marked as outdated.
This comment was marked as outdated.
79f91be
to
eafa45d
Compare
|
I split into two commits so we can test the change. |
This comment was marked as outdated.
This comment was marked as outdated.
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
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
I'm honestly a few CI runs from giving up |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
9th time's the charm |
|
I went ahead and visited all failed builds on this PR and added them as flaky on my PR #54802 |
|
10th time might actually be it then |
eafa45d
to
55c83d0
Compare
|
If the CI doesn't pass here I am no longer going to bother with this PR |
|
PR is currently blocked from landing by unreliable CI. |


Fixes #54617