Re: [ServiceWorker] Cancelling HTTP fetch (#592)

> If the user hits X (or even closes the tab) while /whatever.json is fetching, I don't think we can simply cancel the request.

This is the part I don't like the most (if not the main reason I don't like Fetch) ... an API that goes out without thinking people in data roaming or people pressing a download or listen button by accident shouldn't happen in this mobile first era.

Please fix Fetch cancel-ability for real (dropping the underlying network) and also please tell whoever is in charge of [this page](https://fetch.spec.whatwg.org/#fetch-api) that it should mention inside a strong that Fetch so far cannot cancel.

> The fetch() method is relatively low-level API for fetching resources. It covers slightly more ground than XMLHttpRequest, although it is currently lacking when it comes to reporting progression **and it cannot abort a request/stream**

I wish progress was the real difference with XHR, missing `.abort()` for a Network API is way more harmful.

Thanks for collaboration and your understanding.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/592#issuecomment-85466944