Generic Sensor API Changelog

Significant changes between the latest Editor's Draft and the W3C Working Draft 24 March 2016 reviewed by TAG earlier are the following:

The Background section has been removed, the content from the previous Background section was merged to the description of the default sensor concept.
The Security and privacy considerations section has been extended with new subsections: ‘Types of privacy and security threats’, ‘Mitigation strategies’,’Mitigation strategies applied on a case by case basis‘.
Major changes were made in the Concepts section to provide a better description of how the exposed interfaces should interact with the hardware sensors and their platform representations and to clarify the implementation details for user agents. Changes in the defined concepts:
1. The sensor concept is split into device sensor and platform sensor.
2. New concepts added: reading timestamp, default sensor, sampling frequency, requested sampling frequency, reporting frequency, reading change threshold, conditions to expose sensor readings.
3. Concepts dropped: reporting modes.
The Model section is described in more detail and a descriptive diagram is added. Changes in the subsections:
1. The identifying parameters definition was removed from the ‘Sensor type’ section, deferred to Generic Sensor API Level 2, since it is related to the sensor discovery API.
2. The Sensor section was rewritten to fully match the implementation.
Changes in the API section:
1. The SensorReading interface was merged into the Sensor interface to address API ergonomics issues and GC concerns.
2. Sensor states were moved to internal slots, and activated and hasReading readonly attributes were exposed instead.
3. The onchange event handler was renamed to onreading.
4. The SensorReadingEvent interface was flattened and merged into the Sensor interface.
5. The SensorErrorEvent interface now exposes error of DOMException type instead of Error type.
The Abstract Operations section was completely rewritten to consider implementation feedback and how sensors are exposed on the underlying layers (i.e. platform APIs).
Extensibility section was completed.
Feature Policy integration added: see the Feature Policy mitigation strategy and Extending the Feature Policy API sections.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!