[sensors] Reading attributes at different sensor states
- Re: [sensors] Reading attributes at different sensor states
- Re: [sensors] Reading attributes at different sensor states
- Re: [sensors] Reading attributes at different sensor states
- Re: [sensors] Reading attributes at different sensor states
Re: [html-media-capture] VideoFacingModeEnum as the capture attribute's value
Closed: [sensors] Meta: figure out why travis fails for pull requests
Re: [sensors] Add script to easily publish to /TR/.
- Re: [sensors] Add script to easily publish to /TR/.
- Re: [sensors] Add script to easily publish to /TR/.
- Re: [sensors] Add script to easily publish to /TR/.
Closed: [wake-lock] "System" wake lock use cases
Re: [wake-lock] TAG feedback on wake-lock API
Re: [wake-lock] "System" wake lock use cases
Re: [sensors] Make timestamp nullable
[sensors] latest reading should be declarted as internal slot
- Re: [sensors] latest reading should be declarted as an internal slot
- Re: [sensors] latest reading should be declarted as an internal slot
- Re: [sensors] latest reading should be declarted as an internal slot
- Re: [sensors] latest reading should be declarted as an internal slot
- Re: [sensors] latest reading should be declarted as an internal slot
- Re: [sensors] latest reading should be declarted as an internal slot
[sensors] Fix Sensor.start() operation description
- Re: [sensors] Fix Sensor.start() operation description
- Re: [sensors] Fix Sensor.start() operation description
- Closed: [sensors] Fix Sensor.start() operation description
[sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
- Re: [sensors] Find a better name for 'unconnected' state
[sensors] Sensor.timestamp must be nullable
Re: [wake-lock] chore: fix ReSpec warnings (closes #91)
[sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Re: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
- Closed: [sensors] DOMExceptions when calling stop/start on already stopped/started sensor
Closed: [sensors] Frequency readout allows fingerprinting sensors, privacy.
Re: [sensors] Malicious use of the phone's Gyroscope
Closed: [sensors] Malicious use of the phone's Gyroscope
Re: [sensors] Updating privacy considerations - accounting
Closed: [sensors] Updating privacy considerations - accounting
Closed: [sensors] Revoking user permission
Closed: [sensors] Updating security and privacy considerations
Closed: [sensors] Clarify scope of generic sensor
Re: [sensors] Clarify scope of generic sensor
Re: [gyroscope] Adapt Gyroscope to the latest changes in the Generic Sensor API
- Re: [gyroscope] Adapt Gyroscope to the latest changes in the Generic Sensor API
- Re: [gyroscope] Adapt Gyroscope to the latest changes in the Generic Sensor API
Re: [sensors] Split parameters between start() and constructor
Re: [sensors] Call 'onchange' only when data changes and considering frequency hint
Closed: [sensors] Should the enum SensorState have nosensor ?
Closed: [sensors] Remove side-effects from Sensor Constructor
Closed: [sensors] Possibility of cross-domain communication using frequency in periodic reporting mode
Closed: [sensors] Don't allocate response objects to avoid triggering GC
Closed: [sensors] Eventually rename the SensorReading timeStamp attribute for consistency with DOM events.
Closed: [sensors] Move default sensor check to start()
Closed: [sensors] Should we request permission when sensor is not supported by the platform?
Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications
- Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications
- Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications
- Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications
- Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications