Implementation & new charter update

Hi All,

I'd like to let you know of couple of recent advances:

* Chrome 67 Stable channel is now shipping Generic Sensor-based motion sensors [1] defined in this group. Thanks to the broader community that made this possible, including spec people, browser vendors, horizontal groups, security and privacy researchers who helped us make these next-gen Sensor APIs privacy-enabling by design. Special thanks to Rick Waldron for contributing the initial API proposal.

Now we should expect to get feedback based on real-world usage across this huge user base. As usual, this feedback should be considered carefully, and we should delineate any spec-related issues from implementation issues. Spec issues should be file against the spec repos (https://www.w3.org/das/roadmap), and implementation issues against the implementation (https://crbug.com/new). In some cases it may not be clear where to file an issue, and in such cases I'd recommend filing a spec issue since we have implementers in this group who can find the root cause and report the issue in the right place.

* The AC review of the proposed new charter for the Devices and Sensors Working Group [2] has concluded and we're on track to have the new charter operational starting 1 July 2018. Thank you for your wide support! I'm excited for the future of this group.

Thanks,

-Anssi (Devices and Sensors Working Group)

[1] https://www.chromestatus.com/features/schedule
[2] https://w3c.github.io/dap-charter/DeviceAPICharter.html

Received on Wednesday, 30 May 2018 11:04:40 UTC