Monday, 31 October 2016
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [sensors] Add prose for on{error|change}
- Closed: [sensors] Construct Sensor Object algorithm is doing weird things with frequency
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [sensors] Possibility of cross-domain communication using frequency in periodic reporting mode
- Re: [sensors] granularity of Permission name for concrete/ fusion sensors
- Re: [sensors] SensorReadings must be immutable.
- Re: [sensors] SensorReadings must be immutable.
- Re: [ambient-light] Security and Privacy considerations for ALS
- Closed: [ambient-light] Permissions for verbose readout of ALS
- Re: [ambient-light] Permissions for verbose readout of ALS
- [sensors] SensorReadings must be immutable.
- Re: [ambient-light] What illuminance value should be reported for stopped sensor?
- Re: [sensors] Does Sensor.stop() require user permission?
- Re: [sensors] Does Sensor.stop() require user permission?
- Re: [sensors] Does Sensor.stop() require user permission?
- Re: [sensors] Does Sensor.stop() require user permission?
- Re: [sensors] Does Sensor.stop() require user permission?
- [sensors] Does Sensor.stop() require user permission?
- Re: [sensors] Should we request permission when sensor is not supported by the platform?
- [sensors] Should we request permission when sensor is not supported by the platform?
- Re: [ambient-light] Available in workers?
- Re: [ambient-light] Available in workers?
- Re: [ambient-light] Security and Privacy considerations for ALS
- [ambient-light] Available in workers?
- Re: [ambient-light] Security and Privacy considerations for ALS
Sunday, 30 October 2016
- Re: [battery] Permission model & potential privacy-invasive usage
- Re: [wake-lock] TAG feedback on wake-lock API
Saturday, 29 October 2016
Friday, 28 October 2016
- Closed: [sensors] Should SensorReadingEvent carry reading payload?
- Re: [battery] Permission model & potential privacy-invasive usage
- Re: [sensors] Reporting mode and polling frequency
- Re: [sensors] Reporting mode and polling frequency
- Re: [sensors] Reporting mode and polling frequency
- Re: [sensors] Reporting mode and polling frequency
- Closed: [accelerometer] Rename AccelerometerReading properties to x, y, z
- Re: [sensors] Reporting mode and polling frequency
- Re: [accelerometer] Fix #9: Rename AccelerometerReading properties to x, y, z
- Re: [sensors] Reporting mode and polling frequency
- Re: [sensors] Reporting mode and polling frequency
- Closed: [sensors] Validate state transitions.
- Re: [sensors] Default sensor configuration
- Closed: [gyroscope] Rename GyroscopeReading properties to x, y, z
- Re: [sensors] Clarify terminology
- Closed: [sensors] Clarify terminology
- Closed: [sensors] start() to return a cancellable promise that resolves on first reading
- Re: [sensors] start() to return a cancellable promise that resolves on first reading
- Re: [sensors] Exposing sensors in workers and shared workers
- Re: [sensors] Validate state transitions.
- Closed: [sensors] Should we use OnErrorEventHandler error handler instead of EventHandler?
- Re: [sensors] Should we use OnErrorEventHandler error handler instead of EventHandler?
- [sensors] Privacy Impact Assesment
- Closed: [sensors] Constructing a SensorReading with SensorReadingInit is non-optional?
- Re: [sensors] Constructing a SensorReading with SensorReadingInit is non-optional?
- Re: [sensors] default sensor check during sensor construction
- Closed: [sensors] WebIDL ref label is "Level 1" but links to "Level 2"
Thursday, 27 October 2016
- Re: [sensors] Default sensor configuration
- Re: [sensors] Default sensor configuration
- Re: [sensors] SensorErrorEvent IDL doesn't match Blink
- Closed: [sensors] Naming of derivative sensors are very inconsistent
- Re: [sensors] Default sensor configuration
- Re: [sensors] Default sensor configuration
- [sensors] SensorErrorEvent IDL doesn't match Blink
- Closed: [sensors] SensorReadingEventInit's reading member needs to be required
- Closed: [sensors] Prepare licensing change in spec
- Closed: [gyroscope] API Name Objection
- Re: [gyroscope] API Name Objection
- Closed: [accelerometer] API Name Objection
- Re: [accelerometer] API Name Objection
- Re: [battery] Permission model & potential privacy-invasive usage
Wednesday, 26 October 2016
Monday, 24 October 2016
Thursday, 20 October 2016
- Re: [proximity] Fix typo in 'near' attribute and remove 'in centimeters' in 'near' attribute
- Re: [proximity] Fix typo in 'near' attribute and remove 'in centimeters' in 'near' attribute
- [vibration] ISSUE-146: Add vibration strength control
Tuesday, 18 October 2016
Monday, 17 October 2016
Tuesday, 11 October 2016
Monday, 10 October 2016
- Re: [sensors] Sensor discovery
- Re: [sensors] Sensor discovery
- Re: [sensors] Sensor discovery
- Closed: [sensors] Multiple sensor & sensor change discoverability
- Re: [sensors] Multiple sensor & sensor change discoverability
- [sensors] Multiple sensor & sensor change discoverability
Friday, 7 October 2016
- [sensors] Example code omits call to .start()
- Re: [battery] Permission model & potential privacy-invasive usage
- Re: [battery] Permission model & potential privacy-invasive usage
- Re: [battery] Permission model & potential privacy-invasive usage
Thursday, 6 October 2016
- [vibration] Accessible Platform Architectures WG feedback
- [sensors] Split construction parameters and parameters that can be changed at runtime
- [gyroscope] Rename GyroscopeReading properties to x, y, z
- [accelerometer] Rename AccelerometerReading properties to x, y, z
Tuesday, 4 October 2016
- Re: [gyroscope] Rename 'GyroscopeSensor' to 'Gyroscope'
- Re: [accelerometer] Rename AccelerometerSensor interface to Accelerometer
- Re: [gyroscope] Rename 'GyroscopeSensor' to 'Gyroscope'
- Re: [accelerometer] Rename AccelerometerSensor interface to Accelerometer
- Re: [accelerometer] Rename AccelerometerSensor interface to Accelerometer
- Re: [accelerometer] Rename AccelerometerSensor interface to Accelerometer
- Re: [accelerometer] Rename AccelerometerSensor interface to Accelerometer
- Re: [battery] Permission model & potential privacy-invasive usage
- Re: [battery] Permission model & potential privacy-invasive usage