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

Re: Trying to understand the Promise usage in the battery API

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Thu, 20 Aug 2015 13:01:37 +0000
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: Андрей Логвинов <alogvinov@yandex-team.ru>, Marcos Fábio Pereira <marcos.pereira@signove.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <2AD5B04D-E04E-4360-8730-C7CB71D6C8C4@intel.com>

> On 30 Jul 2015, at 18:29, Boris Zbarsky <bzbarsky@MIT.EDU> wrote:
> On 7/30/15 11:11 AM, Андрей Логвинов wrote:
>> The spec says the browser must run those tasks as soon as the relevant
>> battery state change is detected (e.g. by listening to operating system
>> events), so this is anyway the most current information the browser can
>> provide.
> It's the difference between providing the state as of the last event and the state as of the completion of the query you start when the state is asked for.  It's not a big deal, I guess, as long as the OS events fire sufficiently expeditiously.

Please let us know if you think we could clarify this in the spec prose, or whether the current text is sufficient.


Received on Thursday, 20 August 2015 13:02:09 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:06 UTC