- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Mar 2020 07:12:28 +0000
- To: public-web-nfc@w3.org
> And, by my current understanding, seems Browser has no way to block the native processing of NDEF? I mean, Browser is just one of the clients of Android NFC service, it can get the "discovered NFC tags events" but is not able to block other clients getting them. When reading NDEF tags with Web NFC, the native "Android NFC tag" activity is not launched. This is the root issue from what I understand. Chrome should catch it and dispatch it to the website using Web NFC scan. If not, it should "hold" it. @OlivierGrenoble Can you share/record a screencast of what's currently happening so that everyone get a good understanding? -- GitHub Notification of comment by beaufortfrancois Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/551#issuecomment-601023370 using your GitHub account
Received on Thursday, 19 March 2020 07:12:30 UTC