Intent to Ship: AbortSignal.timeout() Static Method

Skip to first unread message

Scott Haseley

Apr 22, 2022, 6:50:00 PMApr 22
to blink-dev

Contact emails




Returns a new AbortSignal object that is automatically aborted after a given number of milliseconds. This method can be used by developers to easily implement timeouts for signal-accepting async APIs, e.g. fetch().

Blink component


TAG review

Note: the TAG review is still pending (we replied to their initial set of questions and are awaiting response). Since filing the issue, however, the DOM spec PR has been merged and Safari and Firefox have implemented the feature, meaning this should be exempt from TAG review.

TAG review status



Interoperability and Compatibility

Low risk. This feature is already part of the DOM standard, has web platform tests, and is implemented by Safari and Firefox. We'll improve eventual interop by shipping this feature.

Gecko: Shipped/Shipping ( Available in FF 100

WebKit: Shipped/Shipping ( Available in Safari TP Release 141:

Web developers: Positive. Positive reception to Chrome, Safari, and Node tweets:

Other signals: This has also shipped in Node and Deno.


We think this API is useful on its own, but also think it will benefit from an API to combine AbortSignals, e.g. combining a timeout with user cancellation, which we're currently working on:


The feature has already been implemented in both Safari and Firefox, but it would benefit from a polyfill for use in older browser versions.



WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No, this change is strictly additive.


Basic tooling only, i.e. autocomplete support for the new AbortSignal method will be provided.

Is this feature fully tested by web-platform-tests?


Flag name


Requires code in //chrome?


Tracking bug

Launch bug


Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?


Sample links

Estimated milestones


Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).


Link to entry on the Chrome Platform Status

Links to previous Intent discussions

Intent to prototype:

This intent message was generated by Chrome Platform Status.

Mike Taylor

Apr 26, 2022, 8:23:10 AMApr 26
to Scott Haseley, blink-dev
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit

Yoav Weiss

Apr 27, 2022, 2:18:00 AMApr 27
to Mike Taylor, Scott Haseley, blink-dev

Daniel Bratell

Apr 27, 2022, 5:03:40 AMApr 27
to Yoav Weiss, Mike Taylor, Scott Haseley, blink-dev
Reply all
Reply to author
0 new messages