- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Fri, 1 Jul 2016 10:12:27 +0200
- To: Marcos Caceres <marcos@marcosc.com>, Frederick Hirsch <w3c@fjhirsch.com>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
- Cc: W3C Device APIs WG <public-device-apis@w3.org>
Hi Marcos, >> * after discussion with the Director, the likely next step for Battery >> will be to publish an updated Proposed Recommendation (Dom in charge, >> pun intended) > > Mozilla's DOM Team is considering removing the Battery API from Gecko > because of the recent abuse by companies like Uber [1] - and because > of a lack of credible set of use cases. Abuses like that harm users > and the credibility of apps in general. Thanks for letting us know, that's indeed important information to determine our next steps. Given this, I would like to suggest that we should instead of a new Proposed Recommendation, fall back to Candidate Recommendation where we can evaluate the expected future implementations of the API, or evaluate mitigation strategies to the concerns you mentioned. Frederick, Anssi, what do you think? There is a certain amount of time sensitiveness to this: we owe the Advisory Committee an update on the Battery API (since they reviewed it as a Proposed Recommendation quite a while ago), so I would like whatever next step we choose to be put in place next week if possible. Dom > [1] http://www.independent.co.uk/life-style/gadgets-and-tech/news/uber-knows-when-your-phone-is-about-to-run-out-of-battery-a7042416.html
Received on Friday, 1 July 2016 08:12:34 UTC