Not hating on it, there are always reqs involved, but can somebody explain why not .abort() ? https://developers.google.com/web/updates/2017/09/abortable-fetch#api_disagreement …pic.twitter.com/79LBDsEe0K
My guess is that b/c the promise abort spec was rejected, adding it just for XHR would be a no-go. Also this works with async/await.
-
-
Why a no-go? Do all promises need to have an == API? For await: var fetchRes = fetch(...) await fetchRes // ... can still fetchRes.abort()
-
Oh I found out the problem. It's because the fetch API is in two stages, with two promises
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.