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

Alexander Shalamov via GitHub

• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 15 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• [magnetometer] Provide API to access uncalibrated magnetometer values (Thursday, 3 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Tuesday, 1 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Tuesday, 1 November)

Andrey Logvinov via GitHub

• [wake-lock] Plans for v2 (Tuesday, 29 November)
• Re: [wake-lock] TAG feedback on wake-lock API (Thursday, 3 November)

André Cipriani Bandarra via GitHub

• Re: [wake-lock] "System" wake lock use cases (Thursday, 17 November)

Anne van Kesteren via GitHub

• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)

Anssi Kostiainen via GitHub

• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Friday, 4 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Thursday, 3 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Thursday, 3 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Thursday, 3 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Thursday, 3 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Wednesday, 2 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Wednesday, 2 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Tuesday, 1 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Tuesday, 1 November)

Chris Peterson via GitHub

• Re: [battery] Mitigating potential privacy-invasive usage (Tuesday, 1 November)

Dominique Hazael-Massieux via GitHub

• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)

Lukasz Olejnik via GitHub

• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 22 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 22 November)
• Re: [sensors] Relation to Feature Policy (Wednesday, 16 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Thursday, 3 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Wednesday, 2 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Wednesday, 2 November)
• Re: [sensors] Updating privacy considerations - accounting (Tuesday, 1 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 1 November)
• [sensors] Updating privacy considerations - accounting (Tuesday, 1 November)
• Re: [sensors] Possibility of cross-domain communication using frequency in periodic reporting mode (Tuesday, 1 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 1 November)
• Re: [sensors] SensorReadings must be immutable. (Tuesday, 1 November)

Marcos Cáceres via GitHub

• Re: [battery] Mitigating potential privacy-invasive usage (Friday, 4 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Thursday, 3 November)
• Re: [battery] Mitigating potential privacy-invasive usage (Thursday, 3 November)

Maryam Mehr via GitHub

• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Monday, 14 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Monday, 14 November)
• Re: [sensors] Relation to Feature Policy (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 8 November)
• Re: [sensors] Malicious use of the phone's Gyroscope (Tuesday, 8 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 8 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 8 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 8 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 8 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 8 November)

maryammjd via GitHub

• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 8 November)

Mikhail Pozdnyakov via GitHub

• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Friday, 18 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Wednesday, 16 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Call onchange only when data changes (Friday, 11 November)
• Re: [sensors] Call onchange only when data changes (Friday, 11 November)
• Re: [sensors] Call onchange only when data changes (Friday, 11 November)
• [sensors] Call onchange only when data changes (Friday, 11 November)
• Re: [sensors] SensorErrorEvent IDL doesn't match Blink (Thursday, 10 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Tuesday, 1 November)

Owen Campbell-Moore via GitHub

• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 22 November)

Philip Jägenstedt via GitHub

• Re: [sensors] SensorErrorEvent IDL doesn't match Blink (Thursday, 10 November)
• Re: [sensors] SensorErrorEvent IDL doesn't match Blink (Thursday, 10 November)

raymeskhoury via GitHub

• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 22 November)

Rick Waldron via GitHub

• Re: [sensors] Exposing secondary values in the SensorReading (Wednesday, 16 November)
• Re: [sensors] Call onchange only when data changes (Wednesday, 16 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Wednesday, 16 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Tuesday, 15 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 15 November)
• Re: [sensors] Call onchange only when data changes (Tuesday, 15 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 15 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Tuesday, 15 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 15 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Friday, 4 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Wednesday, 2 November)
• [sensors] Issues caused by visibility state restriction semantics (Wednesday, 2 November)

Rijubrata Bhaumik via GitHub

• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Thursday, 3 November)

Tobie Langel via GitHub

• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Wednesday, 23 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 22 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Friday, 18 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Friday, 18 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Wednesday, 16 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Wednesday, 16 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Wednesday, 16 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Call onchange only when data changes (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Tuesday, 15 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 15 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Tuesday, 15 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Tuesday, 15 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Monday, 14 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Monday, 14 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Monday, 14 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Monday, 14 November)
• Re: [sensors] Relation to Feature Policy (Monday, 14 November)
• Re: [sensors] Should we request permission when sensor is not supported by the platform? (Monday, 14 November)
• Re: [sensors] Call onchange only when data changes (Friday, 11 November)
• Re: [sensors] Call onchange only when data changes (Friday, 11 November)
• Re: [sensors] Call onchange only when data changes (Friday, 11 November)
• Re: [sensors] SensorErrorEvent IDL doesn't match Blink (Thursday, 10 November)
• Re: [sensors] SensorErrorEvent IDL doesn't match Blink (Thursday, 10 November)
• Re: [ambient-light] Is "frequency" available in ALS? (Wednesday, 9 November)
• Re: [sensors] Reporting mode and polling frequency (Wednesday, 9 November)
• Re: [sensors] Exposing secondary values in the SensorReading (Tuesday, 8 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 8 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 8 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 8 November)
• Closed: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• [sensors] Exposing secondary values in the SensorReading (Tuesday, 8 November)
• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• Re: [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• [sensors] Should SensorReading be a dictionary? (Tuesday, 8 November)
• [ambient-light] Should we really redefine AmbientLightSensor.reading? (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 8 November)
• Re: [sensors] Issues caused by visibility state restriction semantics (Monday, 7 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Friday, 4 November)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Thursday, 3 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Wednesday, 2 November)
• Re: [sensors] Using PIA terminology (Wednesday, 2 November)
• Closed: [sensors] Using PIA terminology (Wednesday, 2 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 1 November)
• Re: [sensors] Updating privacy considerations - accounting (Tuesday, 1 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Tuesday, 1 November)
• Closed: [sensors] Add prose for on{error|change} (Tuesday, 1 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Tuesday, 1 November)
• Re: [sensors] Updating privacy considerations - accounting (Tuesday, 1 November)
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors (Tuesday, 1 November)
• Re: [sensors] SensorReadings must be immutable. (Tuesday, 1 November)
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? (Tuesday, 1 November)

Wanming Lin via GitHub

• Re: [ambient-light] Is "frequency" available in ALS? (Thursday, 10 November)
• Closed: [ambient-light] Is "frequency" available in ALS? (Thursday, 10 November)
• [ambient-light] Is "frequency" available in ALS? (Wednesday, 9 November)

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