- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Mar 2020 13:34:34 +0000
- To: public-web-nfc@w3.org
> Here is a screencast (in a zip file). I have clicked on "Write NFC Tag", then on "Write URI", then I have taped the NFC Tag. The URI is written successfully. As you can see, I immediately gets a notification to open the URI in Chrome. Based on the video I would say things work as they are designed to work (*) and also according to your [preference](https://github.com/w3c/web-nfc/issues/551#issuecomment-601024359) to not interfere with other apps on reading. (*) But IIUC you would prefer that Web NFC implementation would create and "own" a sort of "tag writing session" in a way that re-reading that tag would get dispatched to Web NFC and discarded there? Of course the app could do that by: - setting up a scan - write with `ignoreRead=true` - ignoring the read event. But I understood that was not your preference, right? -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/551#issuecomment-601181157 using your GitHub account
Received on Thursday, 19 March 2020 13:34:36 UTC