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

> If the fetch is initiated on the same thread as the controller, should we ensure aborting before the fetch promise resolves always rejects the promise with an AbortError, even if the response completes? It may involve removing things from the microtask queue. Worried that pretending an upload was aborted, when it actually completed, is a bit misleading.

Yeah, I thought this was resolved with the decision that `abort()` would be async, resolving with a boolean of whether the request was actually aborted or if it had already ended by the time the abort was evaluated.

-- 
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-291340721