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

Friday, 29 September 2017

• Re: [sensors] Introduce the Reading Timestamp concept Google
• Re: [sensors] Future proofing terminology Mikhail Pozdnyakov via GitHub
• Re: [sensors] Future proofing terminology Tobie Langel via GitHub
• Re: [sensors] Future proofing terminology Mikhail Pozdnyakov via GitHub
• Re: [sensors] Sensor.timeStamp could be clarified Anssi Kostiainen via GitHub
• Re: [sensors] Sensor.timeStamp could be clarified Mikhail Pozdnyakov via GitHub
• [sensors] Future proofing terminology Tobie Langel via GitHub
• Closed: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency? Mikhail Pozdnyakov via GitHub
• Re: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency? Mikhail Pozdnyakov via GitHub
• Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors Anssi Kostiainen via GitHub
• Re: [sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors Alexander Shalamov via GitHub
• Re: [sensors] Clarify sensor frequency concepts Mikhail Pozdnyakov via GitHub

Thursday, 28 September 2017

• Re: [sensors] Clarify sensor frequency concepts Mikhail Pozdnyakov via GitHub

Wednesday, 27 September 2017

• Re: [sensors] Clarify sensor frequency concepts Mikhail Pozdnyakov via GitHub
• Re: [sensors] Editorial fixes to Extensibility section Anssi Kostiainen via GitHub

Tuesday, 26 September 2017

• Closed: [sensors] What's the rationale of moving security checks outside of normative requirements? Anssi Kostiainen via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Anssi Kostiainen via GitHub
• Re: [sensors] Addressing finger printing concerns for sensor APIs Anssi Kostiainen via GitHub
• Closed: [sensors] Addressing finger printing concerns for sensor APIs Anssi Kostiainen via GitHub
• Closed: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration Anssi Kostiainen via GitHub
• Re: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration Anssi Kostiainen via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Anssi Kostiainen via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Tobie Langel via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Anssi Kostiainen via GitHub
• Closed: [sensors] Take into account user gestures as an input for security policy enforcement Alexander Shalamov via GitHub
• Re: [sensors] Take into account user gestures as an input for security policy enforcement Alexander Shalamov via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Anssi Kostiainen via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Alexander Shalamov via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Tobie Langel via GitHub
• Re: [sensors] Add 'user triggered activation' as mitigation strategy Alexander Shalamov via GitHub
• Re: [sensors] Make 'Conditions to expose sensor readings' must Mikhail Pozdnyakov via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Tobie Langel via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Alexander Shalamov via GitHub
• Closed: [sensors] Should a "suspended" state be added Alexander Shalamov via GitHub
• Re: [sensors] Should a "suspended" state be added Alexander Shalamov via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Mikhail Pozdnyakov via GitHub
• Re: [sensors] Should a "suspended" state be added Tobie Langel via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Tobie Langel via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Dan Brickley via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Lukasz Olejnik via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Tobie Langel via GitHub
• Re: [sensors] What's the rationale of moving security checks outside of normative requirements? Alexander Shalamov via GitHub
• [sensors] What's the rationale of moving security checks outside of normative requirements? Tobie Langel via GitHub
• Closed: [sensors] Define algorithm for suspending / resuming activated sensor objects Alexander Shalamov via GitHub
• Closed: [sensors] Should a "suspended" state be added Alexander Shalamov via GitHub
• Closed: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec. Alexander Shalamov via GitHub
• Closed: [sensors] bikeshed link errors Mikhail Pozdnyakov via GitHub
• Re: [sensors] bikeshed link errors Mikhail Pozdnyakov via GitHub

Monday, 25 September 2017

• Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 Rick Waldron via GitHub
• Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 Anssi Kostiainen via GitHub
• Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 Rick Waldron via GitHub
• Closed: [sensors] Undefined values makes GS a pain to work with using TypeScript Rick Waldron via GitHub
• Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 Anssi Kostiainen via GitHub
• Re: [sensors] bikeshed link errors Alexander Shalamov via GitHub
• Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 Rick Waldron via GitHub
• Re: [sensors] Sensor discovery Anssi Kostiainen via GitHub
• Re: [sensors] Sensor discovery Lars Knudsen via GitHub
• Re: [sensors] Sensor discovery Anssi Kostiainen via GitHub
• Re: [magnetometer] Use value getter operation and use double as attribute type Alexander Shalamov via GitHub
• Re: [ambient-light] Use value getter operation and fix illuminance attribute type Anssi Kostiainen via GitHub
• Re: [sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments Alexander Shalamov via GitHub
• Closed: [sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments Alexander Shalamov via GitHub
• Re: [sensors] Introduce Default Sensor concept Anssi Kostiainen via GitHub
• Re: [sensors] Sensor discovery Lars Knudsen via GitHub
• Re: [magnetometer] Add security and privacy questionnaire for Magnetometer Alexander Shalamov via GitHub
• Re: [sensors] Split security & privacy questionnaire Anssi Kostiainen via GitHub
• Re: [magnetometer] Add security and privacy questionnaire for Magnetometer Alexander Shalamov via GitHub
• Re: [sensors] Introduce Default Sensor concept Mikhail Pozdnyakov via GitHub
• Re: [proximity] Align with Generic Sensor API current state Dominique Hazael-Massieux via GitHub

Friday, 22 September 2017

• Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 Rick Waldron via GitHub
• Re: [sensors] Introduce Default Sensor concept Mikhail Pozdnyakov via GitHub
• Re: [magnetometer] Add security and privacy questionnaire for Magnetometer Alexander Shalamov via GitHub
• Re: [battery] Allow use in same-origin children Anssi Kostiainen via GitHub
• [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 Alexander Shalamov via GitHub
• Re: [battery] Allow use in same-origin children Ian Clelland via GitHub

Thursday, 21 September 2017

• Re: [battery] Allow use in same-origin children Anssi Kostiainen via GitHub
• Re: [accelerometer] Why unrestricted double for acceleration readings? Mikhail Pozdnyakov via GitHub
• Re: [sensors] Introduce Default Sensor concept Mikhail Pozdnyakov via GitHub
• Re: [gyroscope] Define Gyroscope sensor type, clarify latest reading Anssi Kostiainen via GitHub
• Re: [sensors] Introduce a Reading Change Treshold concept Anssi Kostiainen via GitHub
• Re: [battery] Allow use in same-origin children Ian Clelland via GitHub

Wednesday, 20 September 2017

• Re: [battery] Allow use in same-origin children Anssi Kostiainen via GitHub
• Re: [battery] Allow use in same-origin children Dominique Hazael-Massieux via GitHub
• Re: [battery] Allow use in same-origin children Anssi Kostiainen via GitHub
• Closed: [sensors] Find a clearer name for the sensor concept Mikhail Pozdnyakov via GitHub
• Re: [sensors] Fix #193: Define extension spec Security & Privacy expectations Anssi Kostiainen via GitHub
• Closed: [sensors] Security issues when used in combination with other APIs Anssi Kostiainen via GitHub
• Re: [sensors] Fix Bikeshed custom header rendering bug Anssi Kostiainen via GitHub
• Re: [accelerometer] Why unrestricted double for acceleration readings? Mikhail Pozdnyakov via GitHub
• Re: [sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 Mikhail Pozdnyakov via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Alexander Shalamov via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Alexander Shalamov via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Alexander Shalamov via GitHub
• Re: [sensors] Answer Security and Privacy self review questionnaire Alexander Shalamov via GitHub
• Closed: [sensors] granularity of Permission name for concrete/ fusion sensors Alexander Shalamov via GitHub
• Closed: [sensors] Simplify extension of the Permissions API for concrete sensor implementations Alexander Shalamov via GitHub
• Re: [battery] Allow use in same-origin children Mounir Lamouri via GitHub

Tuesday, 19 September 2017

• Re: [sensors] Security issues when used in combination with other APIs Lukasz Olejnik via GitHub
• Re: [sensors] Add information to "Extending the Permission API" section Rick Waldron via GitHub
• Closed: [sensors] Review Security and Privacy questionnaire Rick Waldron via GitHub
• Re: [sensors] Answer Security and Privacy self review questionnaire Rick Waldron via GitHub
• Re: [battery] Allow use in same-origin children Rick Byers via GitHub
• Re: [sensors] Answer Security and Privacy self review questionnaire Dominique Hazael-Massieux via GitHub
• Re: [sensors] Security issues when used in combination with other APIs Anssi Kostiainen via GitHub
• Re: [sensors] Answer Security and Privacy self review questionnaire Alexander Shalamov via GitHub
• Re: [accelerometer] Why unrestricted double for acceleration readings? Alexander Shalamov via GitHub
• Re: [sensors] Redefine [=sensor=] concept Anssi Kostiainen via GitHub
• Re: [sensors] Security issues when used in combination with other APIs Dominique Hazael-Massieux via GitHub
• Re: [sensors] Security issues when used in combination with other APIs Anssi Kostiainen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Alexander Shalamov via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Alexander Shalamov via GitHub
• Re: [battery] Allow use in same-origin children Anssi Kostiainen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Mikhail Pozdnyakov via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Mikhail Pozdnyakov via GitHub
• Re: [sensors] Fix Bikeshed custom header rendering bug Anssi Kostiainen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub

Monday, 18 September 2017

• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Rick Waldron via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Rick Waldron via GitHub
• Re: [sensors] Tie [=latest reading=] map to an origin Anssi Kostiainen via GitHub
• Re: [sensors] Answer Security and Privacy self review questionnaire Alexander Shalamov via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Mikhail Pozdnyakov via GitHub
• Re: [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• [sensors] Undefined values makes GS a pain to work with using TypeScript Kenneth Rohde Christiansen via GitHub
• Re: [sensors] Tie [=latest reading=] map to an origin Mikhail Pozdnyakov via GitHub
• Re: [sensors] Update geolocation.js polyfill Anssi Kostiainen via GitHub
• Re: [sensors] Update geolocation.js polyfill Anssi Kostiainen via GitHub

Friday, 15 September 2017

• Re: [sensors] Tie [=latest reading=] map to an origin Lukasz Olejnik via GitHub
• Re: [sensors] Tie [=latest reading=] map to an origin Mikhail Pozdnyakov via GitHub
• Re: [sensors] Tie [=latest reading=] map to an origin Alexander Shalamov via GitHub
• Re: [sensors] Tie [=latest reading=] map to an origin Mikhail Pozdnyakov via GitHub
• [accelerometer] Why unrestricted double for acceleration readings? Dominique Hazael-Massieux via GitHub

Thursday, 14 September 2017

• Re: [sensors] Security issues when used in combination with other APIs Lukasz Olejnik via GitHub

Wednesday, 13 September 2017

• Re: [sensors] Security issues when used in combination with other APIs Anssi Kostiainen via GitHub
• Re: [sensors] Review Security and Privacy questionnaire Anssi Kostiainen via GitHub

Tuesday, 12 September 2017

• Re: [sensors] Review Security and Privacy questionnaire Rick Waldron via GitHub
• [sensors] Review Security and Privacy questionnaire Alexander Shalamov via GitHub

Friday, 8 September 2017

• Re: [sensors] Investigate using PWA installed status as indication of user intent Anssi Kostiainen via GitHub
• Closed: [sensors] Investigate using PWA installed status as indication of user intent Anssi Kostiainen via GitHub
• Re: [sensors] Security issues when used in combination with other APIs Anssi Kostiainen via GitHub

Thursday, 7 September 2017

• Re: [sensors] Investigate using PWA installed status as indication of user intent Anssi Kostiainen via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Alexander Shalamov via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Anssi Kostiainen via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Tobie Langel via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Alexander Shalamov via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Tobie Langel via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Alexander Shalamov via GitHub
• Re: [sensors] Relation to Permissions API Mikhail Pozdnyakov via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Tobie Langel via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Anssi Kostiainen via GitHub
• Re: [sensors] Investigate using PWA installed status as indication of user intent Mikhail Pozdnyakov via GitHub
• Re: [sensors] Security issues when used in combination with other APIs Mikhail Pozdnyakov via GitHub
• Re: [sensors] Addressing finger printing concerns for sensor APIs Anssi Kostiainen via GitHub
• Re: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration Alexander Shalamov via GitHub
• Re: [sensors] Addressing finger printing concerns for sensor APIs Alexander Shalamov via GitHub

Wednesday, 6 September 2017

• Re: [sensors] Annotate interface with [Exposed] extended attribute Anssi Kostiainen via GitHub
• Re: [sensors] Use [Exposed=Window] Alexander Shalamov via GitHub
• Re: [sensors] Use [Exposed=Window] Anssi Kostiainen via GitHub
• Re: [sensors] Use [Exposed=Window] Anssi Kostiainen via GitHub
• Re: [sensors] Use [Exposed=Window] Dominique Hazael-Massieux via GitHub

Monday, 4 September 2017

• Re: [ambient-light] Fix #37: Add cross-origin leaks, hijacking browsing history Anssi Kostiainen via GitHub
• Closed: [ambient-light] Exfiltrating data across origins Anssi Kostiainen via GitHub

Sunday, 3 September 2017

• Re: [ambient-light] Fix #37: Add cross-origin leaks, hijacking browsing history Lukasz Olejnik via GitHub

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