- From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- Date: Mon, 5 Dec 2011 13:56:44 +0200
- To: public-device-status@w3.org
[ -cc public-device-apis ] On 3.12.2011, at 1.02, ext Mounir Lamouri wrote: > On 12/02/2011 07:15 PM, Carr, Wayne wrote: >>>> If you have a full battery and disconnect your power source, the spec says to >>> report that the battery is charging -- even though it really is discharging. >>> >>> That is a bug in the specs and should be raised separately. >> >> The bug in the spec that makes it so it says charging when it is actually discharging, also seems to makes it so you can also always determine when a battery is in use. (either charging or discharging. >> >> Current text for charging attribute: "The attribute must be set to false if the battery is discharging, and set to true, if the battery is charging, full, the implementation is unable to report the state, or there is no battery attached to the system, or otherwise. >> No exceptions." >> >> Suggested text for charging attribute: "The attribute must be set to false if the battery is discharging, and set to true if the battery is charging. Otherwise, the attribute is set to true if the battery is neither charging nor discharging or If the implementation is unable to report the state or there is no battery attached to the system. No exceptions." > > Seems reasonable to me. I guess theoretically a discharging battery can't be full but in practice, depending on the battery level precision, that could happen. 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. ]] -Anssi
Received on Monday, 5 December 2011 11:57:22 UTC