Remove boomerang for gmail firefox code#
GetBattery() calls, because the way our telemetry code is written if the Of navigator.battery and 116M uses of navigator.getBattery(). In particular, looking at the actual histogram, we have about 105M uses Given document, which means that 200M number is NOT inflated by multiple Also, it counts only the first call for the Two, though) the latter would be affected by enumeration of Navigatorīut the former would not. In Firefox 49, the BATTERY_STATUS_COUNT thing counts actual calls to > the navigator object's properties without actually calling > counter be inadvertently triggered by web content that simply enumerates > surprisingly high given the few legitimate use cases. > reports that 6% of web pages use the Battery API, IIUC. The USE_COUNTER2_DEPRECATED_NavigatorBattery_PAGE probe > The BATTERY_STATUS_COUNT probe reports over 200M battery API calls Investigative reporter to confirm - could well outweigh any benefit I imagine the negative publicity if a company like Uber were caughtĪctually doing this - which seems like it wouldn't be too hard for an Uber representative is quoted as saying that "e absolutely don’t use Itĭoes suggest this -could- be done, but not that it -has- been and the The article at, however, doesn't say that. Maybe it was just me, but I initially (mis)interpreted this as a claim > inflating Uber prices for desperate users with low batteries. > world use cases, however, seem to be fingerprinting users and > battery is low, or to implement the Firefox OS settings app. > data before the battery dies, to ease off heavy computation when the > In theory, web developers would use the Battery API to save document > WebKit have signaled an intent to implement it.
> apps? Chrome and Firefox support the Battery API, but neither Edge nor > restrict it to non-web content like browser extensions or privileged web > navigator.getBattery()? Can we remove the Battery API or perhaps > What is the use case for the Battery Status API ,
Remove boomerang for gmail firefox Patch#
I have a patch that makes the Battery API chrome-only and fixes the The navigator object's properties without actually calling (Could thatĬounter be inadvertently triggered by web content that simply enumerates Surprisingly high given the few legitimate use cases. reports that 6% of web pages use the Battery API, IIUC. The BATTERY_STATUS_COUNT probe reports over 200M battery API callsįor Firefox 49. CanĪnyone point to a real website using the Battery API for a legitimate Inflating Uber prices for desperate users with low batteries. World use cases, however, seem to be fingerprinting users and In theory, web developers would use the Battery API to save documentĭata before the battery dies, to ease off heavy computation when theīattery is low, or to implement the Firefox OS settings app. WebKit have signaled an intent to implement it. Restrict it to non-web content like browser extensions or privileged webĪpps? Chrome and Firefox support the Battery API, but neither Edge nor Navigator.getBattery()? Can we remove the Battery API or perhaps What is the use case for the Battery Status API ,
0 kommentar(er)
