- From: Mark R. James via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Dec 2018 22:32:37 +0000
- To: public-web-nfc@w3.org
I've now implemented a way to share my URLs by NFC without use of WebNFC, so I'm no longer as insistent about early peer-to-peer support. Because the URLs being shared are within my website, and because a peer-to-peer tap when Chrome is being used will activate Android Beam to send the URL of the current page, I can set a cookie on the sending browser and then open the URL to be shared in a new window. The cookie allows my website to distinguish sender from receiver and either show tap instructions or process the share. I still don't understand why it's hard for WebNFC to use Android Beam in the same way, just with an arbitrary URL rather than the URL of the current page. -- GitHub Notification of comment by mrj Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/166#issuecomment-443896088 using your GitHub account
Received on Monday, 3 December 2018 22:32:39 UTC