Intent to Prototype: Battery status API gated by permissions policy

[Wang, Wei4]

Contact emails

wei4...@intel.com

Explainer

https://github.com/w3c/webappsec-permissions-policy

Specification

https://w3c.github.io/battery/#permissions-policy-integration

Summary

Battery status API gated by permissions policy provides developers with a way to control this API availability. 

Blink component

Blink>BatteryStatus

Motivation

The Battery Status API provides a way to check host device battery status. This might be important e.g. for applications which need to ensure enough power is available for completing a task. Unfortunately this kind of API can be misused for fingerprinting, profiling etc. By gating the Battery Status API using a permissions policy, developers will be able to disable this API within their applications, and in third-party components.

Initial public proposal

TAG review

TAG review status

Not applicable

Risks

Interoperability and Compatibility

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Debuggability

Is this feature fully tested by web-platform-tests?

Yes, see https://github.com/web-platform-tests/wpt/tree/master/battery-status

Flag name

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1007264

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5134470074597376

This intent message was generated by Chrome Platform Status.