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

@joeyparrish [That change](https://chromium.googlesource.com/chromium/src.git/+/3ea192285757861d168b6e508bb34bc054194a22) added the `AbortController` and `AbortSignal` APIs, but it is not yet integrated with `fetch`. From the commit message:
> One fetch() wpt test that previously failed due to AbortController being undefined now times out because the "signal" properties in fetch options doesn't do anything yet. **This will be fixed once it is implemented.**

If you want, you can already write your own functions that can be aborted through an `AbortSignal`. However, Chrome's `fetch` doesn't yet know about `AbortSignal`s, so you can't yet abort a fetch with it.

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