[magnetometer] Should we expose heading?
Closed: [magnetometer] Why magneticFieldX instead of x?
Re: [magnetometer] Why magneticFieldX instead of x?
- Re: [magnetometer] Why magneticFieldX instead of x?
- Re: [magnetometer] Why magneticFieldX instead of x?
- Re: [magnetometer] Why magneticFieldX instead of x?
- Re: [magnetometer] Why magneticFieldX instead of x?
- Re: [magnetometer] Why magneticFieldX instead of x?
- Re: [magnetometer] Why magneticFieldX instead of x?
Re: [ambient-light] What illuminance value should be reported for stopped sensor?
[accelerometer] Address DeviceOrientation issue #4
[gyroscope] Address DeviceOrientation issue number 4
Re: [sensors] Should the enum SensorState have nosensor ?
Closed: [sensors] Does SensorReading always need a timeStamp ?
Re: [sensors] Does SensorReading always need a timeStamp ?
Re: [sensors] Constructing a SensorReading with SensorReadingInit is non-optional?
[gyroscope] Change reporting mode to "periodic"
[magnetometer] Change reporting mode to "periodic"
[accelerometer] Change reporting mode to "periodic"
[sensors] Rename "auto" reporting mode to "undefined" or "implementation specific" reporting mode.
[sensors] Add prose for on{error|change|statechange}
[sensors] Add abstract operation for constructing a SensorReading for extension specs
[sensors] Relation to Feature Policy
[sensors] granularity of Permission name for concrete/ fusion sensors
- Re: [sensors] granularity of Permission name for concrete/ fusion sensors
- Re: [sensors] granularity of Permission name for concrete/ fusion sensors
- Re: [sensors] granularity of Permission name for concrete/ fusion sensors
Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations
Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors
Re: [sensors] Should SensorReadingEvent carry reading payload?
[sensors] Naming of derivative sensors are very inconsistent
- Re: [sensors] Naming of derivative sensors are very inconsistent
- Re: [sensors] Naming of derivative sensors are very inconsistent
- Re: [sensors] Naming of derivative sensors are very inconsistent
- Re: [sensors] Naming of derivative sensors are very inconsistent
- Re: [sensors] Naming of derivative sensors are very inconsistent
[sensors] Clarify scope of generic sensor
[sensors] SensorReadingEventInit's reading member needs to be required
Closed: [sensors] Event object in error callback
Re: [sensors] Event object in error callback
[sensors] default sensor check during sensor construction
[ambient-light] API Name Objection
[magnetometer] API Name Objection
[gyroscope] API Name Objection
[accelerometer] API Name Objection
[sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Closed: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] LaughometerSensor vs Laughometer?
- Re: [sensors] Why was namespacing dropped?
- Closed: [sensors] Why was namespacing dropped?
[sensors] Default sensor configuration
- Re: [sensors] Default sensor configuration
- Re: [sensors] Default sensor configuration
- Re: [sensors] Default sensor configuration
Closed: [magnetometer] Conformance Classes
Re: [magnetometer] Conformance Classes
[accelerometer] Integration in Permission API
Re: [ambient-light] Security and Privacy considerations for ALS
Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
- Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one.
[wake-lock] "System" wake lock use cases
Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency
- Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency
- Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency
- Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency