- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Mon, 14 Jul 2025 08:00:52 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 14 July 2025 15:00:56 UTC
saschanaz created an issue (whatwg/dom#1389) ### What is the issue with the DOM Standard? Currently it's not straightforward to track whether all abort algorithms are finished. You would call `AbortController.abort` and then would hope it that things are aborted, before starting anything new. It's okay to do so when the new job never clashes with the previous supposed-to-be-aborted job (like some simple `fetch()` calls), but might clash if the abort algorithm includes closing a file handle, etc. Would be nice if abort event had something like `ExtendableEvent.waitUntil`. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1389 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1389@github.com>
Received on Monday, 14 July 2025 15:00:56 UTC