public-device-apis-log@w3.org from November 2016 by subject

[ambient-light] Is "frequency" available in ALS?

[ambient-light] Should we really redefine AmbientLightSensor.reading?

[ambient-light] What illuminance value should be reported for stopped sensor?

[battery] Mitigating potential privacy-invasive usage

[magnetometer] Provide API to access uncalibrated magnetometer values

[sensors] Call onchange only when data changes

[sensors] Exposing secondary values in the SensorReading

[sensors] granularity of Permission name for concrete/ fusion sensors

[sensors] Issues caused by visibility state restriction semantics

[sensors] Malicious use of the phone's Gyroscope

[sensors] Possibility of cross-domain communication using frequency in periodic reporting mode

[sensors] Relation to Feature Policy

[sensors] Reporting mode and polling frequency

[sensors] SensorErrorEvent IDL doesn't match Blink

[sensors] SensorReadings must be immutable.

[sensors] Should SensorReading be a dictionary?

[sensors] Should we request permission when sensor is not supported by the platform?

[sensors] Updating privacy considerations - accounting

[sensors] Using PIA terminology

[wake-lock] "System" wake lock use cases

[wake-lock] Plans for v2

[wake-lock] TAG feedback on wake-lock API

Closed: [ambient-light] Is "frequency" available in ALS?

Closed: [ambient-light] Should we really redefine AmbientLightSensor.reading?

Closed: [sensors] Add prose for on{error|change}

Closed: [sensors] Using PIA terminology

Last message date: Tuesday, 29 November 2016 16:23:11 UTC