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

Re: Battery Status Event

From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Date: Tue, 28 Jun 2011 12:08:19 +0300
CC: Robin Berjon <robin@berjon.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <580CEB72-6AC5-4F79-9369-09E8B0809EE7@nokia.com>
To: ext Jatinder Mann <jmann@microsoft.com>

On 24.6.2011, at 21.07, ext Jatinder Mann wrote:

> As promised, we discussed the Battery Status spec in this week's Web Performance WG conference call. Based on the discussion on the call, the WG is happy with the spec. From a Web Performance perspective, we feel that giving web developers more information on the system, like battery status, will only help developers create sites that are more power conscious. We liked the simplicity of the spec and felt that it covered important aspects that would allow management based on the battery status.

Thanks for the review!

> The one question we did have was whether the initBatteryStatusEvent() was needed. I would love to understand your motivation to include it?

When dealing with user agent generated events the UA is doing this initialization step under the hood before dispatching the event. This means a typical web developer would not need to be concerned with the method. It could be useful to those web developers who wish to simulate such events. The spec is referencing the DOM Level 3 Events spec which explains this model in more detail.

Received on Tuesday, 28 June 2011 09:09:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:29 UTC