Browser-laptop: HTML5 Battery Status API

Created on 23 May 2016  Â·  6Comments  Â·  Source: brave/browser-laptop

The API does not require user permission to read the battery information, any website or third-party scripts included on them, can use the API. The API also does not require browsers to notify users when the battery information is accessed. That allows website and third-party scripts to access the battery information transparently – without users’ awareness.

http://techcrunch.com/2015/08/04/battery-attributes-can-be-used-to-track-web-users/

Qno-qa-needed privacy release-noteinclude security

Most helpful comment

lukasz and i had talked in 2015 about addressing this at the W3C spec level; it appears that this is now addressed in https://w3c.github.io/battery/#security-and-privacy-considerations but we should fix without waiting for upstream changes.

options are:

  1. completely disable this API, as tor browser does
  2. disable it only in private browsing mode
  3. ask for user permission always

i'm inclined to go with (3)

All 6 comments

lukasz and i had talked in 2015 about addressing this at the W3C spec level; it appears that this is now addressed in https://w3c.github.io/battery/#security-and-privacy-considerations but we should fix without waiting for upstream changes.

options are:

  1. completely disable this API, as tor browser does
  2. disable it only in private browsing mode
  3. ask for user permission always

i'm inclined to go with (3)

My understanding of Brave's philosophy is to put the user in control.
Thus, I agree with diracdeltas choice of 3.
"Ask for user permission always" should be Brave's motto.
"Licentiam petere a user semper" from Google translate.
A little clunky..
"Always ask permission" yields "Semper licentia." from Google translate.
Pithy and appropriate.
c2

The API is said to being used to track users already.
https://www.smashingmagazine.com/2016/08/web-development-reading-list-148/#privacy

Setting a milestone for now.

FF and webkit have removed this feature already. Chromium has an open issue for it, but I don't think we should wait for them. https://bugs.chromium.org/p/chromium/issues/detail?id=661792

Awesome! Should be in our next version; Enjoy, @gameb0y :smile:

Was this page helpful?
0 / 5 - 0 ratings