public-device-apis-log@w3.org from September 2016 by date

Wednesday, 28 September 2016

• Re: [sensors] Clarify scope of generic sensor Lukasz Olejnik via GitHub

Tuesday, 27 September 2016

• [magnetometer] Should we expose heading? Anssi Kostiainen via GitHub
• Closed: [gyroscope] API Name Objection Rijubrata Bhaumik via GitHub
• Closed: [magnetometer] API Name Objection Rijubrata Bhaumik via GitHub
• Closed: [accelerometer] API Name Objection Rijubrata Bhaumik via GitHub

Thursday, 22 September 2016

• Re: [magnetometer] Why magneticFieldX instead of x? Rick Waldron via GitHub
• Closed: [magnetometer] Why magneticFieldX instead of x? Rijubrata Bhaumik via GitHub
• Closed: [accelerometer] Change reporting mode to "periodic" Rijubrata Bhaumik via GitHub
• Closed: [gyroscope] Change reporting mode to "periodic" Rijubrata Bhaumik via GitHub
• Closed: [magnetometer] Change reporting mode to "periodic" Rijubrata Bhaumik via GitHub

Wednesday, 21 September 2016

• Re: [sensors] Default sensor configuration Mikhail Pozdnyakov via GitHub
• Re: [magnetometer] Why magneticFieldX instead of x? Anssi Kostiainen via GitHub
• Re: [magnetometer] Why magneticFieldX instead of x? Marcos Cáceres via GitHub

Tuesday, 20 September 2016

• Re: [magnetometer] Why magneticFieldX instead of x? Rick Waldron via GitHub
• Re: [magnetometer] Why magneticFieldX instead of x? Rick Waldron via GitHub
• Re: [magnetometer] Why magneticFieldX instead of x? Rick Waldron via GitHub
• Re: [magnetometer] Why magneticFieldX instead of x? Anssi Kostiainen via GitHub
• Re: [ambient-light] What illuminance value should be reported for stopped sensor? Anssi Kostiainen via GitHub
• [accelerometer] Address DeviceOrientation issue #4 Tobie Langel via GitHub
• [gyroscope] Address DeviceOrientation issue number 4 Tobie Langel via GitHub
• Re: [sensors] Should the enum SensorState have nosensor ? Tobie Langel via GitHub
• Closed: [sensors] Does SensorReading always need a timeStamp ? Anssi Kostiainen via GitHub
• Re: [sensors] Does SensorReading always need a timeStamp ? Anssi Kostiainen via GitHub
• Re: [sensors] Default sensor configuration Tobie Langel via GitHub
• Re: [sensors] Default sensor configuration Tobie Langel via GitHub
• Re: [sensors] Constructing a SensorReading with SensorReadingInit is non-optional? Anssi Kostiainen via GitHub
• [gyroscope] Change reporting mode to "periodic" Anssi Kostiainen via GitHub
• [magnetometer] Change reporting mode to "periodic" Anssi Kostiainen via GitHub
• [accelerometer] Change reporting mode to "periodic" Anssi Kostiainen via GitHub
• [sensors] Rename "auto" reporting mode to "undefined" or "implementation specific" reporting mode. Tobie Langel via GitHub
• Re: [magnetometer] API Name Objection Tobie Langel via GitHub
• Re: [accelerometer] API Name Objection Tobie Langel via GitHub
• Re: [gyroscope] API Name Objection Tobie Langel via GitHub
• Re: [ambient-light] API Name Objection Tobie Langel via GitHub
• Closed: [sensors] Why was namespacing dropped? Tobie Langel via GitHub
• Re: [sensors] Why was namespacing dropped? Tobie Langel via GitHub
• Re: [sensors] Naming of derivative sensors are very inconsistent Anssi Kostiainen via GitHub
• Re: [sensors] Naming of derivative sensors are very inconsistent Anssi Kostiainen via GitHub
• Re: [sensors] Naming of derivative sensors are very inconsistent Kenneth Rohde Christiansen via GitHub
• [sensors] Add prose for on{error|change|statechange} Anssi Kostiainen via GitHub
• [sensors] Add abstract operation for constructing a SensorReading for extension specs Anssi Kostiainen via GitHub
• Re: [sensors] Naming of derivative sensors are very inconsistent Tobie Langel via GitHub

