From 71600c4d93cf74ef46d84469628496d2d30ba2f7 Mon Sep 17 00:00:00 2001 From: Reilly Grant Date: Wed, 12 Feb 2025 01:18:57 +0000 Subject: [PATCH] Process: Set CRS comment deadline to 2025-03-15 SHA: 5adbbea4a21d004927f33e40ff4d5a70cc85de73 Reason: push, by reillyeon Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- index.html | 1890 +++++++++++++++++++++++++++++++++------------------- 1 file changed, 1202 insertions(+), 688 deletions(-) diff --git a/index.html b/index.html index 2f5961b..5366086 100644 --- a/index.html +++ b/index.html @@ -5,9 +5,11 @@ Device Orientation and Motion - + - + + + - + - + -

Device Orientation and Motion

-

Editor’s Draft,

+

Editor’s Draft,

More details about this document
@@ -916,7 +989,7 @@

Device Orientation and Motion

- +
@@ -944,7 +1017,7 @@

public-webapps@w3.org (subscribe, archives).

This document is governed by the 03 November 2023 W3C Process Document.

-

New features since publication as a Candidate Recommendation include integration of Permissions Policy and API, which now requires explicit user consent through requestPermission() for accessing device orientation data. 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 (marked at risk). 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 (marked at risk). See § 10 Changes section for more information.

+

New features since publication as a Candidate Recommendation include integration of Permissions Policy and API, which now requires explicit user consent through requestPermission() for accessing device orientation data. 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 (marked at risk). 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 (marked at risk). See § 10 Changes section for more information.