You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: