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

[accelerometer] Add Previous Version metadata

[accelerometer] Address DeviceOrientation issue #4

[ambient-light] Add description for use cases

[ambient-light] Ambient Light Sensors to detect RGB colors

[ambient-light] Available in workers?

[ambient-light] Exfiltrating data across origins

[ambient-light] Fix #13: Expand Security and Privacy Considerations

[ambient-light] Fix #23: Move content from Use Cases to Scope

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

[ambient-light] Fix links to sensor and sensorreading

[ambient-light] Light-level deferred to Media Queries Level 5

[ambient-light] Security and Privacy considerations for ALS

[ambient-light] Security and privacy considerations for Ambient Light Events

[ambient-light] What illuminance value should be reported for stopped sensor?

[battery] Allow use from within secure context and top-level browsing context only

[gyroscope] Address DeviceOrientation issue number 4

[gyroscope] Define coordinate system

[gyroscope] Fix #17: Define local coordinate system

[html-media-capture] [meta] Publish a revised Candidate Recommendation

[html-media-capture] Fix references

[html-media-capture] Fix references for CR publication

[proximity] The spec does not use levels

[sensors] Add `Level: none` to the metadata block

[sensors] Add categorization of security and privacy threats

[sensors] Align sensor lifecycle diagram with normative prose

[sensors] Fix #261: Rename Error -> onerror in state diagram

[sensors] Fix 'steps to determine the visibility state' dfn link

[sensors] Fix a couple of algorithms with their use of variables

[sensors] Initial improvements for use cases document

[sensors] Investigate possibility of synchronizing coordinate systems

[sensors] Modify example to use addEventListener and change table style

[sensors] Refer to the latest [FEATURE-POLICY] spec

[sensors] Stop using "incumbent settings object"?

[sensors] Use proper reference in [HTML] for task queue

[wake-lock] new type: location?

[wake-lock] require a secure context for wakelock

[wake-lock] Restrict Wake Lock API to secure context

[wake-lock] Restrict Wake Lock to secure context

Closed: [accelerometer] Address DeviceOrientation issue #4

Closed: [ambient-light] Add description for use cases

Closed: [ambient-light] Available in workers?

Closed: [ambient-light] Light-level deferred to Media Queries Level 5

Closed: [ambient-light] Security and Privacy considerations for ALS

Closed: [ambient-light] Security and privacy considerations for Ambient Light Events

Closed: [ambient-light] What illuminance value should be reported for stopped sensor?

Closed: [gyroscope] Address DeviceOrientation issue number 4

Closed: [gyroscope] Define coordinate system

Closed: [html-media-capture] [meta] Publish a revised Candidate Recommendation

Closed: [sensors] Align sensor lifecycle diagram with normative prose

Closed: [sensors] Listing threats

Closed: [sensors] Should a Sensor instance be deactivated/stopped when being garbage collected?

Closed: [sensors] w3c.github.io/sensors/usecases.html 404s

Closed: [sensors] What are the event.type strings?

Closed: [wake-lock] Restrict Wake Lock to secure context

Last message date: Thursday, 31 August 2017 14:17:43 UTC