[web-nfc] Distinguish between NFC not available and not enabled. (#237)

• From: Rijubrata Bhaumik via GitHub <sysbot+gh@w3.org>
• Date: Thu, 27 Jun 2019 08:25:36 +0000
• To: public-web-nfc@w3.org
• Message-ID: <issues.opened-461388532-1561623935-sysbot+gh@w3.org>

riju has just created a new issue for https://github.com/w3c/web-nfc:

== Distinguish between NFC not available and not enabled. ==
This came up while [reviewing](https://chromium-review.googlesource.com/c/chromium/src/+/1677736/5/services/device/nfc/android/java/src/org/chromium/device/nfc/NfcImpl.java#381). 

Present :
The Spec grouped all HW unavailable cases to NOT_READABLE, and data_not_support to NOT_SUPPORTED error, see item-5 and item-6 here https://w3c.github.io/web-nfc/#the-push-method.

Proposal in Android parlance, 

1. No NFC chip on device --> (mNfcManager == null || mNfcAdapter == null) --> NOT_SUPPORTED
2. OS-level NFC setting is OFF --> (!mNfcAdapter.isEnabled()) --> NOT_READABLE (pop up a message to turn ON NFC from system settings)

Scenario: 
Open GooglePay with NFC off, the messageBox "Turn on NFC"

Thoughts ?

Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/237 using your GitHub account

Received on Thursday, 27 June 2019 08:25:37 UTC