On Tue, Aug 29, 2017 at 2:05 AM, Andrea Marchesini <[email protected]> wrote:
> 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). > I don't understand why we would potentially ship these separately. AFAICT the abort API is only really useful if its integrated into something like fetch(). Currently the Fetch API is the only part of the platform that uses it. Also, we have seen people do thing like feature detect for ReadableStream and assume Response.body can be a ReadableStream. This is why we are not shipping the js ReadableStream until the fetch body stream can ship as well. I worry that people would do a similar kind of feature detection with Abort API. Also, while the fetch+abort spec change has not landed yet, we pretty much have consensus. There are WPT tests in the tree already. I don't think this is what is blocking shipping the fetch+abort code. To me its a bigger issue that we still don't pass many of those WPT tests. If we passed the tests then I think we could reasonably ship it given the current level of consensus on the spec. > Other vendors: > Chromium https://bugs.chromium.org/p/chromium/issues/detail?id=750599 > I haven't found anything about Edge and Safari. > Edge has marked their issue for this "fixed": https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/13009916/ It hasn't shipped yet, of course. > Estimated target date: Firefox 58. > If you are asking to enable the Abort API by default now, wouldn't that put it in FF57? _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