Monday, 19 September 2016

• Re: [sensors] Clarify scope of generic sensor Rick Waldron via GitHub
• Re: [sensors] Naming of derivative sensors are very inconsistent Rick Waldron via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Rick Waldron via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Tobie Langel via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Rick Waldron via GitHub
• [sensors] Relation to Feature Policy Dominique Hazael-Massieux via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Tobie Langel via GitHub
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors Lukasz Olejnik via GitHub
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors Rijubrata Bhaumik via GitHub
• Re: [sensors] granularity of Permission name for concrete/ fusion sensors Anssi Kostiainen via GitHub
• [sensors] granularity of Permission name for concrete/ fusion sensors Rijubrata Bhaumik via GitHub
• Re: [sensors] Simplify extension of the Permissions API for concrete sensor implementations Anssi Kostiainen via GitHub
• Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Should SensorReadingEvent carry reading payload? Dominique Hazael-Massieux via GitHub
• [sensors] Naming of derivative sensors are very inconsistent Kenneth Rohde Christiansen via GitHub
• [sensors] Clarify scope of generic sensor Dominique Hazael-Massieux via GitHub

Thursday, 15 September 2016

• Re: [sensors] LaughometerSensor vs Laughometer? Rijubrata Bhaumik via GitHub
• [sensors] SensorReadingEventInit's reading member needs to be required Philip Jägenstedt via GitHub
• Closed: [sensors] Event object in error callback Anssi Kostiainen via GitHub
• Re: [sensors] Event object in error callback Anssi Kostiainen via GitHub

Wednesday, 14 September 2016

• Re: [sensors] LaughometerSensor vs Laughometer? Domenic Denicola via GitHub
• [sensors] default sensor check during sensor construction Mikhail Pozdnyakov via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Marcos Cáceres via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Anssi Kostiainen via GitHub

Tuesday, 13 September 2016

• Re: [sensors] LaughometerSensor vs Laughometer? Rick Waldron via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Anssi Kostiainen via GitHub
• Closed: [sensors] LaughometerSensor vs Laughometer? Anssi Kostiainen via GitHub
• Re: [sensors] LaughometerSensor vs Laughometer? Anssi Kostiainen via GitHub
• [ambient-light] API Name Objection Rick Waldron via GitHub
• [magnetometer] API Name Objection Rick Waldron via GitHub
• [gyroscope] API Name Objection Rick Waldron via GitHub
• [accelerometer] API Name Objection Rick Waldron via GitHub
• [sensors] LaughometerSensor vs Laughometer? Rick Waldron via GitHub
• [sensors] Default sensor configuration Mikhail Pozdnyakov via GitHub
• Closed: [magnetometer] Conformance Classes Anssi Kostiainen via GitHub
• Re: [magnetometer] Conformance Classes Anssi Kostiainen via GitHub

Monday, 12 September 2016

• [accelerometer] Integration in Permission API Dominique Hazael-Massieux via GitHub

Tuesday, 6 September 2016

• Re: [wake-lock] "System" wake lock use cases Marcos Cáceres via GitHub
• Re: [wake-lock] "System" wake lock use cases Marcos Cáceres via GitHub

Monday, 5 September 2016

• Re: [ambient-light] Security and Privacy considerations for ALS Anssi Kostiainen via GitHub
• Re: [wake-lock] TAG feedback on wake-lock API Andrey Logvinov via GitHub

Friday, 2 September 2016

• Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency Tobie Langel via GitHub
• Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency Boris Zbarsky via GitHub
• Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency Tobie Langel via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Tobie Langel via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Alexander Shalamov via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Tobie Langel via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Tobie Langel via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Alexander Shalamov via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Tobie Langel via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Tobie Langel via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Alexander Shalamov via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Tobie Langel via GitHub
• Re: [accelerometer] includeGravity parameter turns low-level sensor into high-level fused one. Anssi Kostiainen via GitHub
• [wake-lock] "System" wake lock use cases Andrew Betts via GitHub

Thursday, 1 September 2016

• Re: [sensors] https://w3c.github.io/sensors/#construct-sensor-object is doing weird things with frequency Rick Waldron via GitHub
• [wake-lock] TAG feedback on wake-lock API Travis Leithead via GitHub

Last message date: Wednesday, 28 September 2016 15:25:39 UTC