Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

> It seems likely something is clearly inconsistent and wrong here, but its not clear to me from the sketch what the correct defined behavior should be.

It may help to rephrase the API as being about abort *requests*, not about forceful aborts. It's a request to the person who you give the signal to to stop doing unnecessary work. It's not a demand that the API terminate with an AbortError. You only terminate with an AbortError if you actually decided to respond to that request and abort the underlying process (here, a fetch).

So in some of the tricky cases being discussed here, where there is no work left to abort, then in that case you should just ignore the abort request---there's nothing to abort.

-- 
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/447#issuecomment-293139999