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

Re: [battery] Mitigating potential privacy-invasive usage

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Nov 2016 08:38:25 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-258087129-1478162304-sysbot+gh@w3.org>
>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.

Per http://caniuse.com/#feat=battery-status (show all) the UAs 
currently shipping include Firefox, Chrome, Opera, Android Browser, 
Opera Mobile, Chrome for Android, Firefox for Android, UC Browser for 
Android (partial), and Samsung Internet.

I feel it is my responsibility as the spec editor to keep maintaining 
and improving the specification as long as there are implementations, 
and that's why I'd like to keep this issue open.

GitHub Notification of comment by anssiko
Please view or discuss this issue at 
https://github.com/w3c/battery/issues/5#issuecomment-258087129 using 
your GitHub account
Received on Thursday, 3 November 2016 08:38:31 UTC

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