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

> Oh, so you'd expect `controller.abort()` to resolves with `false` if the fetch was already aborted?

[Yes.](https://github.com/whatwg/fetch/issues/447#issuecomment-292359393) That's how I interpreted this description from [the original meeting notes](https://github.com/whatwg/fetch/issues/455#issuecomment-274869169):

> Aborting an already-complete request shouldn't produce an error, it should be a no-op, but there should be some way to confirm that something was actually aborted. E.g. some deletion APIs return a boolean to signal if anything was actually deleted.

Much as how requesting the deletion of something that doesn't exist (whether it existed previously or not) means that nothing was actually deleted in response to the request (it was effectively a no-op), calling `abort()` on a fetch that's already aborted would state "abort not performed", returning `false` to signify the non-operation.

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