Re: [fetch] Add timeout option (#20)

Hmmm. Interesting.

XMLHttpRequests work with CORS preflights and HTTP authentication, right? Why would this be any different?

I confess I'm not familiar with how "involvement of service workers" affects this, is there some comment that explains what negative interaction might happen with timeout? The mechanism for handling `.ontimeout` seems the same as `.onload` in the context of the main `.fetch` operation.

Regarding comment #20, is there a compelling reason to make timeout behave any differently from how it's already defined on XHR? This isn't ping; seems like a non sequitur.

> Also, if we get abort semantics, we might want to use those here and not reject, so that is unclear too at this point.

You mean... change the object you get out of `.fetch` to not be a standard JavaScript Promise?

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/20#issuecomment-135159715