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

Alexander Shalamov via GitHub

Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors (Friday, 29 September)
Closed: [sensors] Take into account user gestures as an input for security policy enforcement (Tuesday, 26 September)
Re: [sensors] Take into account user gestures as an input for security policy enforcement (Tuesday, 26 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] Add 'user triggered activation' as mitigation strategy (Tuesday, 26 September)
Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Closed: [sensors] Should a "suspended" state be added (Tuesday, 26 September)
Re: [sensors] Should a "suspended" state be added (Tuesday, 26 September)
Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Closed: [sensors] Define algorithm for suspending / resuming activated sensor objects (Tuesday, 26 September)
Closed: [sensors] Should a "suspended" state be added (Tuesday, 26 September)
Closed: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec. (Tuesday, 26 September)
Re: [sensors] bikeshed link errors (Monday, 25 September)
Re: [magnetometer] Use value getter operation and use double as attribute type (Monday, 25 September)
Re: [sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments (Monday, 25 September)
Closed: [sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments (Monday, 25 September)
Re: [magnetometer] Add security and privacy questionnaire for Magnetometer (Monday, 25 September)
Re: [magnetometer] Add security and privacy questionnaire for Magnetometer (Monday, 25 September)
Re: [magnetometer] Add security and privacy questionnaire for Magnetometer (Friday, 22 September)
[sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments from https://github.com/w3c/sensors/pull/270#issuecomment-330579933 (Friday, 22 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Wednesday, 20 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Wednesday, 20 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Wednesday, 20 September)
Re: [sensors] Answer Security and Privacy self review questionnaire (Wednesday, 20 September)
Closed: [sensors] granularity of Permission name for concrete/ fusion sensors (Wednesday, 20 September)
Closed: [sensors] Simplify extension of the Permissions API for concrete sensor implementations (Wednesday, 20 September)
Re: [sensors] Answer Security and Privacy self review questionnaire (Tuesday, 19 September)
Re: [accelerometer] Why unrestricted double for acceleration readings? (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Answer Security and Privacy self review questionnaire (Monday, 18 September)
Re: [sensors] Tie [=latest reading=] map to an origin (Friday, 15 September)
[sensors] Review Security and Privacy questionnaire (Tuesday, 12 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration (Thursday, 7 September)
Re: [sensors] Addressing finger printing concerns for sensor APIs (Thursday, 7 September)
Re: [sensors] Use [Exposed=Window] (Wednesday, 6 September)

Anssi Kostiainen via GitHub

Re: [sensors] Sensor.timeStamp could be clarified (Friday, 29 September)
Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors (Friday, 29 September)
Re: [sensors] Editorial fixes to Extensibility section (Wednesday, 27 September)
Closed: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] Addressing finger printing concerns for sensor APIs (Tuesday, 26 September)
Closed: [sensors] Addressing finger printing concerns for sensor APIs (Tuesday, 26 September)
Closed: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration (Tuesday, 26 September)
Re: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration (Tuesday, 26 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (Monday, 25 September)
Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (Monday, 25 September)
Re: [sensors] Sensor discovery (Monday, 25 September)
Re: [sensors] Sensor discovery (Monday, 25 September)
Re: [ambient-light] Use value getter operation and fix illuminance attribute type (Monday, 25 September)
Re: [sensors] Introduce Default Sensor concept (Monday, 25 September)
Re: [sensors] Split security & privacy questionnaire (Monday, 25 September)
Re: [battery] Allow use in same-origin children (Friday, 22 September)
Re: [battery] Allow use in same-origin children (Thursday, 21 September)
Re: [gyroscope] Define Gyroscope sensor type, clarify latest reading (Thursday, 21 September)
Re: [sensors] Introduce a Reading Change Treshold concept (Thursday, 21 September)
Re: [battery] Allow use in same-origin children (Wednesday, 20 September)
Re: [battery] Allow use in same-origin children (Wednesday, 20 September)
Re: [sensors] Fix #193: Define extension spec Security & Privacy expectations (Wednesday, 20 September)
Closed: [sensors] Security issues when used in combination with other APIs (Wednesday, 20 September)
Re: [sensors] Fix Bikeshed custom header rendering bug (Wednesday, 20 September)
Re: [sensors] Security issues when used in combination with other APIs (Tuesday, 19 September)
Re: [sensors] Redefine [=sensor=] concept (Tuesday, 19 September)
Re: [sensors] Security issues when used in combination with other APIs (Tuesday, 19 September)
Re: [battery] Allow use in same-origin children (Tuesday, 19 September)
Re: [sensors] Fix Bikeshed custom header rendering bug (Tuesday, 19 September)
Re: [sensors] Tie [=latest reading=] map to an origin (Monday, 18 September)
Re: [sensors] Update geolocation.js polyfill (Monday, 18 September)
Re: [sensors] Update geolocation.js polyfill (Monday, 18 September)
Re: [sensors] Security issues when used in combination with other APIs (Wednesday, 13 September)
Re: [sensors] Review Security and Privacy questionnaire (Wednesday, 13 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Friday, 8 September)
Closed: [sensors] Investigate using PWA installed status as indication of user intent (Friday, 8 September)
Re: [sensors] Security issues when used in combination with other APIs (Friday, 8 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Addressing finger printing concerns for sensor APIs (Thursday, 7 September)
Re: [sensors] Annotate interface with [Exposed] extended attribute (Wednesday, 6 September)
Re: [sensors] Use [Exposed=Window] (Wednesday, 6 September)
Re: [sensors] Use [Exposed=Window] (Wednesday, 6 September)
Re: [ambient-light] Fix #37: Add cross-origin leaks, hijacking browsing history (Monday, 4 September)
Closed: [ambient-light] Exfiltrating data across origins (Monday, 4 September)

Dan Brickley via GitHub

Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)

Dominique Hazael-Massieux via GitHub

Re: [proximity] Align with Generic Sensor API current state (Monday, 25 September)
Re: [battery] Allow use in same-origin children (Wednesday, 20 September)
Re: [sensors] Answer Security and Privacy self review questionnaire (Tuesday, 19 September)
Re: [sensors] Security issues when used in combination with other APIs (Tuesday, 19 September)
[accelerometer] Why unrestricted double for acceleration readings? (Friday, 15 September)
Re: [sensors] Use [Exposed=Window] (Wednesday, 6 September)

Google

Re: [sensors] Introduce the Reading Timestamp concept (Friday, 29 September)

Ian Clelland via GitHub

Re: [battery] Allow use in same-origin children (Friday, 22 September)
Re: [battery] Allow use in same-origin children (Thursday, 21 September)

Kenneth Rohde Christiansen via GitHub

Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Wednesday, 20 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Wednesday, 20 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Monday, 18 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Monday, 18 September)
[sensors] Undefined values makes GS a pain to work with using TypeScript (Monday, 18 September)

Lars Knudsen via GitHub

Re: [sensors] Sensor discovery (Monday, 25 September)
Re: [sensors] Sensor discovery (Monday, 25 September)

Lukasz Olejnik via GitHub

Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Re: [sensors] Security issues when used in combination with other APIs (Tuesday, 19 September)
Re: [sensors] Tie [=latest reading=] map to an origin (Friday, 15 September)
Re: [sensors] Security issues when used in combination with other APIs (Thursday, 14 September)
Re: [ambient-light] Fix #37: Add cross-origin leaks, hijacking browsing history (Sunday, 3 September)

Mikhail Pozdnyakov via GitHub

Re: [sensors] Future proofing terminology (Friday, 29 September)
Re: [sensors] Future proofing terminology (Friday, 29 September)
Re: [sensors] Sensor.timeStamp could be clarified (Friday, 29 September)
Closed: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency? (Friday, 29 September)
Re: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency? (Friday, 29 September)
Re: [sensors] Clarify sensor frequency concepts (Friday, 29 September)
Re: [sensors] Clarify sensor frequency concepts (Thursday, 28 September)
Re: [sensors] Clarify sensor frequency concepts (Wednesday, 27 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Closed: [sensors] bikeshed link errors (Tuesday, 26 September)
Re: [sensors] bikeshed link errors (Tuesday, 26 September)
Re: [sensors] Introduce Default Sensor concept (Monday, 25 September)
Re: [sensors] Introduce Default Sensor concept (Friday, 22 September)
Re: [accelerometer] Why unrestricted double for acceleration readings? (Thursday, 21 September)
Re: [sensors] Introduce Default Sensor concept (Thursday, 21 September)
Closed: [sensors] Find a clearer name for the sensor concept (Wednesday, 20 September)
Re: [accelerometer] Why unrestricted double for acceleration readings? (Wednesday, 20 September)
Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (Wednesday, 20 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Monday, 18 September)
Re: [sensors] Tie [=latest reading=] map to an origin (Monday, 18 September)
Re: [sensors] Tie [=latest reading=] map to an origin (Friday, 15 September)
Re: [sensors] Tie [=latest reading=] map to an origin (Friday, 15 September)
Re: [sensors] Relation to Permissions API (Thursday, 7 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Security issues when used in combination with other APIs (Thursday, 7 September)

Mounir Lamouri via GitHub

Re: [battery] Allow use in same-origin children (Wednesday, 20 September)

Rick Byers via GitHub

Re: [battery] Allow use in same-origin children (Tuesday, 19 September)

Rick Waldron via GitHub

Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (Monday, 25 September)
Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (Monday, 25 September)
Closed: [sensors] Undefined values makes GS a pain to work with using TypeScript (Monday, 25 September)
Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (Monday, 25 September)
Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (Friday, 22 September)
Re: [sensors] Add information to "Extending the Permission API" section (Tuesday, 19 September)
Closed: [sensors] Review Security and Privacy questionnaire (Tuesday, 19 September)
Re: [sensors] Answer Security and Privacy self review questionnaire (Tuesday, 19 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Monday, 18 September)
Re: [sensors] Undefined values makes GS a pain to work with using TypeScript (Monday, 18 September)
Re: [sensors] Review Security and Privacy questionnaire (Tuesday, 12 September)

Tobie Langel via GitHub

Re: [sensors] Future proofing terminology (Friday, 29 September)
[sensors] Future proofing terminology (Friday, 29 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] Make 'Conditions to expose sensor readings' must (Tuesday, 26 September)
Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Re: [sensors] Should a "suspended" state be added (Tuesday, 26 September)
Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Re: [sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
[sensors] What's the rationale of moving security checks outside of normative requirements? (Tuesday, 26 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)
Re: [sensors] Investigate using PWA installed status as indication of user intent (Thursday, 7 September)

Last message date: Friday, 29 September 2017 21:45:19 UTC