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

[accelerometer] Why unrestricted double for acceleration readings?

[ambient-light] Fix #37: Add cross-origin leaks, hijacking browsing history

[ambient-light] Use value getter operation and fix illuminance attribute type

[battery] Allow use in same-origin children

[gyroscope] Define Gyroscope sensor type, clarify latest reading

[magnetometer] Add security and privacy questionnaire for Magnetometer

[magnetometer] Use value getter operation and use double as attribute type

[proximity] Align with Generic Sensor API current state

[sensors] Add 'user triggered activation' as mitigation strategy

[sensors] Add information to "Extending the Permission API" section

[sensors] Addressing finger printing concerns for sensor APIs

[sensors] Annotate interface with [Exposed] extended attribute

[sensors] Answer Security and Privacy self review questionnaire

[sensors] API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors

[sensors] bikeshed link errors

[sensors] Clarify sensor frequency concepts

[sensors] Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269

[sensors] Editorial fixes to Extensibility section

[sensors] Fix #193: Define extension spec Security & Privacy expectations

[sensors] Fix Bikeshed custom header rendering bug

[sensors] Future proofing terminology

[sensors] Introduce a Reading Change Treshold concept

[sensors] Introduce Default Sensor concept

[sensors] Introduce the Reading Timestamp concept

[sensors] Investigate using PWA installed status as indication of user intent

[sensors] Make 'Conditions to expose sensor readings' must

[sensors] Redefine [=sensor=] concept

[sensors] Relation to Permissions API

[sensors] Review Security and Privacy questionnaire

[sensors] Security issues when used in combination with other APIs

[sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration

[sensors] Sensor discovery

[sensors] Sensor.timeStamp could be clarified

[sensors] Should a "suspended" state be added

[sensors] Should the API allow setting both samplingFrequency and reportingFrequency?

[sensors] Split security & privacy questionnaire

[sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments

[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

[sensors] Take into account user gestures as an input for security policy enforcement

[sensors] Tie [=latest reading=] map to an origin

[sensors] Undefined values makes GS a pain to work with using TypeScript

[sensors] Update geolocation.js polyfill

[sensors] Use [Exposed=Window]

[sensors] What's the rationale of moving security checks outside of normative requirements?

Closed: [ambient-light] Exfiltrating data across origins

Closed: [sensors] Addressing finger printing concerns for sensor APIs

Closed: [sensors] bikeshed link errors

Closed: [sensors] Define algorithm for suspending / resuming activated sensor objects

Closed: [sensors] Find a clearer name for the sensor concept

Closed: [sensors] granularity of Permission name for concrete/ fusion sensors

Closed: [sensors] Investigate using PWA installed status as indication of user intent

Closed: [sensors] Missing browsing-context focus/unfocus hooks in HTML spec.

Closed: [sensors] Review Security and Privacy questionnaire

Closed: [sensors] Security issues when used in combination with other APIs

Closed: [sensors] Security/privacy concerns beyond fingerprinting -- data exfiltration

Closed: [sensors] Should a "suspended" state be added

Closed: [sensors] Should the API allow setting both samplingFrequency and reportingFrequency?

Closed: [sensors] Simplify extension of the Permissions API for concrete sensor implementations

Closed: [sensors] Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments

Closed: [sensors] Take into account user gestures as an input for security policy enforcement

Closed: [sensors] Undefined values makes GS a pain to work with using TypeScript

Closed: [sensors] What's the rationale of moving security checks outside of normative requirements?

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