W3C home > Mailing lists > Public > public-nfc@w3.org > January 2014

Re: Chrome and Firefox browser asking for NFC access on Android

From: Arno Puder <arno@puder.org>
Date: Tue, 07 Jan 2014 11:54:35 -0500
To: Dave Raggett <dsr@w3.org>, <public-nfc@w3.org>
Message-ID: <1436da08140.2813.3a730ffa62825e16b8f865c86cbbd5c7@puder.org>
I am one of the engineers who helps Mozilla to add NFC API to their Firefox 
OS. The reason that the Firefox Browser (and most likely Chrome) for 
Android request NFC permissions is for the Android Beam capability that 
lets applications easily share information via NFC. It does not mean that 
the Android version of those browsers expose NFC capability via a Web API.


On January 7, 2014 6:37:40 AM Dave Raggett <dsr@w3.org> wrote:

> My colleague, Philipp Hoschka sent me the following report:
> > when installing Chrome and Firefox  browsers on an Android stick, I got 
> prompted to approve they have access to NFC - I found that interesting and 
> hard to explain, given that - afaik - they don't expose NFC APIs to WebApp 
> developers (and aren't involved in our NFC activities).
> >
> > Can you explain why they nevertheless ask for permissions?
> I heard that recent versions of Firefox for Android have some form of 
> support for NFC, but wasn't aware of any NFC support in Chrome. Anyone know 
> any more?   We should try to get Mozilla and Google involved in the NFC WG.
> --
> Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Monday, 13 January 2014 08:00:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:35:14 UTC