- From: Jake Archibald <notifications@github.com>
- Date: Thu, 31 Aug 2017 02:44:21 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 31 August 2017 09:44:42 UTC
jakearchibald commented on this pull request. > - <li><p>Let <var>cancel</var> be an action that - <a lt=terminated for=fetch>terminates</a> the ongoing fetch with reason - <i>end-user abort</i>. + <li><p>Let <var>cancel</var> be an action that <a lt=terminated for=fetch>terminates</a> the + ongoing fetch with reason <i>fatal</i>. I guess we could see the `AbortError` coming from the service worker and turn that into a network error with some sort of abort flag set. But things like "timeout" seem specific to XHR (right now), so having them in fetch isn't great. -- 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/pull/523#discussion_r136291133
Received on Thursday, 31 August 2017 09:44:42 UTC