- From: Darien Maillet Valentine <notifications@github.com>
- Date: Mon, 24 May 2021 10:44:59 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 24 May 2021 17:45:12 UTC
> you still need to 'assert' that signal.aborted is false before starting the async action That's true when the signal itself is input and would be important to call out. For library code, this is likely the common case. For app/UI code, it seems quite rare(?). About 90% of AC/AS use in our codebase is internal state (e.g. of a custom element) in service of the abort-replace-proceed pattern. The signal can never be aborted at the beginning of the work in such cases; you've just created it one line earlier. -- 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/946#issuecomment-847220182
Received on Monday, 24 May 2021 17:45:12 UTC