[whatwg/fetch] Ability to detect CORS failures vs connection failures (#605)

And potentially other kinds of failures too.

In background fetch we might consider retrying a GET request in event of a connection failure. However, if the request failed a CORS check, there's little point in retrying.

I'm happy for this to live in spec-land. Later, we could consider exposing it via an error type, or the fetch oberver.

I guess *response* could have an *failure reason*. A value of "aborted" would probably replace the *aborted flag* from https://github.com/whatwg/fetch/pull/523/files.

-- 
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/605