Re: [whatwg/dom] Add a way to identify Abort errors originating from controllers (Issue #1033) from Benjamin Gruenbaum on 2021-11-21 (public-webapps-github@w3.org from November 2021)

From: Benjamin Gruenbaum <notifications@github.com>
Date: Sun, 21 Nov 2021 05:53:23 -0800
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/issues/1033/974821738@github.com>

> Hmm, it's not actually possible to brand all reason values, as any non-undefined value is a valid reason. ac.abort(false) is expected to reject with false.

It would be great if we could prohibit non `DOMException`s as reasons even if it means a lot more work for Node.js in the future because I am a lot more worried about the "API surface increased and cancellation is hard to determine" problem than the "Node will have portability issues with it" problem.

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

Received on Sunday, 21 November 2021 13:53:36 UTC