On Wed, Jun 15, 2011 at 5:58 PM, Brett Wilson <bre...@chromium.org> wrote: > On Wed, Jun 15, 2011 at 9:30 AM, Holger Freyther <ze...@selfish.org> wrote: >> On 06/15/2011 06:11 PM, laszlo.1.gom...@nokia.com wrote: >>> Hi, >>> >> >>> >>> The use-case for us is to enable content developers to implement >>> rudimentary power management (e.g. to stop "expensive" operations on the >>> page, perhaps save state). I'm not sure if this API is really meant for >>> accurately reporting all the possible power management states of the system >>> as Anssi pointed out. >> >> Okay, point on complexity taken. My question is what if you want to add >> complexity, is there something in the event that prevents that (I have no >> idea >> about DOM compatibility issues)? Don't get me wrong I think having more >> device >> support is great. >> >> My other complain was, it is too simple. E.g. 'isPlugged' has no guarantee >> that the battery is getting charged. Is this a problem? > > Why would a web page care about whether the battery is being charged > when the device is plugged in? >
Because it would know not to start doing things that drain the battery. For instance, powering up a 3G antenna to download your latest emails could be annoying to users if the battery level is too low. 3G takes quite a bit of power and the device would be in danger of powering down. Thanks, Andrei _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
