Re: [whatwg/fetch] More informative error types (#526)

A way forward may be to make a list of desired error types and see which ones are OK to expose cross-origin or not. Here's a strawman:

- "API error" (gave something that's not a Request or a URL to fetch())
- "network error" (something at the TCP/IP layer caused us to fail to fetch
- "abort error" (the user closed the tab or clicked stop or something like that)
- "timeout error" (the browser timed out the request (I'm not sure this really happens for fetch()))
- "offline error" (this is a subset of network error when the browser knows it's offline)

I guess we already have the name AbortError taken with the new abortable fetch thing.


-- 
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/526#issuecomment-380686368