-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
We decided to make abort() no-op more #4033
Conversation
See whatwg/xhr#88 for the discussion that led to these changes.
Reviewers for this pull request are: @Manishearth, @Ms2ger, @caitp, @emilio, @hallvors, @ibelem, @jdm, @jungkees, @kangxu, @mathiasbynens, @plehegar, and @ronkorving. |
To cover all issues raised in #88, I believe open-during-abort should also be modified by adding this final check:
Since abort() does not fire a readystatechange event in step 3, the test cannot currently catch an erroneous state change. Apologies if this is already covered in this PR. |
@berniegp since assert_array_equals in that test happens after the |
Never mind, I see what you mean. |
Testing in Firefox
All results were stable All results
|
Testing in Chrome
All results were stable All results
|
See whatwg/xhr#88 for the discussion that led
to these changes.