Standards: https://dom.spec.whatwg.org/#aborting-ongoing-activities https://github.com/whatwg/fetch/pull/523
Summary: In bug 1378342 I have been working on Abort API and its integration with Fetch API. There are 2 separate prefs: dom.abortController.enabled and dom.abortController.fetch.enabled both set to false in release, and to true in nightly. These allow the enabling of Abort API independently, and the enabling of Abort + Fetch. Abort API is a simple API that can be used separately, but when integrated with Fetch, if a fetch() operation is aborted, this involves the canceling of the networking, and the body consuming, and the ReadableStream (if involved and enabled). Abort API is already part of the DOM spec and I would like to enable it by default everywhere in our codebase (dom.abortController.enabled). Abort + Fetch integration is not part of the spec yet. There is a read-ish pull-request, but as soon as it is merged, I would like to enable the second pref as well (dom.abortController.fetch.enabled). Bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=1394085 https://bugzilla.mozilla.org/show_bug.cgi?id=1378342 Other vendors: Chromium https://bugs.chromium.org/p/chromium/issues/detail?id=750599 I haven't found anything about Edge and Safari. Estimated target date: Firefox 58. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
