Re: [whatwg/fetch] Term 'network error' conflicts with NEL, and is really a response. (#931)

You may be right that NEL should tie in to Fetch somewhere (given that Fetch's 'network error' does hide a lot of details that NEL tries to report on, I expect that it may have to hook in somewhere else). I wasn't arguing that they cover different sorts of errors, though.

The problem is just that we have two specs defining the term "network error", to represent two different things, and one of them should probably change, so that there's no ambiguity.

NEL uses the term 'network error' to refer to the actual error condition that may trigger a report. (The report isn't called an error; the error is something that happens at the network). Fetch is using the same term to refer not to the error condition itself, but to the response object returned as a result of an error.

That's why I was suggesting changing the Fetch name -- we'd end up having the underlying network condition be called a "network error" (wherever that ends up being defined), and that condition can cause a *network error response* to be returned by Fetch, and could also cause a *network error report* to be sent by NEL.

-- 
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/931#issuecomment-526708471