Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exposing battery status #172

Closed
samuelweiler opened this issue Mar 19, 2021 · 3 comments
Closed

Exposing battery status #172

samuelweiler opened this issue Mar 19, 2021 · 3 comments
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

Comments

@samuelweiler
Copy link
Member

Breaking this item out from #170. (@NalaGinrut, for tracking)

  1. About the powerEfficient field of MediaCapabilitiesInfo

A MediaCapabilitiesInfo has associated supported, smooth, powerEfficient fields which are booleans.
Authors can use powerEfficient in concordance with the Battery Status API [battery-status] in order to determine whether the media they would like to play is appropriate for the user configuration. It is worth noting that even when a device is not power constrained, high power usage has side effects such as increasing the temperature or the fans noise.

Question 1: When the powerEfficient is set to true, is it possible to expose Battery Status without users' explicit permission?

@samuelweiler samuelweiler added the privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. label Mar 19, 2021
@chcunningham
Copy link
Contributor

When the powerEfficient is set to true, is it possible to expose Battery Status without users' explicit permission?

No, the intent is that powerEfficient = true/false is independent of the current battery status. It is intended to (very roughly) describe the power draw of a given codec configurations compared to other possible codec configurations on that machine. For example, if your GPU supports H264 acceleration, but not VP9 acceleration, we may say powerEfficient = true and false respectively. But, we may also call VP9 powerEfficient at lower resolutions (say 360p or less) where hardware acceleration does not offer a power savings. Critically, none of these answers would change if you were plugged into a power source.

@samuelweiler samuelweiler added privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. and removed privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. labels Mar 29, 2021
@NalaGinrut
Copy link
Member

@chcunningham Thanks, this one is clear and done.
cc @samuelweiler

@chcunningham
Copy link
Contributor

Thanks. Please re-open if needed.

@chrisn chrisn mentioned this issue Aug 27, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Projects
None yet
Development

No branches or pull requests

3 participants