Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

HTML5 Battery Status API #1885

Closed
gameb0y opened this issue May 23, 2016 · 6 comments
Closed

HTML5 Battery Status API #1885

gameb0y opened this issue May 23, 2016 · 6 comments

Comments

@gameb0y
Copy link

gameb0y commented May 23, 2016

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/

This was referenced May 23, 2016
@diracdeltas
Copy link
Member

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)

@Dr-Infinity
Copy link

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

@luixxiul
Copy link
Contributor

luixxiul commented Aug 7, 2016

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

@luixxiul
Copy link
Contributor

luixxiul commented Aug 7, 2016

Setting a milestone for now.

@luixxiul luixxiul added this to the 0.11.4dev milestone Aug 7, 2016
@bbondy bbondy modified the milestones: 0.11.4dev, 0.11.5dev Aug 9, 2016
@luixxiul luixxiul added this to the 0.11.6dev milestone Aug 18, 2016
@bbondy bbondy modified the milestones: 1.1.0, 0.11.6dev Aug 23, 2016
@gameb0y gameb0y mentioned this issue Nov 26, 2016
@diracdeltas
Copy link
Member

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

@diracdeltas diracdeltas modified the milestones: 0.13.1, 1.1.0 Dec 1, 2016
@diracdeltas diracdeltas self-assigned this Dec 1, 2016
@cndouglas cndouglas modified the milestones: 0.13.0, 0.13.1 Dec 2, 2016
@bsclifton
Copy link
Member

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants