Wednesday, 31 May 2017
- Re: [sensors] Clarify relationship between Sensor object and task source
- Closed: [magnetometer] Permission
- Re: [magnetometer] Permission
- Re: [magnetometer] Link to use cases in the spec
- Closed: [magnetometer] Link to use cases in the spec
- Re: [sensors] Sensor objects fire 'change' event considering their own frequency hint
- Re: [sensors] Define tasks for state changes
- Re: [sensors] Define tasks for state changes
- Re: [sensors] Define processing model
- Re: [sensors] Sensor objects fire 'change' event considering their own frequency hint
- Re: [sensors] Queue tasks for [[state]] changes.
- [magnetometer] Link to use cases in the spec
- [gyroscope] Add link to use cases in spec
Tuesday, 30 May 2017
- [accelerometer] Add use cases to spec
- Closed: [sensors] Should update sensor reading task be in sync with latest reading?
- Re: [sensors] Should update sensor reading task be in sync with latest reading?
- Re: [sensors] Clarify relationship between Sensor object and task source
- Closed: [sensors] Clarify relationship between Sensor object and task source
- Re: [sensors] Define tasks for state changes
- Closed: [sensors] Mark mitigation strategy section as informative and avoid RFC2119 language in it.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- [sensors] Define algorithm for suspending / resuming activated sensor objects
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- [sensors] Mark mitigation strategy section as informative and avoid RFC2119 language in it.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Investigate adding dedicated task sources
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Use focus chain.
- Closed: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- Closed: [sensors] Clarify sensor task source scope
- Re: [sensors] Clarify sensor task source scope
- Closed: [sensors] Define algorithm for suspending / resuming activated sensor objects
- Re: [sensors] Define algorithm for suspending / resuming activated sensor objects
- Closed: [sensors] Avoid PIN skimming attacks
- Closed: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- [sensors] Should a "suspended" state be added
- [sensors] Missing browsing-context focus/unfocus hooks in HTML spec.
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
Monday, 29 May 2017
- Re: [sensors] Agree on event names
- Re: [sensors] Agree on event names
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Define processing model
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Define processing model
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [ambient-light] Security and Privacy considerations for ALS
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Should update sensor reading task be in sync with latest reading?
- Re: [sensors] Should update sensor reading task be in sync with latest reading?
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
Saturday, 27 May 2017
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [sensors] Should update sensor reading task be in sync with latest reading?
- [sensors] Investigate adding dedicated task sources
- Re: [sensors] Should update sensor reading task be in sync with latest reading?
- Re: [sensors] Clarify sensor task source scope
- Re: [sensors] Define algorithm for suspending / resuming activated sensor objects
- Re: [sensors] Clarify relationship between Sensor object and task source
- Re: [sensors] Define parameters for events
- Closed: [sensors] Define parameters for events
- Re: [sensors] Should update sensor reading task be in sync with latest reading?
- Re: [sensors] Define algorithm for suspending / resuming activated sensor objects
- Re: [sensors] Define tasks for state changes
- Re: [sensors] Clarify relationship between Sensor object and task source
- Re: [sensors] Define algorithm for suspending / resuming activated sensor objects
- Re: [sensors] Clarify sensor task source scope
- Re: [sensors] Clarify relationship between Sensor object and task source
- [sensors] Should update sensor reading task be in sync with latest reading?
- [sensors] Define parameters for events
- [sensors] Define tasks for state changes
- [sensors] Define algorithm for suspending / resuming activated sensor objects
- [sensors] Clarify relationship between Sensor object and task source
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
Friday, 26 May 2017
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Define processing model
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Define processing model
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] [meta] Publish a new Working Draft
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Define processing model
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Define processing model
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Define processing model
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Define processing model
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost.
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use simple event dispatch mechanism instead of task source (queued)
- [sensors] Use simple event dispatch mechanism instead of task source (queued)
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
Wednesday, 24 May 2017
- Re: [ambient-light] Security and Privacy considerations for ALS
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- Re: [sensors] Sensor objects have their own reading copies
- Re: [sensors] Define processing model
- Re: [sensors] Sensor objects have their own reading copies
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- Re: [sensors] Define processing model
- [sensors] Sensors unable to provide their state when instantiated
- Closed: [sensors] [meta] Publish a new Working Draft
Tuesday, 23 May 2017
- [sensors] Clarify sensor task source scope
- [sensors] Investigate using PWA installed status as indication of user intent
- Re: [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] [meta] Publish a new Working Draft
- Closed: [sensors] The Update Observers abstract operation fires unspecified "reading" event
- Re: [sensors] Define processing model
- Re: [sensors] Sensor obects have their own a reading copies.
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Define processing model
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- [sensors] Use ''sampling frequency" instead of "polling frequency"
- Re: [sensors] Consistent event names.
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [battery] [meta] Publish a revised Candidate Recommendation
- Re: [battery] [meta] Publish a revised Candidate Recommendation
- Re: [html-media-capture] [meta] Publish a revised Candidate Recommendation
- Closed: [html-media-capture] Define clearly how the capture IDL attribute is reflected
- Re: [battery] [meta] Publish a revised Candidate Recommendation
Monday, 22 May 2017
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [html-media-capture] [meta] Publish a revised Candidate Recommendation
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- Re: [html-media-capture] Fix #12: Make the capture IDL attribute a DOMString
- [html-media-capture] [meta] Publish a revised Candidate Recommendation
- Re: [sensors] Define processing model
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Define processing model
- Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [battery] [meta] Publish a revised Candidate Recommendation
- Re: [battery] [meta] Publish a revised Candidate Recommendation
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Define processing model
- Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- Re: [sensors] Add mitigation strategy for focuseable elements
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Define processing model
- Closed: [ambient-light] [meta] Publish a new Working Draft
- Re: [ambient-light] [meta] Publish a new Working Draft
- [wake-lock] new type: location?
Friday, 19 May 2017
- Re: [sensors] Add 'user triggered activation' as mitigation strategy
- Re: [sensors] Add mitigation strategy for focuseable elements
- Re: [sensors] Sensor object can stuck in `activating` state
- Closed: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object
- [sensors] Agree on event names
- Re: [sensors] The Handle Errors abstract operation must deactivate the Sensor object
- Re: [battery] [meta] Publish a revised Candidate Recommendation
- Re: [sensors] The Update latest reading abstract operation is never invoked
- Re: [sensors] The Handle Errors abstract operation must deactivate the Sensor object
- Closed: [sensors] The Handle Errors abstract operation must deactivate the Sensor object
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- [sensors] The Update latest reading abstract operation is never invoked
- [sensors] Sensor object can stuck in `activating` state
- [sensors] The Handle Errors abstract operation must deactivate the Sensor object
- [sensors] The Sensor.waitingForUpdate internal slot is useless
- [sensors] The Update Observers abstract operation fires unspecified "reading" event
- [sensors] The Sensor.lastEventFiredAt internal slot is useless
- Re: [sensors] Define processing model
- Re: [sensors] Rewrite Abstract Operations
- [sensors] Define processing model
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Rewrite Abstract Operations
Thursday, 18 May 2017
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] Rewrite Abstract Operations
- Re: [sensors] A Sensor instance sends 'onchange' considering its frequency hint
- Re: [sensors] Rewrite Abstract Operations
- Re: [ambient-light] [meta] Publish a new Working Draft
- [ambient-light] [meta] Publish a new Working Draft
- Re: [ambient-light] Auto reporting mode is not defined
- Closed: [ambient-light] Auto reporting mode is not defined
- Re: [ambient-light] Security and Privacy considerations for ALS
Wednesday, 17 May 2017
Tuesday, 16 May 2017
- Re: [magnetometer] Provide API to access uncalibrated magnetometer values
- Re: [sensors] [meta] Publish a new Working Draft
Monday, 15 May 2017
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] A Sensor instance sends 'onchange' considering its frequency hint
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] Listing threats
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
Friday, 12 May 2017
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [sensors] Take into account user gestures as an input for security policy enforcement
- [sensors] Take into account user gestures as an input for security policy enforcement
- Re: [ambient-light] Provide "Use Cases and Requirements" section
- Re: [ambient-light] Add description for use cases
- Re: [ambient-light] Provide "Use Cases and Requirements" section
- Re: [ambient-light] Provide "Use Cases and Requirements" section
- Re: [ambient-light] Provide "Use Cases and Requirements" section
Thursday, 11 May 2017
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Provide API to access uncalibrated magnetometer values
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [html-media-capture] VideoFacingModeEnum as the capture attribute's value
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
Wednesday, 10 May 2017
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Closed: [html-media-capture] Update test suite
- Re: [html-media-capture] Update test suite
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Re: [sensors] [meta] Publish a new Working Draft
- Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings.
- Closed: [battery] Allow use from within secure context and top-level browsing context only
- Re: [battery] Fix #10: Restrict to secure context and top-level browsing context
- Re: [battery] Allow use from within secure context and top-level browsing context only
Tuesday, 9 May 2017
- Re: [sensors] [meta] Publish a new Working Draft
- Re: [sensors] [meta] Publish a new Working Draft
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] Add Input Elements to Mitigation Strategies
Monday, 8 May 2017
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] Security issues when used in combination with other APIs
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Relation to Permissions API
- Re: [sensors] Relation to Permissions API
- Re: [sensors] Relation to Permissions API
Friday, 5 May 2017
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] Batching API for sensor readings
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
Thursday, 4 May 2017
- Re: [magnetometer] Provide API to access uncalibrated magnetometer values
- [sensors] Security issues when used in combination with other APIs
- [sensors] Listing threats
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] Avoid PIN skimming attacks
- Closed: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] First pass at adding sensor-specific mitigation strategies.
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Add Input Elements to Mitigation Strategies
Wednesday, 3 May 2017
- Closed: [sensors] Provide the DeviceOrientation sensor
- Re: [sensors] Avoid PIN skimming attacks
- Re: [sensors] Batching API for sensor readings
- Re: [html-media-capture] Define clearly how the capture IDL attribute is reflected
- Re: [sensors] Avoid PIN skimming attacks by using input element state
- [html-media-capture] Define clearly how the capture IDL attribute is reflected
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] Avoid PIN skimming attacks by using input element state
- Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint
- Re: [sensors] Add Input Elements to Mitigation Strategies
- Re: [sensors] [meta] Publish a new Working Draft
- Re: [sensors] [meta] Publish a new Working Draft
- [sensors] [meta] Publish a new Working Draft