- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Fri, 16 Mar 2018 13:20:02 +0100
- To: Mark James <mrj@rbate.com>, "public-web-nfc@w3.org" <public-web-nfc@w3.org>
On 2018-03-16 13:16, Mark James wrote: > On 16/03/18 22:46, Christiansen, Kenneth R wrote: >> >> Web NFC is behind a flag in Chrome. Given that shipping such features in chrome takes a lot of work and reviews, we are postponing doing that until we have landed the Generic Sensor API, which should be happening soon. >> >> The more use-cases and interest you can show for us shipping this, the easier it will be. >> >> Please test out the implementation behind the flag (about:flags to turn it on) >> > Thanks Kenneth for telling me about having to enable the WebNFC flag. I now get navigator.nfc defined. > > However, like Martin Beekhuizen, I'm also getting no response by the tapping device to a push of a URL record, although there's no WebNFC error. > > Is there anything I can code or do to speed up support, or as you said, should I wait until "after we ship Generic Sensor APIs"? > > My use case is definitely mainstream rather than niche. Indeed it is: https://github.com/w3c/web-nfc/issues/140 Anders > > Mark >
Received on Friday, 16 March 2018 12:20:30 UTC