public-device-apis-log@w3.org from May 2017 by author

Alexander Shalamov via GitHub

• Re: [sensors] Define tasks for state changes (Wednesday, 31 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• [sensors] Define algorithm for suspending / resuming activated sensor objects (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Should update sensor reading task be in sync with latest reading? (Monday, 29 May)
• Re: [sensors] Should update sensor reading task be in sync with latest reading? (Saturday, 27 May)
• Re: [sensors] Define algorithm for suspending / resuming activated sensor objects (Saturday, 27 May)
• Re: [sensors] Clarify relationship between Sensor object and task source (Saturday, 27 May)
• Re: [sensors] Clarify sensor task source scope (Saturday, 27 May)
• [sensors] Should update sensor reading task be in sync with latest reading? (Saturday, 27 May)
• [sensors] Define parameters for events (Saturday, 27 May)
• [sensors] Define tasks for state changes (Saturday, 27 May)
• [sensors] Define algorithm for suspending / resuming activated sensor objects (Saturday, 27 May)
• [sensors] Clarify relationship between Sensor object and task source (Saturday, 27 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Saturday, 27 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [ambient-light] Security and Privacy considerations for ALS (Wednesday, 24 May)
• Re: [sensors] Define processing model (Wednesday, 24 May)
• Re: [sensors] Define processing model (Wednesday, 24 May)
• Re: [sensors] Define processing model (Wednesday, 24 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Friday, 19 May)
• Re: [sensors] Add mitigation strategy for focuseable elements (Friday, 19 May)
• Re: [ambient-light] Security and Privacy considerations for ALS (Thursday, 18 May)
• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Friday, 12 May)
• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Friday, 12 May)
• [sensors] Take into account user gestures as an input for security policy enforcement (Friday, 12 May)
• Re: [ambient-light] Add description for use cases (Friday, 12 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks by using input element state (Wednesday, 3 May)
• Re: [ambient-light] Security and Privacy considerations for ALS (Tuesday, 2 May)

Anssi Kostiainen via GitHub

• Closed: [magnetometer] Permission (Wednesday, 31 May)
• Re: [magnetometer] Permission (Wednesday, 31 May)
• Re: [magnetometer] Link to use cases in the spec (Wednesday, 31 May)
• Closed: [magnetometer] Link to use cases in the spec (Wednesday, 31 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Define processing model (Tuesday, 30 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Tuesday, 30 May)
• Re: [sensors] Agree on event names (Monday, 29 May)
• Re: [sensors] Define processing model (Monday, 29 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] [meta] Publish a new Working Draft (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Define processing model (Wednesday, 24 May)
• Re: [sensors] Rewrite Abstract Operations (Tuesday, 23 May)
• Re: [sensors] Define processing model (Tuesday, 23 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Tuesday, 23 May)
• Re: [battery] [meta] Publish a revised Candidate Recommendation (Tuesday, 23 May)
• Re: [html-media-capture] [meta] Publish a revised Candidate Recommendation (Tuesday, 23 May)
• Closed: [html-media-capture] Define clearly how the capture IDL attribute is reflected (Tuesday, 23 May)
• Re: [html-media-capture] [meta] Publish a revised Candidate Recommendation (Monday, 22 May)
• Re: [html-media-capture] Fix #12: Make the capture IDL attribute a DOMString (Monday, 22 May)
• [html-media-capture] [meta] Publish a revised Candidate Recommendation (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Define processing model (Monday, 22 May)
• Re: [battery] [meta] Publish a revised Candidate Recommendation (Monday, 22 May)
• Re: [battery] [meta] Publish a revised Candidate Recommendation (Monday, 22 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Monday, 22 May)
• Re: [sensors] Add mitigation strategy for focuseable elements (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Define processing model (Monday, 22 May)
• Closed: [ambient-light] [meta] Publish a new Working Draft (Monday, 22 May)
• Re: [ambient-light] [meta] Publish a new Working Draft (Monday, 22 May)
• [ambient-light] [meta] Publish a new Working Draft (Thursday, 18 May)
• Re: [ambient-light] Auto reporting mode is not defined (Thursday, 18 May)
• Closed: [ambient-light] Auto reporting mode is not defined (Thursday, 18 May)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Wednesday, 17 May)
• Re: [sensors] [meta] Publish a new Working Draft (Tuesday, 16 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Monday, 15 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Monday, 15 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Monday, 15 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Monday, 15 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Monday, 15 May)
• Re: [ambient-light] Provide "Use Cases and Requirements" section (Friday, 12 May)
• Re: [ambient-light] Provide "Use Cases and Requirements" section (Friday, 12 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [html-media-capture] VideoFacingModeEnum as the capture attribute's value (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Closed: [html-media-capture] Update test suite (Wednesday, 10 May)
• Re: [html-media-capture] Update test suite (Wednesday, 10 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Re: [sensors] [meta] Publish a new Working Draft (Wednesday, 10 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Closed: [battery] Allow use from within secure context and top-level browsing context only (Wednesday, 10 May)
• Re: [battery] Fix #10: Restrict to secure context and top-level browsing context (Wednesday, 10 May)
• Re: [battery] Allow use from within secure context and top-level browsing context only (Wednesday, 10 May)
• Re: [sensors] [meta] Publish a new Working Draft (Tuesday, 9 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Tuesday, 9 May)
• Re: [sensors] Relation to Permissions API (Monday, 8 May)
• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Thursday, 4 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Thursday, 4 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Wednesday, 3 May)
• Re: [sensors] [meta] Publish a new Working Draft (Wednesday, 3 May)
• [sensors] [meta] Publish a new Working Draft (Wednesday, 3 May)
• Re: [html-media-capture] [meta] Prepare a revised Candidate Recommendation snapshot (Tuesday, 2 May)

chaals via GitHub

• [wake-lock] new type: location? (Monday, 22 May)

Domenic Denicola via GitHub

• Re: [html-media-capture] Define clearly how the capture IDL attribute is reflected (Wednesday, 3 May)

Dominique Hazael-Massieux via GitHub

• Re: [battery] [meta] Publish a revised Candidate Recommendation (Friday, 19 May)
• Re: [sensors] [meta] Publish a new Working Draft (Wednesday, 3 May)

Kenneth Rohde Christiansen via GitHub

• Re: [sensors] Queue tasks for [[state]] changes. (Wednesday, 31 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Friday, 5 May)
• Re: [sensors] Batching API for sensor readings (Friday, 5 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)

Lukasz Olejnik via GitHub

• Re: [ambient-light] Security and Privacy considerations for ALS (Monday, 29 May)
• Re: [ambient-light] Provide "Use Cases and Requirements" section (Friday, 12 May)
• Re: [sensors] Security issues when used in combination with other APIs (Thursday, 11 May)
• Re: [sensors] Security issues when used in combination with other APIs (Monday, 8 May)
• Re: [sensors] Avoid PIN skimming attacks (Wednesday, 3 May)

Maryam Mehr via GitHub

• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Friday, 5 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Thursday, 4 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Thursday, 4 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Thursday, 4 May)

Mikhail Pozdnyakov via GitHub

• Re: [sensors] Define processing model (Wednesday, 31 May)
• Re: [sensors] Sensor objects fire 'change' event considering their own frequency hint (Wednesday, 31 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Agree on event names (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Sensor objects have their own reading copies (Wednesday, 24 May)
• Re: [sensors] Sensor obects have their own a reading copies. (Tuesday, 23 May)
• Re: [sensors] Rewrite Abstract Operations (Tuesday, 23 May)
• [sensors] Use ''sampling frequency" instead of "polling frequency" (Tuesday, 23 May)
• Re: [sensors] Consistent event names. (Tuesday, 23 May)
• Re: [sensors] Rewrite Abstract Operations (Tuesday, 23 May)
• Re: [sensors] Rewrite Abstract Operations (Monday, 22 May)
• Re: [sensors] Rewrite Abstract Operations (Monday, 22 May)
• Re: [sensors] Define processing model (Monday, 22 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Monday, 22 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the Sensor object (Friday, 19 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 19 May)
• [sensors] The Update latest reading abstract operation is never invoked (Friday, 19 May)
• [sensors] Sensor object can stuck in `activating` state (Friday, 19 May)
• [sensors] The Handle Errors abstract operation must deactivate the Sensor object (Friday, 19 May)
• [sensors] The Sensor.waitingForUpdate internal slot is useless (Friday, 19 May)
• [sensors] The Update Observers abstract operation fires unspecified "reading" event (Friday, 19 May)
• [sensors] The Sensor.lastEventFiredAt internal slot is useless (Friday, 19 May)
• Re: [sensors] Batching API for sensor readings (Friday, 19 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 19 May)
• Re: [sensors] Rewrite Abstract Operations (Thursday, 18 May)
• Re: [sensors] A Sensor instance sends 'onchange' considering its frequency hint (Thursday, 18 May)
• Re: [sensors] A Sensor instance sends 'onchange' considering its frequency hint (Monday, 15 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)

ojan via GitHub

• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Saturday, 27 May)

Owen Campbell-Moore via GitHub

• [magnetometer] Link to use cases in the spec (Wednesday, 31 May)
• [gyroscope] Add link to use cases in spec (Wednesday, 31 May)
• [accelerometer] Add use cases to spec (Tuesday, 30 May)

Philip Jägenstedt via GitHub

• [html-media-capture] Define clearly how the capture IDL attribute is reflected (Wednesday, 3 May)

raymeskhoury via GitHub

• Re: [sensors] Relation to Permissions API (Monday, 8 May)

Rick Waldron via GitHub

• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)

Rijubrata Bhaumik via GitHub

• Re: [magnetometer] Provide API to access uncalibrated magnetometer values (Tuesday, 16 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)

Tobie Langel via GitHub

• Re: [sensors] Clarify relationship between Sensor object and task source (Wednesday, 31 May)
• Re: [sensors] Sensor objects fire 'change' event considering their own frequency hint (Wednesday, 31 May)
• Re: [sensors] Define tasks for state changes (Wednesday, 31 May)
• Closed: [sensors] Should update sensor reading task be in sync with latest reading? (Tuesday, 30 May)
• Re: [sensors] Should update sensor reading task be in sync with latest reading? (Tuesday, 30 May)
• Re: [sensors] Clarify relationship between Sensor object and task source (Tuesday, 30 May)
• Closed: [sensors] Clarify relationship between Sensor object and task source (Tuesday, 30 May)
• Re: [sensors] Define tasks for state changes (Tuesday, 30 May)
• Closed: [sensors] Mark mitigation strategy section as informative and avoid RFC2119 language in it. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• [sensors] Mark mitigation strategy section as informative and avoid RFC2119 language in it. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Investigate adding dedicated task sources (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• Re: [sensors] Use focus chain. (Tuesday, 30 May)
• Closed: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Tuesday, 30 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Tuesday, 30 May)
• Closed: [sensors] Clarify sensor task source scope (Tuesday, 30 May)
• Re: [sensors] Clarify sensor task source scope (Tuesday, 30 May)
• Closed: [sensors] Define algorithm for suspending / resuming activated sensor objects (Tuesday, 30 May)
• Re: [sensors] Define algorithm for suspending / resuming activated sensor objects (Tuesday, 30 May)
• Closed: [sensors] Avoid PIN skimming attacks (Tuesday, 30 May)
• Closed: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec. (Tuesday, 30 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Tuesday, 30 May)
• [sensors] Should a "suspended" state be added (Tuesday, 30 May)
• [sensors] Missing browsing-context focus/unfocus hooks in HTML spec. (Tuesday, 30 May)
• Re: [sensors] Define processing model (Tuesday, 30 May)
• Re: [sensors] Define processing model (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Monday, 29 May)
• Re: [sensors] Should update sensor reading task be in sync with latest reading? (Monday, 29 May)
• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Saturday, 27 May)
• Re: [sensors] Should update sensor reading task be in sync with latest reading? (Saturday, 27 May)
• [sensors] Investigate adding dedicated task sources (Saturday, 27 May)
• Re: [sensors] Clarify sensor task source scope (Saturday, 27 May)
• Re: [sensors] Define algorithm for suspending / resuming activated sensor objects (Saturday, 27 May)
• Re: [sensors] Clarify relationship between Sensor object and task source (Saturday, 27 May)
• Re: [sensors] Define parameters for events (Saturday, 27 May)
• Closed: [sensors] Define parameters for events (Saturday, 27 May)
• Re: [sensors] Should update sensor reading task be in sync with latest reading? (Saturday, 27 May)
• Re: [sensors] Define tasks for state changes (Saturday, 27 May)
• Re: [sensors] Define algorithm for suspending / resuming activated sensor objects (Saturday, 27 May)
• Re: [sensors] Clarify relationship between Sensor object and task source (Saturday, 27 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Define processing model (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Add mitigation strategy for skimming attacks when focus is lost. (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Call 'onchange' on a Senor instance considering its own frequency hint (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use simple event dispatch mechanism instead of task source (queued) (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 26 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Friday, 26 May)
• Re: [sensors] Sensor objects have their own reading copies (Wednesday, 24 May)
• Re: [sensors] Define processing model (Wednesday, 24 May)
• Re: [sensors] Define processing model (Wednesday, 24 May)
• [sensors] Sensors unable to provide their state when instantiated (Wednesday, 24 May)
• Closed: [sensors] [meta] Publish a new Working Draft (Wednesday, 24 May)
• [sensors] Clarify sensor task source scope (Tuesday, 23 May)
• [sensors] Investigate using PWA installed status as indication of user intent (Tuesday, 23 May)
• Re: [sensors] Use ''sampling frequency" instead of "polling frequency" (Tuesday, 23 May)
• Re: [sensors] [meta] Publish a new Working Draft (Tuesday, 23 May)
• Closed: [sensors] The Update Observers abstract operation fires unspecified "reading" event (Tuesday, 23 May)
• Re: [sensors] Define processing model (Tuesday, 23 May)
• Re: [sensors] Rewrite Abstract Operations (Tuesday, 23 May)
• Re: [sensors] Rewrite Abstract Operations (Tuesday, 23 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Rewrite Abstract Operations (Monday, 22 May)
• Re: [sensors] Rewrite Abstract Operations (Monday, 22 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Define processing model (Monday, 22 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Monday, 22 May)
• Re: [sensors] Add 'user triggered activation' as mitigation strategy (Monday, 22 May)
• Re: [sensors] Sensor object can stuck in `activating` state (Friday, 19 May)
• Closed: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Friday, 19 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the activated Sensor object (Friday, 19 May)
• [sensors] Agree on event names (Friday, 19 May)
• Re: [sensors] The Update latest reading abstract operation is never invoked (Friday, 19 May)
• Re: [sensors] The Handle Errors abstract operation must deactivate the Sensor object (Friday, 19 May)
• Closed: [sensors] The Handle Errors abstract operation must deactivate the Sensor object (Friday, 19 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 19 May)
• Re: [sensors] Define processing model (Friday, 19 May)
• Re: [sensors] Rewrite Abstract Operations (Friday, 19 May)
• [sensors] Define processing model (Friday, 19 May)
• Re: [sensors] Rewrite Abstract Operations (Thursday, 18 May)
• Re: [sensors] Rewrite Abstract Operations (Thursday, 18 May)
• Re: [sensors] Rewrite Abstract Operations (Thursday, 18 May)
• Re: [ambient-light] [meta] Publish a new Working Draft (Thursday, 18 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Monday, 15 May)
• Re: [sensors] Listing threats (Monday, 15 May)
• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Friday, 12 May)
• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Friday, 12 May)
• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Friday, 12 May)
• Re: [sensors] Take into account user gestures as an input for security policy enforcement (Friday, 12 May)
• Re: [ambient-light] Provide "Use Cases and Requirements" section (Friday, 12 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Thursday, 11 May)
• Re: [sensors] Security issues when used in combination with other APIs (Thursday, 11 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Re: [magnetometer] Add RawMagnetometer, for uncalibrated readings. (Wednesday, 10 May)
• Re: [sensors] [meta] Publish a new Working Draft (Tuesday, 9 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Tuesday, 9 May)
• Re: [sensors] Security issues when used in combination with other APIs (Monday, 8 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Monday, 8 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Monday, 8 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Monday, 8 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Monday, 8 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Monday, 8 May)
• Re: [sensors] Relation to Permissions API (Monday, 8 May)
• Re: [sensors] Batching API for sensor readings (Friday, 5 May)
• Re: [sensors] Batching API for sensor readings (Friday, 5 May)
• Re: [sensors] Batching API for sensor readings (Friday, 5 May)
• [sensors] Security issues when used in combination with other APIs (Thursday, 4 May)
• [sensors] Listing threats (Thursday, 4 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Thursday, 4 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Closed: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Thursday, 4 May)
• Re: [sensors] First pass at adding sensor-specific mitigation strategies. (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Re: [sensors] Avoid PIN skimming attacks (Thursday, 4 May)
• Closed: [sensors] Provide the DeviceOrientation sensor (Wednesday, 3 May)
• Re: [sensors] Batching API for sensor readings (Wednesday, 3 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Wednesday, 3 May)
• Re: [sensors] Avoid PIN skimming attacks by using input element state (Wednesday, 3 May)
• Re: [sensors] Add Input Elements to Mitigation Strategies (Wednesday, 3 May)

Wanming Lin via GitHub

• Re: [battery] [meta] Publish a revised Candidate Recommendation (Tuesday, 23 May)
• Re: [battery] [meta] Publish a revised Candidate Recommendation (Tuesday, 23 May)

Last message date: Wednesday, 31 May 2017 13:16:03 UTC