W3C home > Mailing lists > Public > public-device-status@w3.org > December 2011

RE: charging attribute (was: Re: no longer possible to detect battery presence? RE: Battery API in Last Call)

From: Carr, Wayne <wayne.carr@intel.com>
Date: Wed, 7 Dec 2011 21:44:18 +0000
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>, "public-device-status@w3.org" <public-device-status@w3.org>
Message-ID: <52F8A45B68FD784E8E4FEE4DA9C6E52A2404DD19@ORSMSX102.amr.corp.intel.com>
That's good. Thanks.

>-----Original Message-----
>From: Anssi Kostiainen [mailto:anssi.kostiainen@nokia.com]
>Sent: Wednesday, December 07, 2011 12:01 AM
>To: public-device-status@w3.org; Carr, Wayne
>Subject: Re: charging attribute (was: Re: no longer possible to detect battery
>presence? RE: Battery API in Last Call)
>
>Hi Wayne, All,
>
>On 5.12.2011, at 19.33, ext Carr, Wayne wrote:
>
>>> Wouldn't dropping "full" from the true condition fix this.
>>> "Otherwise" will catch the case "neither charging nor discharging". My
>proposal:
>>>
>>> [[
>>>
>>> charging of type boolean, readonly
>>>
>>> Represents if the system's battery is charging. The attribute must be
>>> set to false if the battery is discharging, and set to true, if the
>>> battery is charging, the implementation is unable to report the
>>> state, or there is no battery attached to the system, or otherwise.
>>>
>>> ]]
>>
>> That would do it.
>
>I updated the spec accordingly. Let me know if there are concerns with this
>change.
>
>-Anssi
>

Received on Wednesday, 7 December 2011 21:44:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 December 2011 21:44:55 GMT