- From: Wanming Lin via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Sep 2019 07:18:23 +0000
- To: public-web-nfc@w3.org
Honry has just created a new issue for https://github.com/w3c/web-nfc: == Two 'ignoreRead' relevant descriptions look wrong == 1. Look at the definition of [ignoreRead](https://w3c.github.io/web-nfc/#dom-nfcpushoptions-ignoreread), does it only work for an NFC tag? > When the value of the ignoreRead property is true, the push algorithm will skip invoking the receiving and parsing steps for an NFC tag. 2. In `push` operation, > If options's ignoreRead is not equal to true, run the receiving steps. While in the [receiving steps](https://w3c.github.io/web-nfc/#steps-receiving), “step 3 of the NFC listen algorithm.” is out of sync, what was the exact step it intended to refer to? And hardcoding step number is not appropriate. > If there are any NFCReader instances in activated reader objects then UAs MUST listen to NDEF messages, according to step 3 of the NFC listen algorithm. Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/349 using your GitHub account
Received on Tuesday, 10 September 2019 07:18:25 UTC