- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Mar 2020 07:20:24 +0000
- To: public-web-nfc@w3.org
In the [scan()](https://w3c.github.io/web-nfc/#the-scan-method) algorithm we reject the promise with a DOMException when the NFC adapter is not accessible (many reasons given). The reading algorithm is invoked by the scan() algorithm and will use a simple error event for any read error. An app doesn't need to know anything else, since the only way to recover is that the user retries the touch, therefore the app just has to show there was an error. We don't have a use case for exposing HW specific error codes to web pages and in general we better avoid it in order to minimize fingerprinting surface. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/549#issuecomment-597480997 using your GitHub account
Received on Wednesday, 11 March 2020 07:20:26 UTC