Edit comment LC-2965 for Device and Sensors Working Group

Quick access to LC-2965

Comment LC-2965

Comment Shortname:

Commenter:

On Behalf Of:

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeBattery Status API W3C Last Call Working Draft 28 August... Battery Status API W3C Last Call Working Draft 28 August 2... Battery Status API W3C Last Call Working Draft 28 August 2014 Abstract This specification defines an API that provides in... Abstract Status of This Document This section describes the status o... Status of This Document 5 February 2004 W3C Patent Policy 14 October 2005 W3C Process Document Table of Contents 1. Introduction 2. Conformance 3. Termin... Table of Contents 1. Introduction 2. Conformance 3. Terminology 4. Security a... 1. Introduction This section is non-normative. The Battery... 1. Introduction 2. Conformance As well as sections marked as non-normative,... 2. Conformance user agent 3. Terminology The following concepts, terms and interfaces... 3. Terminology queue a task fires a simple event event handlers event handler event types browsing context Promise 4. Security and privacy considerations This section is non-... 4. Security and privacy considerations 5. The Navigator interface partial interface Navigator {... 5. The Navigator interface partial interface Navigator { Promise<BatteryManager> ge... battery promise getBattery() Resolve 6. The BatteryManager interface The BatteryManager interfac... 6. The BatteryManager interface current battery status information interface BatteryManager : EventTarget { readonly att... create a new BatteryManager object default values unable to report the battery status information Note charging chargingTime dischargingTime level Note 6.1 Multiple batteries If a hosting device contains more th... 6.1 Multiple batteries 6.2 Event handlers The following are the event handlers (an... 6.2 Event handlers onchargingchange chargingchange onchargingtimechange chargingtimechange ondischargingtimechange dischargingtimechange onlevelchange levelchange 7. Examples This section is non-normative. This trivial exa... 7. Examples A. Acknowledgements The group is deeply indebted to Mounir... A. Acknowledgements B. References B.1 Normative references [ECMASCRIPT] ECMA-... B. References B.1 Normative references [ECMASCRIPT] ECMA-262 ECMAScript... B.1 Normative references [ECMASCRIPT] [HTML5] [RFC2119] [WEBIDL]
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody Bah, Slimane Bernhart, Bryan Bhaumik, Rijubrata Bogdanovich, Ilya Caceres, Marcos Christiansen, Kenneth DADAS, Mohammed Gouaillard, Alexandre Grant, Reilly Hazaël-Massieux, Dominique Hirsch, Frederick Hu, Ningxin huang, qigang Hwang, Dongseong Jeon, Jonathan Kang, Shin-Gak Kim, Sung Hei Kim, Sunghan Kinlan, Paul Kis, Zoltan Kliche, Ingmar Kollarova, Martina Kostiainen, Anssi Krishnan, Sanjay Lamouri, Mounir Lee, Dong-Young Lee, Kangchan Lee, Seungyun Lee, WonSuk Lin, Wanming Liu, Dapeng Liu, Guanyu Logvinov, Andrey Mandyam, Giridhar McCathie Nevile, Charles Mehrnezhad, Maryam Mikityuk, Alexandra Nilsson, Claes Olejnik, Lukasz Pashidis, Michallis Poussa, Sakari Pozdnyakov, Mikhail Raggett, Dave Scheib, Vincent Shalamov, Alexander Song, Jungkee Spreitzer, Raphael Steglich, Stephan Stojiljkovic, Aleksandar Tran, Dzung Waldron, Rick Walsh, Michael WEI, XIAOHAI xiong, aiden Xue, Fuqiao Yamamoto, Eiji Yamazaki, Fumi Zhang, Rong Zhang, Zhiqiang zhong, heng

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)

Check to confirm deletion (not reversible)