W3C home > Mailing lists > Public > public-device-status@w3.org > December 2011

Re: no longer possible to detect battery presence? RE: Battery API in Last Call

From: Glenn Adams <glenn@skynav.com>
Date: Thu, 1 Dec 2011 16:23:57 -0700
Message-ID: <CACQ=j+f9YKBFoJF4FKFf0Mf+ogZn_4HmLqBU6fyihq_hSuhK2Q@mail.gmail.com>
To: olli@pettay.fi
Cc: "Carr, Wayne" <wayne.carr@intel.com>, Dominique Hazael-Massieux <dom@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>, "public-device-status@w3.org" <public-device-status@w3.org>
that's ridiculous; you might as well argue that the presence or absence of
the battery API itself is a privacy violation, since it allows some
fingerprinting

On Thu, Dec 1, 2011 at 4:06 PM, Olli Pettay <Olli.Pettay@helsinki.fi> wrote:

> On 12/02/2011 12:59 AM, Carr, Wayne wrote:
>
>> It appears that changes in the Last Call draft have made it so there
>> is no way to distinguish between a full battery and no battery being
>> present.  Was the ability to detect a battery being present
>> intentionally removed?
>>
>
> I hope so.
> Being able to detect whether or not there is a battery
> would be a privacy violation and would allow some
> fingerprinting.
Received on Thursday, 1 December 2011 23:24:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 1 December 2011 23:24:52 GMT