RfC: LCWD of Battery Status API; deadline October 2

WebApps received a Request for Comments re DAPWG's August 28 Last Call 
WD of Battery Status API (last published as a [CR], see [Diff]):


Individual WG members are encouraged to provide individual feedback.

If anyone in WebApps wants to propose an official group response, please 
do so ASAP, in reply to this e-mail so the group can discuss it.

Comments should be sent to public-device-apis @ w3.org by October 2. 
Presumably, DAPWG also welcomes data about "silent reviews", f.ex. "I 
reviewed section N.N and have no comments".

-Thanks, AB

[CR] <http://www.w3.org/TR/2012/CR-battery-status-20120508/>

On 8/28/14 1:07 PM, Frederick Hirsch wrote:
> This is a return from CR to make normative changes to address feedback raised by implementers (much appreciated). The changes include the following:
> [[
> 	 Expose BatteryManager via getBattery() returning a Promise instead of a synchronous accessor. (Section 5)
> 	 Clarify default values when a BatteryManager object is created and the implementation is unable to report the battery status information. (Section 6)
> 	 Specify the behavior when a host device has more than one battery. (Section 6.1)
> ]]
> (Links to the sections and diff are in the status section of the draft)

Received on Thursday, 28 August 2014 17:18:58 UTC