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

Re: Battery Status Event Spec

From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Date: Tue, 5 Apr 2011 19:22:40 +0300
Message-ID: <4FFA6390-CB14-40AB-B956-D0BCC42A8994@nokia.com>
To: "public-device-apis@w3.org Group WG" <public-device-apis@w3.org>

The Editor's Draft of the Battery Status Event Specification is at:


It builds on the initial draft [1] and addresses or takes a note of the issues identified so far [2]. All feedback is welcome.

Below I address the comments received so far (thanks!). The proposed changes have been baked in to the Editor's Draft.

On 31.3.2011, at 17.48, ext Robin Berjon wrote:

> It is certainly true that timeRemaining is hard to calculate, and will necessarily fluctuate as the activities you perform on your computer change. I think that it should be optional (I don't think that all platforms support it) but that it should be exposed if available as it is even harder for an application to evaluate it than it is for the system.

timeRemaining is now optional i.e. nullable.

On 31.3.2011, at 16.37, ext Robin Berjon wrote:

> Maybe the best thing would be to provide some guidelines, maybe as SHOULDs?
>    UAs SHOULD dispatch an event when timeRemaining varies by a minute or more.
>    UAs SHOULD dispatch an event when isCharging or isBattery changes.
>    UAs SHOULD dispatch an event when level varies by a 1% or more.

Added the SHOULDs.

On 31.3.2011, at 1.02, ext Tran, Dzung D wrote:

> Please proceed with your plans and check in to the same location as SysInfo API. Also, I would like to contribute if possible

Thanks, feel free to contribute.


[1] http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0122.html
[2] http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0143.html
Received on Tuesday, 5 April 2011 16:23:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:48 UTC