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: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Fri, 2 Dec 2011 20:07:44 +0000
To: "olli@pettay.fi" <olli@pettay.fi>
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>
Message-ID: <84BCA539DD96614691177EDA3CE4FF05240755EA@ORSMSX102.amr.corp.intel.com>
Fine, then the current "charging" attribute is unclear with respect to if you don't have a battery or a bad battery. The case of on a desktop system where there is no battery, what should this attribute set to true or false?


-----Original Message-----
From: Olli Pettay [mailto:Olli.Pettay@helsinki.fi] 
Sent: Friday, December 02, 2011 12:01 PM
To: Tran, Dzung D
Cc: Josh Soref; Carr, Wayne; mounir@lamouri.fr; dom@w3.org; public-device-apis@w3.org
Subject: Re: no longer possible to detect battery presence? RE: Battery API in Last Call

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:08:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:46:06 UTC