Fetch Javascript API should be abortable

Fixed Issue #13009916


Jake A.
Jul 31, 2017
This issue is public.
Fixed in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

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.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Brandon M.”

      Changed Status to “Confirmed”

      Changed Title from “Implement abortable fetch” to “Fetch Javascript API should be abortable”

      Changed Status from “Confirmed” to “In code review”

      Changed Status from “In code review” to “Fixed”

    • Wow, that was incredibly quick!

      I’m currently working on the spec, and noticed that I missed details around request.clone(). Once I’ve landed the spec changes and added more tests, I’ll open another bug. Of course, there’s a chance the spec will meet whatever Edge does already.

      Thank you for working on this!

    You need to sign in to your Microsoft account to add a comment.

    Sign in