- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Dec 2020 14:12:10 +0000
- To: public-web-nfc@w3.org
Valid observations. In this version of the API, and in this PR, if ndef1.scan() has already resolved and ndef2.scan() is called, the events are still coming through ndef1's event. We could extend the "abort a pending scan" algorithm with steps to stop delivering event. But we don't have a way to notify ndef1 about it having been stopped. Using the onreadingerror event would be a misuse of it. Another pain point in this design. Could be avoided if we had a direct API like in #605. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/611#issuecomment-745309929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 December 2020 14:12:11 UTC