List of comments on “Battery Status API” (dated 28 August 2014)

Status: allopen proposal pending resolved_yes resolved_no resolved_partial other Type: allsubstantive editorial typo question general comment undefined

Quick access to LC-2965

Comment LC-2965

Commenter: Tobie Langel <tobie.langel@gmail.com> (archived message)

Context: Document as a whole

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Anssi Kostiainen

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

Hi,

I don't understand why this API is developed separately from other sensor
APIs.

It would be much better for developers if all sensor APIs were consistent.

The API difference between DeviceOrientation and Geolocation was bad
enough. Why are we repeating such mistakes over and over again?

Sorry for the late and negative feedback.

--tobie

Related issues: (space separated ids)

WG Notes:

Resolution: Continue Battery API with current approach given we have two implementations and support for the API as-is and no significant technical issue to support a late-stage restart. Can consider alternatives for a v.next as appropriate. http://lists.w3.org/Archives/Public/public-device-apis/2014Sep/0054.html

(Please make sure the resolution is adapted for public consumption)