- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Sat, 29 Jun 2019 01:06:02 +0000
- To: public-web-nfc@w3.org
@odejesush has been working on making sure that Bluetooth availability information is available to applications with the `getAvailability()` method. The distinction is that the Bluetooth permission dialog is an opportunity for the user agent to provide a link to system settings to enable Bluetooth while there is no equivalent for NFC and so it is up to web content to detect that NFC is available but disabled. It seems reasonable to differentiate between the two conditions and return a "not readable" error when NFC hardware is available but disabled and a "not supported" error if it is not present or inoperable. If a user agent decides to display UI when a page is requesting a read operation it could forgo returning the "not readable" error and instead prompt the user to enable NFC itself. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/237#issuecomment-506914467 using your GitHub account
Received on Saturday, 29 June 2019 01:06:04 UTC