Bug 174980 - [Fetch API] Implement abortable fetch
Summary: [Fetch API] Implement abortable fetch
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-31 02:31 PDT by Jake Archibald
Modified: 2018-12-10 07:10 PST (History)
13 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jake Archibald 2017-07-31 02:31:59 PDT
This includes AbortController & AbortSignal https://dom.spec.whatwg.org/#aborting-ongoing-activities.

Fetch abort tests are at https://github.com/w3c/web-platform-tests/pull/6484.

Fetch abort spec is in progress https://github.com/whatwg/fetch/pull/523.

Mozilla intends to start implementing next month, using the tests rather than the spec.
Comment 1 Antonio Torres 2018-07-24 20:48:13 PDT
Is there a roadmap for these features? I cannot find them in Webkit Status, and Firefox and Chrome already have support for aborts.
Comment 2 molsson 2018-11-25 07:26:06 PST
It's a strange that:

* caniuse.com claims that Safari supports AbortController
* window.AbortController is defined in Safari

...but a simple testcase like this:

http://temp.minimum.se/abort-native.html

Shows that Safari 12.0.1 sends the request even if controller.abort() has been called, i.e. only some "placeholder AbortController" has been added in Safari. It is not working at all.
Comment 3 Alexandre C 2018-11-25 23:41:26 PST
I confirm what molsson mentioned. 
The abort on fetch request on Safari 12.0.1 doesn't work at all.
Comment 4 Sergey Rubanov 2018-12-10 07:10:19 PST
This is really sad that only Webkit is missing Abortable Fetch since April 2018