Skip to content
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

abort #21

Closed
Mouvedia opened this issue Apr 21, 2018 · 0 comments
Closed

abort #21

Mouvedia opened this issue Apr 21, 2018 · 0 comments
Milestone

Comments

@Mouvedia
Copy link
Owner

Mouvedia commented Apr 21, 2018

https://stackoverflow.com/questions/31061838
https://developers.google.com/web/updates/2017/09/abortable-fetch
https://www.quirksmode.org/blog/archives/2005/09/xmlhttp_notes_a_1.html
web-platform-tests/wpt#6484 (comment)
JakeChampion/fetch@da07fa1
https://lists.w3.org/Archives/Public/public-webapps/2013JanMar/0545.html
!!self.Request && 'signal' in self.Request.prototype

It is not really correct to manually force a connection to go away by nulling out various
aspects of the request object or callback function or overwriting an existing XHR with another
request. It may have a similar feeling to the end user in some cases because a callback won’t
happen, but any changes may still happen on the server as the request, once sent, still happened.

@Mouvedia Mouvedia added this to the 1.1 milestone Apr 21, 2018
@Mouvedia Mouvedia closed this as completed Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant