Skip to main content

AbortController / AbortSignal.timeout()

Cancels asynchronous work through a signal; AbortSignal.timeout() and any() create signals that abort on their own. Specification: dom.spec.whatwg.org/.

Results​

Probed on 2026-10-19 with Node.js v22.23.3.

warpdom 0.1.6​

Supported

3 of 3 checks work.

Web IDL existence (coverage):

Report a wrong result for warpdom

happy-dom 21.0.3​

Supported

3 of 3 checks work.

Web IDL existence (coverage):

  • AbortController: interface present; 1 of 2 members present, missing: signal.
  • AbortSignal: interface present; 6 of 7 members present, missing: onabort.
Report a wrong result for happy-dom

jsdom 30.1.3​

Supported

3 of 3 checks work.

Web IDL existence (coverage):

Report a wrong result for jsdom

linkedom 0.18.13​

Supported

3 of 3 checks work.

The window's value is Node.js's own global (identical object), not the engine's implementation.

Web IDL existence (coverage):

  • AbortController: interface present (Node.js's own global); 2 of 2 members present.
  • AbortSignal: interface present (Node.js's own global); 7 of 7 members present.
Report a wrong result for linkedom

Checks​

Exists when: typeof window.AbortController is defined.

  • abort-reason: abort() fires "abort" and sets signal.reason to an "AbortError" DOMException. (spec)
  • timeout: AbortSignal.timeout(10) aborts with a "TimeoutError" DOMException. (spec)
  • any: AbortSignal.any([a, b]) aborts when one of its inputs aborts, with that reason. (spec)

Node.js globals​

Node.js defines AbortController itself. Depending on the test runner and its environment, tests may see Node's version even where the engine's window has none; these results describe the engine's window only.