Re: [whatwg/fetch] Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts) (#179)

It's functionally the same as XHR's timeout. Ergonomics is a very important part of it, because for a robust web app the timeout has to be added to *every single `fetch()` call* (I'm serious). 

I know this from experience of developing a major PWA. I have done this for our XHR and [contributed such interface](http://visionmedia.github.io/superagent/#timeouts) to [superagent](https://www.npmjs.com/package/superagent). 

We've found that there are unbelievably broken phones/mobile operators that made connections appear infinitely slow (similar to what @jakearchibald calls Lie-Fi) so our requests would get stuck waiting forever, and in turn keep related bits of logic or UI similarly stuck all over the place.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/179#issuecomment-450862917