- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Oct 2022 23:31:37 +0000
- To: public-web-nfc@w3.org
reillyeon has just created a new issue for https://github.com/w3c/web-nfc: == AbortSignals not associated with a particular operation == As specified an `AbortSignal` passed as an option to `scan()`, `write()` or `makeReadOnly()` is not explicitly linked to that operation. This is theoretically fine because only one instance of those operations to exist at once but since we add the abort steps before performing such checks and the abort steps aren't specific about cancelling only the operation for which that signal was passed there is opportunity for an `AbortSignal` to abort an unrelated operation when it is signaled. Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/651 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 October 2022 23:31:39 UTC