Re: [battery] CfC to update Battery with async/promises proposal (implies LC return); deadline 22 May 2014.

+1
We at Google strongly support this update to the Battery Status API
specification.
We are also currently preparing a more detailed text version of the
proposed change which I will circulate on this list.

thanks,
Tim

On Thu, May 15, 2014 at 7:30 PM, Frederick Hirsch <w3c@fjhirsch.com> wrote:

> This is a Call for Consensus to  change update the Battery specification
> with the async proposal as outlined in
> http://lists.w3.org/Archives/Public/public-device-apis/2014Apr/0037.html
>
> Quoting that proposal:
>
> [[
>
> the proposal is to return the battery object asynchronously
> as a promise, e.g.
>
> function onBatterySuccess(battery) {
>   console.log(batery.level);
> }
> function onBatteryFailure(msg) {
>   console.log("battery information not available");
> }
> navigator.getBattery().then(onBatterySuccess, onBatteryFailure);
>
> ]]
>
> In addition, this CfC includes the decision that this API returns
> aggregated energy - if information were needed about multiple batteries
> individually that would require another API (see
> http://lists.w3.org/Archives/Public/public-device-apis/2014May/0001.html )
>
> Approval of this CfC will subsequently require a detailed set of changes
> to the text of the specification, a return to Last Call and then CR and
> revised implementation/interop test support for progressing the revised
> specification. Implementers indicating support for the CfC would be most
> valuable.
>
> Please respond to this CfC on the public list indicating support or any
> concern with the change (even a +1 in support is helpful). No response will
> be taken as signifying  agreement.
>
> Please respond by next Thursday, 22 May 2014.
>
> Thanks
>
> regards, Frederick
>
> Frederick Hirsch, Nokia
> Chair XML Security WG
>
> For tracker, this will complete ACTION-691
>
>
>