W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2011

Re: Battery Status API Last Call Feedback

From: <Frederick.Hirsch@nokia.com>
Date: Tue, 29 Nov 2011 23:10:28 +0000
To: <annevk@opera.com>
CC: <Frederick.Hirsch@nokia.com>, <public-device-apis@w3.org>
Message-ID: <43FEAC5E-2D2E-4D35-AB87-6E56CFD0DD47@nokia.com>
Anne

I have entered this as in our last call comment tracker as two comments

#1) LC-2574 for Event handling (queue an on* handlers)

https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-battery-status-20111129/2574

#2)  LC-2575 for privacy question

https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-battery-status-20111129/2575

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Co-Chair, W3C DAP Working Group




On Nov 29, 2011, at 6:52 AM, ext Anne van Kesteren wrote:

> The events need to be queued using the task queue defined in HTML5. It should probably be worded in such a way that the attribute is updated and the event is dispatched in the same task so nothing else can observe the attribute having changed before the event is dispatched.
> 
> You also need to actually define the various on* attributes as being event handlers and update their IDL to match the latest crazy IDL syntax (which might be simplified, so maybe you want to wait for that).
> 
> Should there be some kind of privacy section? I guess you cannot tell much from someone charging his phone, but maybe in conjunction with other data you can find patterns of some kind. Fingerprinting is probably also somewhat aided by this functionality.
> 
> 
> -- 
> Anne van Kesteren
> http://annevankesteren.nl/
> 
Received on Tuesday, 29 November 2011 23:11:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:24 GMT