- From: Mark R. James via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 May 2018 11:29:02 +0000
- To: public-web-nfc@w3.org
Thank you Alex. I've read your linked document, patch, and about Android Intents. I still don't understand why code is needed to support P2P. If WebNFC can currently write a URL to a passive tag, and a passive tag with a URL can currently trigger a browser selector or direct navigation on Android, what is Android Chrome WebNFC sending differently to a passive tag such that the receiving Android device doesn't respond? Is a lot of coding involved? Was the postponement due to the amount of work to polish and release, an assessment of the demand for and the utility of this feature, or corporate strategy? -- GitHub Notification of comment by mrj Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/139#issuecomment-387372324 using your GitHub account
Received on Tuesday, 8 May 2018 11:29:10 UTC