Fix html/webappapis/scripting/events/event-handler-attributes-body-wi… #3873
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ndow.html Fix html/webappapis/scripting/events/event-handler-attributes-body-window.html so that it no longer requires user interaction before moving on to the next test. The test is registering a number of event listeners on the body / window, which caused a confirmation dialog to be shown on unload. So that the test can be run in an automated fashion, we now unregister the event listeners at the end of the test. We now also checks that the event listeners have properly been unregistered.
|
Reviewers for this pull request are: @Ms2ger, @ayg, @gsnedders, @jdm, @jgraham, @plehegar, @sideshowbarker, @zcorpan, and @zqzhang. |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ndow.html
Fix html/webappapis/scripting/events/event-handler-attributes-body-window.html so
that it no longer requires user interaction before moving on to the next test.
The test is registering a number of event listeners on the body / window, which
caused a confirmation dialog to be shown on unload.
So that the test can be run in an automated fashion, we now unregister the event
listeners at the end of the test. We now also checks that the event listeners
have properly been unregistered.