-
Notifications
You must be signed in to change notification settings - Fork 32
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
Comments
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. |
@chcunningham Thanks, this one is clear and done. |
Thanks. Please re-open if needed. |
Breaking this item out from #170. (@NalaGinrut, for tracking)
powerEfficient
field ofMediaCapabilitiesInfo
Question 1:
When thepowerEfficient
is set totrue
, is it possible to expose Battery Status without users' explicit permission?The text was updated successfully, but these errors were encountered: