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

Re: [battery] Mitigating potential privacy-invasive usage

From: Chris Peterson via GitHub <sysbot+gh@w3.org>
Date: Tue, 01 Nov 2016 16:38:19 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-257617533-1478018297-sysbot+gh@w3.org>
Limiting access to the API (to a secure context of a top-level 
document) is good. Prompting the user for permission is another 
option, though I don't think most users can make an informed decision 
about allowing access to the battery status.

Identifying the use cases for the battery API would help show where 
the API is exposing more information than necessary. For example, is 
`chargingTime` useful for a web app that would like to be polite when 
the battery is low? IIUC, the API was originally designed to implement
 the status bar and system settings app in Firefox OS, which is a 
different use case.

GitHub Notification of comment by cpeterso
Please view or discuss this issue at 
https://github.com/w3c/battery/issues/5#issuecomment-257617533 using 
your GitHub account
Received on Tuesday, 1 November 2016 16:38:25 UTC

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