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: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Fri, 02 Dec 2011 22:00:41 +0200
Message-ID: <4ED92E69.7080403@helsinki.fi>
To: "Tran, Dzung D" <dzung.d.tran@intel.com>
CC: Josh Soref <jsoref@rim.com>, "Carr, Wayne" <wayne.carr@intel.com>, "mounir@lamouri.fr" <mounir@lamouri.fr>, "dom@w3.org" <dom@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>
On 12/02/2011 09:56 PM, Tran, Dzung D wrote:
> This is a battery spec, so you would only use it if it is on a mobile
> device. One can use User agent string to determine if you are on a
> mobile device.

No. One shouldn't need to check UA string before using the API.


>
> Otherwise, might consider to change this attribute to a “state”
> attribute of enumerated type of (charging, discharging,undefined).
>
> Thanks
>
> Tran
>
> *From:*Josh Soref [mailto:jsoref@rim.com]
> *Sent:* Friday, December 02, 2011 11:37 AM
> *To:* Tran, Dzung D; Carr, Wayne; mounir@lamouri.fr
> *Cc:* olli@pettay.fi; dom@w3.org; public-device-apis@w3.org;
> public-device-status@w3.org
> *Subject:* Re: no longer possible to detect battery presence? RE:
> Battery API in Last Call
>
> 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 20:01:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:26 GMT