Closed sideshowbarker closed 3 years ago
@sideshowbarker, thanks!
The current integration is through https://w3c.github.io/sensors/#check-sensor-policy-controlled-features that is called into from https://w3c.github.io/accelerometer/#construct-an-accelerometer-object (and other sensor APIs that inherit from Sensor
).
The feature strings are defined in https://w3c.github.io/permissions/#permission-registry
It seems if we'd make the following default allowlist normative in the Generic Sensor API (from https://w3c.github.io/sensors/#permissions-policy-api):
The features' default allowlist is ["self"].
... that'd satisfy this requirement without needing to add a Permissions Policy Integration section into each concrete sensor API spec?
@reillyeon @clelland for review of the idea.
The current integration is through w3c.github.io/sensors/#check-sensor-policy-controlled-features that is called into from w3c.github.io/accelerometer/#construct-an-accelerometer-object (and other sensor APIs that inherit from
Sensor
).The feature strings are defined in w3c.github.io/permissions/#permission-registry
aha — thanks
It seems if we'd make the following default allowlist normative in the Generic Sensor API (from w3c.github.io/sensors/#permissions-policy-api):
The features' default allowlist is ["self"].
... that'd satisfy this requirement without needing to add a Permissions Policy Integration section into each concrete sensor API spec?
Sounds right to me
Preview | Diff