Re: [whatwg/dom] `AbortController` / `AbortSignal` was updated in a somewhat breaking way (Issue #1059) from Kyle Simpson on 2024-09-01 (public-webapps-github@w3.org from September 2024)

From: Kyle Simpson <notifications@github.com>
Date: Sun, 01 Sep 2024 12:31:32 -0700
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/issues/1059/2323470065@github.com>

> Before the change there was a singular reason, exposed in APIs that ended up rejecting a promise (i.e., an "AbortError" DOMException).

Just for posterity sake, this is not accurate as far as I know. Prior to the spec adding `reason`, the `signal.reason` access would always return `undefined`. I dunno if there was always an internal `AbortError` DOMException or not... but it wasn't exposed on the `reason` property. I maintain this was a breaking change. But I guess it doesn't matter anymore.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1059#issuecomment-2323470065
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1059/2323470065@github.com>

Received on Sunday, 1 September 2024 19:31:36 UTC