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

Re: [battery] Alternative design proposal (was: addEventListener side effects, ordering & boundary crossing ...)

From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Date: Thu, 15 Sep 2011 10:53:26 +0300
Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <ECF7213F-0670-4B09-82EE-E70F4E930E59@nokia.com>
To: ext Josh Soref <jsoref@rim.com>
Hi,

On 14.9.2011, at 17.20, ext Josh Soref wrote:

> Anssi: of note, battery percentages can vary wildly if someone is amusing and swaps battery sources, a system can easily go from 100% charged to 50% charged (insert an empty battery), or from 99% charged to 33% charged (insert an empty high capacity battery). For more fun, it could go from 40% charged (kinda low), to 15% charged (insert an empty high capacity battery while trying to give more power to the system). In each of these cases, the actual amount of time remaining for the system hasn't changed, but you're going to cause any application listening to a percentage to panic.

This use case justifies the existence of battery{low|critical|ok} events.

-Anssi
Received on Thursday, 15 September 2011 07:54:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:22 GMT