- From: OlivierGrenoble via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Mar 2020 06:31:59 +0000
- To: public-web-nfc@w3.org
> I don't think this relates to `ignoreRead`, which is only for ignoring active WebNFC `scan()` sessions when writing and does not (cannot) affect how Android handles the tag. Thanks for this clarification, that 's good to know. > Did this work for you? I mean can it forbid Android from reading the tag? @OlivierGrenoble > > > I have been told to run scan() and discard the onreading events. No, for the moment I haven't been able to get it work. I have started a scan() before calling the write function but the difficult point is to know when to abort this scan. I have done it in the then() function of writer.write() but I still get the native processing. Based on what you said, I'm now thinking that I should set ignoreRead to false to be sure that my callbacks "catched" the read notification and discard it. Would you have an example of code writing an NDEF without triggering the native processing of this NDEF? My 2 cents: I have the feeling that we are not going in the right direction here. It is too cumbersome. -- GitHub Notification of comment by OlivierGrenoble Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/551#issuecomment-601011844 using your GitHub account
Received on Thursday, 19 March 2020 06:32:00 UTC