RE: Review of the Battery Status Event specification

Hello.  Anssi and all.

I'm Kihong Kwon and works for Samsung Electronics.
Concerning to revised draft of Battery Status Spec, I have a comment
related with dropped attribute, isCharging.

In the perspective of handset manufacturer, I think additional attribute
might be required to indicate whether a device is strongly charged or not
on the isPluged state.
Because some applications would like to do certain heavy works as a
background jobs in only strongly charged state due to battery consumption
issue.
In case that device is connected to USB port, the amount of power is a
little. So it's not appropriate time to do heavy works in background.

What do you think?

best regards,
Kihong.


---------------------------------
Kihong Kwon
Sinear Engineer
Next Generation S/W R&D Group
Mobile Communication Division
SAMSUNG ELECTRONICS CO.,LTD.
TEL : +82-10-301-0739
Mobile : +82-10-9962-2322
E-Mail : kihong.kwon@samsung.com
Twitter : @vimff
---------------------------------

-----Original Message-----
From: public-device-apis-request@w3.org [mailto:public-device-apis-
request@w3.org] On Behalf Of Anssi Kostiainen
Sent: Thursday, May 26, 2011 10:22 PM
To: ext Robin Berjon
Cc: public-device-apis@w3.org
Subject: Re: Review of the Battery Status Event specification

Hi,

On 25.5.2011, at 17.42, ext Robin Berjon wrote:

> On May 25, 2011, at 14:45 , Robin Berjon wrote:
>> we recently published a FPWD of the Battery Status Event, here are some
comments on the current draft
> 
> I forgot to ask this question: Should we indicate that the battery event
is also available on the WorkerGlobalScope in addition to Window? It would
seem to make sense.

IMHO it does make a lot of sense, because currently also some parts of the
navigator such as the onLine attribute (and the online and offline events)
are available to workers. I baked this requirement into the spec too.

-Anssi

Received on Tuesday, 31 May 2011 07:40:15 UTC