- From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Mar 2021 17:29:43 +0000
- To: public-device-apis-log@w3.org
> The current integration is through [w3c.github.io/sensors/#check-sensor-policy-controlled-features](https://w3c.github.io/sensors/#check-sensor-policy-controlled-features) that is called into from [w3c.github.io/accelerometer/#construct-an-accelerometer-object](https://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](https://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](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? Sounds right to me -- GitHub Notification of comment by sideshowbarker Please view or discuss this issue at https://github.com/w3c/accelerometer/pull/60#issuecomment-807145315 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 March 2021 17:29:45 UTC