RE: Implementation status update

There has been some discussion, like always having the object there in order to avoid fingerprinting. But please file a but on the spec and start discussion there.

Kenneth

> -----Original Message-----
> From: Mark James [mailto:mrj@rbate.com]
> Sent: Thursday, August 11, 2016 1:33 PM
> To: Web NFC (W3C) <public-web-nfc@w3.org>
> Cc: Syrjala, Ilkka <ilkka.syrjala@intel.com>; henrylim.everything@gmail.com
> Subject: Re: Implementation status update
> 
> Great. Thanks Kenneth for the detailed reply. I'll give Android Chrome a go.
> 
> Just one question on the implementation that's not clear from the spec: Is it
> possible to differentiate from the value of navigator.nfc whether Web NFC is
> either not implemented, not active because there are no NFC devices, or not
> available because it's in use? It would be good to tell these apart so that the
> user can be given a helpful message to get it working.
> 
> Mark
> 
> On 11/08/16 18:33, Christiansen, Kenneth R wrote:
> > We are in the progress of finishing upstreaming the remaining parts of our
> WebNFC implementation to Chrome on Android.
> >
> > It has been a long journey because of some major refactoring of Chrome
> (Project Onion Soup) going on in parallel, but now we are almost there.  A
> few patches are still pending as reviewers are still on vacation, but they
> should be landed within the next month I would say.
> >
> > In order to test Web NFC, you need to enable Experimental Web Platform
> Features in the about:flags on Chrome for Android. The Dev Channel should
> give you the most complete implementation.
> >
> > We had an experimental implementation for Linux, using 'neard' - but we
> refocused to Android as neard has several bugs and missing features that are
> required.
> >
> > Kenneth
> >
>

Received on Thursday, 11 August 2016 13:29:06 UTC