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

Re: no longer possible to detect battery presence? RE: Battery API in Last Call

From: Josh Soref <jsoref@rim.com>
Date: Fri, 2 Dec 2011 19:37:27 +0000
To: "dzung.d.tran@intel.com" <dzung.d.tran@intel.com>, "wayne.carr@intel.com" <wayne.carr@intel.com>, "mounir@lamouri.fr" <mounir@lamouri.fr>
CC: "olli@pettay.fi" <olli@pettay.fi>, "dom@w3.org" <dom@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>, "public-device-status@w3.org" <public-device-status@w3.org>
Message-ID: <957F1ECDA90E004B8DBDE23CFC94E3A311650F7F@XMB103ECNC.rim.net>
Tran wrote:
> to something:
> 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. If the battery status cannot be determined, the implementation should raise an error or an undefined state.

Absolutely not.

The average case is that I'm on a desktop. We do *not* want average cases to trigger exceptions. Nor do we want them not to work.

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Friday, 2 December 2011 19:38:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:52 UTC