- From: Randall Leeds <notifications@github.com>
- Date: Sat, 23 Jul 2022 11:41:52 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 23 July 2022 18:42:06 UTC
The whatwg/fetch#1343 seems to be going in the direction of aborting with the reason from the signal, but this PR is suggesting instead to abort with an `AbortError` and its `cause` set to the signal's reason. I've been searching for several hours through issues and don't see a resolution anywhere that's being consistently applied across environments. Node.js seems to have consistently opted for using `cause` ([examples](https://github.com/nodejs/node/search?p=2&q=%22new+AbortError%22)). I can understand both perspectives. However, one aspect of the `cause` approach that seems unaddressed is that `DOMException` doesn't seem to specify `cause` yet. I haven't found an issue for that. Should I open one? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1090#issuecomment-1193170619 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1090/1193170619@github.com>
Received on Saturday, 23 July 2022 18:42:06 UTC