- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Thu, 21 Nov 2024 09:06:42 +0000
- To: W3C Devices and Sensors WG <public-device-apis@w3.org>, "public-webapps@w3.org" <public-webapps@w3.org>
- Message-ID: <3E8795A2-B1A7-4A5C-B6E3-F6FCE9E89AF6@intel.com>
Hi Devices and Sensors WG and WebApps WG participants, We have just jointly published the Device Orientation and Motion specification (formerly DeviceOrientation Event) as a new W3C Candidate Recommendation Snapshot (CRS): https://www.w3.org/TR/2024/CR-orientation-event-20241121/ As usual, the latest version you should reference is at: https://www.w3.org/TR/orientation-event/ New features since the previous Candidate Recommendation 18 August 2016 include integration of Permissions Policy and API, which now requires explicit user consent through requestPermission() for accessing device orientation data. Furthermore, updates have been made to the coordinate system explanations and precision requirements to mitigate passive fingerprinting risks. The introduction of the deviceorientationabsolute event enhances applications requiring absolute orientation data. Interfaces are now only available in secure contexts, and security and privacy considerations have been made normative. The specification now also provides a means to automate testing of this API. For more detailed changes, see: https://www.w3.org/TR/orientation-event/#changes For feedback, please file an issue on GitHub: https://github.com/w3c/deviceorientation/issues Congratulations to all the contributors to this effort with special thanks to the editors and implementers, both current and former, for refining this specification and sharing valuable implementation experience. Thanks, -Anssi (DAS WG co-chair)
Received on Thursday, 21 November 2024 09:06:55 UTC