- From: Benjamin Gruenbaum <notifications@github.com>
- Date: Wed, 03 Feb 2021 08:46:04 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 3 February 2021 16:46:16 UTC
Node.js doesn’t currently expose its DOMException and throws errors inside APIs that look like the DOM AbortError (same name and same code but without some of the quirks - quite painful since Node.is codes have a different format) Of course in implemented DOM APIs Node will behave in a spec complaint way and throw a DOM AbortError. However since Node vendors certain bits of its core as user land modules (readable-stream) and exposing DOMException was a show stopper there we ended up with that compromise. I believe Jake Dor Robert Matteo and myself were on that call. We are open to changing this behavior. Note we currently do not expose our AbortError either. -- 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/927#issuecomment-772652451
Received on Wednesday, 3 February 2021 16:46:16 UTC