- From: François Daoust <notifications@github.com>
- Date: Thu, 01 Aug 2024 06:10:39 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 1 August 2024 13:10:43 UTC
### What is the issue with the DOM Standard? The [example on using AbortController and AbortSignal objects](https://dom.spec.whatwg.org/#aborting-ongoing-activities-spec-example) should **queue a global task** to resolve `p` with *amazingResult* (step 3.2). That's sort of already recorded in https://github.com/whatwg/dom/issues/1031#issuecomment-1233136977 but I wasn't clear whether that comment was really about this, so I thought I would create a dedicated issue. FWIW, step 2.3.2 seems correct to me since abort steps run [within a global task](https://dom.spec.whatwg.org/#dom-abortsignal-timeout). Via https://github.com/w3c/strudy/issues/663 where I've started to look into automating detection of such hiccups in specs (although not in examples) -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1300 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1300@github.com>
Received on Thursday, 1 August 2024 13:10:43 UTC