public-device-apis-log@w3.org from January 2017 by date

Tuesday, 31 January 2017

• Re: [sensors] Reading attributes at different sensor states Mikhail Pozdnyakov via GitHub
• Re: [sensors] Reading attributes at different sensor states Tobie Langel via GitHub
• Re: [sensors] Reading attributes at different sensor states Mikhail Pozdnyakov via GitHub
• Re: [sensors] Reading attributes at different sensor states Tobie Langel via GitHub
• [sensors] Reading attributes at different sensor states Mikhail Pozdnyakov via GitHub
• Re: [gyroscope] Adapt Gyroscope to the latest changes in the Generic Sensor API Mikhail Pozdnyakov via GitHub

Monday, 30 January 2017

• Re: [html-media-capture] VideoFacingModeEnum as the capture attribute's value Anssi Kostiainen via GitHub
• Closed: [sensors] Meta: figure out why travis fails for pull requests Tobie Langel via GitHub
• Re: [sensors] Add script to easily publish to /TR/. Dominique Hazael-Massieux via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Add script to easily publish to /TR/. Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Mikhail Pozdnyakov via GitHub
• Re: [sensors] Add script to easily publish to /TR/. Dominique Hazael-Massieux via GitHub
• Re: [sensors] Add script to easily publish to /TR/. Tobie Langel via GitHub
• Re: [wake-lock] "System" wake lock use cases Andrew Betts via GitHub
• Closed: [wake-lock] "System" wake lock use cases Andrew Betts via GitHub
• Re: [wake-lock] TAG feedback on wake-lock API Dominique Hazael-Massieux via GitHub
• Re: [wake-lock] "System" wake lock use cases Dominique Hazael-Massieux via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Mikhail Pozdnyakov via GitHub
• Re: [wake-lock] The spec is unnecessarily strict in regard to promise handling Marcos Cáceres via GitHub

Saturday, 28 January 2017

• Closed: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Tobie Langel via GitHub

Friday, 27 January 2017

• Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Alexis Menard via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Mikhail Pozdnyakov via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Kenneth Rohde Christiansen via GitHub
• Closed: [sensors] Fix Sensor.start() operation description Mikhail Pozdnyakov via GitHub
• Re: [sensors] Fix Sensor.start() operation description Mikhail Pozdnyakov via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Mikhail Pozdnyakov via GitHub
• Re: [sensors] Find a better name for 'unconnected' state Tobie Langel via GitHub
• Re: [sensors] Fix Sensor.start() operation description Tobie Langel via GitHub
• Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Tobie Langel via GitHub
• Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Tobie Langel via GitHub
• Re: [sensors] latest reading should be declarted as an internal slot Tobie Langel via GitHub
• Re: [sensors] latest reading should be declarted as an internal slot Mikhail Pozdnyakov via GitHub
• Closed: [sensors] Sensor.timestamp must be nullable Tobie Langel via GitHub
• Re: [sensors] latest reading should be declarted as an internal slot Tobie Langel via GitHub
• Re: [sensors] latest reading should be declarted as an internal slot Mikhail Pozdnyakov via GitHub
• Re: [sensors] Make timestamp nullable Mikhail Pozdnyakov via GitHub
• Re: [sensors] latest reading should be declarted as an internal slot Tobie Langel via GitHub
• Re: [sensors] latest reading should be declarted as an internal slot Tobie Langel via GitHub
• [sensors] latest reading should be declarted as internal slot Mikhail Pozdnyakov via GitHub
• [sensors] Fix Sensor.start() operation description Mikhail Pozdnyakov via GitHub
• [sensors] Find a better name for 'unconnected' state Mikhail Pozdnyakov via GitHub
• [sensors] Sensor.timestamp must be nullable Mikhail Pozdnyakov via GitHub
• Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Mikhail Pozdnyakov via GitHub
• Re: [wake-lock] chore: fix ReSpec warnings (closes #91) Marcos Cáceres via GitHub
• Closed: [wake-lock] Fix respec warnings Andrey Logvinov via GitHub
• Re: [wake-lock] chore: fix ReSpec warnings (closes #91) Andrey Logvinov via GitHub

Thursday, 26 January 2017

• Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Kenneth Rohde Christiansen via GitHub
• Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Alexis Menard via GitHub
• [sensors] DOMExceptions when calling stop/start on already stopped/started sensor Alexis Menard via GitHub
• Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications Tobie Langel via GitHub
• Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications lukes3315 via GitHub
• Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications lukes3315 via GitHub
• Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications Tobie Langel via GitHub
• Closed: [sensors] Frequency readout allows fingerprinting sensors, privacy. Tobie Langel via GitHub
• Re: [sensors] Malicious use of the phone's Gyroscope Tobie Langel via GitHub
• Closed: [sensors] Malicious use of the phone's Gyroscope Tobie Langel via GitHub
• Re: [sensors] Updating privacy considerations - accounting Tobie Langel via GitHub
• Closed: [sensors] Updating privacy considerations - accounting Tobie Langel via GitHub
• Closed: [sensors] Revoking user permission Tobie Langel via GitHub
• Closed: [sensors] Updating security and privacy considerations Tobie Langel via GitHub
• Re: [gyroscope] Adapt Gyroscope to the latest changes in the Generic Sensor API Anssi Kostiainen via GitHub
• Closed: [sensors] Clarify scope of generic sensor Tobie Langel via GitHub
• Re: [sensors] Clarify scope of generic sensor Tobie Langel via GitHub
• Re: [gyroscope] Adapt Gyroscope to the latest changes in the Generic Sensor API Mikhail Pozdnyakov via GitHub
• Re: [sensors] Split parameters between start() and constructor Tobie Langel via GitHub
• Re: [sensors] Call 'onchange' only when data changes and considering frequency hint Tobie Langel via GitHub
• Closed: [sensors] Should the enum SensorState have nosensor ? Tobie Langel via GitHub
• Closed: [sensors] Remove side-effects from Sensor Constructor Tobie Langel via GitHub
• Closed: [sensors] Possibility of cross-domain communication using frequency in periodic reporting mode Tobie Langel via GitHub
• Closed: [sensors] Don't allocate response objects to avoid triggering GC Tobie Langel via GitHub
• Closed: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. Tobie Langel via GitHub
• Closed: [sensors] Move default sensor check to start() Tobie Langel via GitHub
• Closed: [sensors] Should we request permission when sensor is not supported by the platform? Tobie Langel via GitHub
• Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications Tobie Langel via GitHub

Tuesday, 24 January 2017

• Re: [vibration] Fix ReSpec warnings Anssi Kostiainen via GitHub

Monday, 23 January 2017

• Re: [battery] Fix ReSpec warnings Anssi Kostiainen via GitHub

Sunday, 22 January 2017

• Re: [battery] Mitigating potential privacy-invasive usage Lukasz Olejnik via GitHub

Friday, 13 January 2017

• 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

Tuesday, 10 January 2017

• Re: [magnetometer] Add support for raw Tobie Langel via GitHub
• [wake-lock] The spec is unnecessarily strict in regard to promise handling Andrey Logvinov via GitHub

Monday, 9 January 2017

• [battery] Respec warns about missing <dfn>'s in contiguous webidl Andrey Logvinov via GitHub
• [wake-lock] Fix respec warnings Andrey Logvinov via GitHub

Wednesday, 4 January 2017

• Re: [magnetometer] Fixup example to use JS conventions Anssi Kostiainen via GitHub
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values Rijubrata Bhaumik via GitHub

Last message date: Tuesday, 31 January 2017 15:09:48 UTC