W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2014

Re: DAP-ISSUE-166: Should getBattery() always return the same promise?

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Mon, 18 Aug 2014 13:42:34 +0000
To: Frederick Hirsch <w3c@fjhirsch.com>, "cathy.chan@nokia.com" <cathy.chan@nokia.com>, Mounir Lamouri <mounir@lamouri.fr>
CC: Device APIs Working Group <public-device-apis@w3.org>
Message-ID: <95FACF63-2814-494D-9919-45395E84FD5B@intel.com>
Hi Cathy, Frederick, All,

On 12 Aug 2014, at 00:31, Frederick Hirsch <w3c@fjhirsch.com> wrote:

> Thanks for the review, I think this editorial comment is helpful and we should update the specification to address it.

To address Cathy’s comments [1‚2] (thanks!) and to further improve the specification text, the editors landed the following changes to the specification:

* clarified the behaviour of getBattery() vis-à-vis browsing contexts [3]
* improved the BatteryManager section by moving applicable content from the Navigator section into the BatteryManager section; also defined and referenced reusable concepts [4]

With these changes we believe we have addressed any unclarity associated with ISSUE-166.

> We can continue the CfC assuming that an appropriate update will be included when we publish, (especially since you noted this at the beginning).

I suggest we continue the CfC, include these changes to the LC scheduled to be published on 28 August.

The updated draft is at [5]. We’ll prepare the LC snapshot, if we hear no concerns.

Thanks,

-Anssi

[1] http://lists.w3.org/Archives/Public/public-device-apis/2014Aug/0038.html
[2] http://lists.w3.org/Archives/Public/public-device-apis/2014Aug/0040.html
[3] https://dvcs.w3.org/hg/dap/rev/28bb4b0040eb
[4] https://dvcs.w3.org/hg/dap/rev/6808958df6d0
[5] https://dvcs.w3.org/hg/dap/raw-file/default/battery/Overview.html
Received on Monday, 18 August 2014 13:44:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:11 UTC