- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Feb 2019 12:22:57 +0000
- To: public-device-apis-log@w3.org
anssiko has just created a new issue for https://github.com/w3c/sensors: == Define the default allowlist normatively == The constructors of concrete sensor specs invoke "Construct a FooSensor object" abstract operation (e.g. [accelerometer](https://w3c.github.io/accelerometer/#construct-an-accelerometer-object) and [gyroscope](https://w3c.github.io/gyroscope/#construct-a-gyroscope-object)) that in turn invokes [Check sensor policy-controlled features](https://w3c.github.io/sensors/#check-sensor-policy-controlled-features) defined in the Generic Sensor API. These abstract operations take care of Feature Policy integration as specified in the [Extending the Feature Policy API](https://w3c.github.io/sensors/#feature-policy-api) section of the Generic Sensor API except that the default allowlist is not normatively defined. It is defined in the above-mentioned non-normative section of the Generic Sensor API as follow: >The features' default allowlist is ["self"]. A proposed fix would be to make this text normative by moving it into the normative [Sensor](https://w3c.github.io/sensors/#model-sensor) section. Please view or discuss this issue at https://github.com/w3c/sensors/issues/382 using your GitHub account
Received on Friday, 8 February 2019 12:22:59 UTC