W3C home > Mailing lists > Public > public-device-apis-log@w3.org > November 2016

Re: [battery] Mitigating potential privacy-invasive usage

From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Nov 2016 06:28:11 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-258071951-1478154489-sysbot+gh@w3.org>
Agree with the motivations and goals, don't get wrong. But we are not 
talking about *all features* here, we are talking about one. We 
learned a lot from battery (that we can now apply more generally), but
 if it's being removed from browsers, we should consider rescinding it
 nonetheless. 

The question is: what UAs will continue shipping the API? and if we 
will have enough implementations to warrant continuing to push forward
 with it. 

-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at 
https://github.com/w3c/battery/issues/5#issuecomment-258071951 using 
your GitHub account
Received on Thursday, 3 November 2016 06:28:17 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:52 UTC