Re: Removing the Battery Status API?

2017-04-24 Thread Anne van Kesteren
On Wed, Oct 26, 2016 at 9:30 AM, Chris Peterson wrote: > I have a patch that makes the Battery API chrome-only and fixes the > web-platform tests. We ended up landing this patch and thereby no longer expose the API to web sites in Firefox:

Re: Removing the Battery Status API?

2016-11-30 Thread Mounir Lamouri
On Tue, 29 Nov 2016, at 15:17, Boris Zbarsky wrote: > > I understand the privacy concerns, but why can't these be handled similar > > to the Geolocation API? Ask permission to use / user opts in. > > Because prompting users is generally an antipattern. If, as a user, you > got a battery API

Re: Removing the Battery Status API?

2016-11-29 Thread mail
On Tuesday, November 29, 2016 at 4:17:21 PM UTC+1, Boris Zbarsky wrote: > On 11/29/16 2:36 AM, JP de Vries wrote: > > Here's a real world use case: > > https://github.com/jpdevries/mab-recommendations/blob/low-battery/proposed/low-battery.md#-responding-to-battery-levels > > This is the

Re: Removing the Battery Status API?

2016-11-29 Thread Boris Zbarsky
On 11/29/16 2:36 AM, m...@devries.jp wrote: Here's a real world use case: https://github.com/jpdevries/mab-recommendations/blob/low-battery/proposed/low-battery.md#-responding-to-battery-levels This is the theoretical use case, yes. Is anyone actually doing this in practice, though? The

Re: Removing the Battery Status API?

2016-11-28 Thread mail
Here's a real world use case: https://github.com/jpdevries/mab-recommendations/blob/low-battery/proposed/low-battery.md#-responding-to-battery-levels An interface whose components reduce their CPU usage based on battery levels. When the battery is low maybe they lower their frame rate, hit the

Re: Removing the Battery Status API?

2016-10-26 Thread Chris Peterson
On 10/26/2016 9:21 AM, Boris Zbarsky wrote: So I decided to see what sites were doing with it. I set a breakpoint in getBattery() and tried browsing. The first site I tried loading was cnn.com, and it hit the breakpoint. It's hitting it because it's using the "boomerang" library from

Re: Removing the Battery Status API?

2016-10-26 Thread Boris Zbarsky
On 10/26/16 3:30 AM, Chris Peterson wrote: The BATTERY_STATUS_COUNT probe [4] reports over 200M battery API calls for Firefox 49. The USE_COUNTER2_DEPRECATED_NavigatorBattery_PAGE probe [5] reports that 6% of web pages use the Battery API, IIUC. That seems surprisingly high given the few

Re: Removing the Battery Status API?

2016-10-26 Thread Jonathan Kew
On 26/10/2016 08:30, Chris Peterson wrote: What is the use case for the Battery Status API [0], navigator.getBattery()? Can we remove the Battery API or perhaps restrict it to non-web content like browser extensions or privileged web apps? Chrome and Firefox support the Battery API, but neither

Re: Removing the Battery Status API?

2016-10-26 Thread Gijs Kruitbosch
On 26/10/2016 08:54, Anne van Kesteren wrote: On Wed, Oct 26, 2016 at 9:30 AM, Chris Peterson wrote: (Could that counter be inadvertently triggered by web content that simply enumerates the navigator object's properties without actually calling navigator.getBattery()?)

Re: Removing the Battery Status API?

2016-10-26 Thread Anne van Kesteren
On Wed, Oct 26, 2016 at 9:30 AM, Chris Peterson wrote: > (Could that counter be > inadvertently triggered by web content that simply enumerates the navigator > object's properties without actually calling navigator.getBattery()?) That seems unlikely given it's a method so

Removing the Battery Status API?

2016-10-26 Thread Chris Peterson
What is the use case for the Battery Status API [0], navigator.getBattery()? Can we remove the Battery API or perhaps restrict it to non-web content like browser extensions or privileged web apps? Chrome and Firefox support the Battery API, but neither Edge nor WebKit have signaled an intent