- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Dec 2019 15:18:50 +0000
- To: public-web-nfc@w3.org
@marcoscaceres I guess you're referring to this part: > If the UA is not allowed to access the underlying NFC Adapter (e.g. a user preference), then reject p with a "NotReadableError" DOMException and return p. We used `NotReadableError` because we already had `NotAllowedError` and `SecurityError. The goal was to help web developers to inform their users that NFC setting was disabled, and that they should turn on NFC manually in platform settings ([android for info](https://www.mobigyaan.com/wp-content/uploads/2016/04/How-to-turn-on-NFC-on-your-smartphone-Android-Guide-2.jpg)). If you can think of another one, that is not used, we're all ears. > Something still doesn’t feel right here. The spec doesn’t hook into the “request permission” algorithm of the permission API. I was at a minimum expecting that. We are. See https://w3c.github.io/web-nfc/#obtaining-permission  -- GitHub Notification of comment by beaufortfrancois Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/449#issuecomment-564592313 using your GitHub account
Received on Wednesday, 11 December 2019 15:18:51 UTC