Re: CfC to publish DeviceOrientation Event CR Snapshot - review by 11 March

Thanks Macros,

I’ve opened a PR where to note any at risk issues: https://github.com/w3c/deviceorientation/pull/142 — if the joint group believes we could transition from this CR Snapshot to Proposed Rec then at risk items are important.

I asked the group about the testing story earlier, here’s the response: https://github.com/w3c/deviceorientation/issues/130#issuecomment-1917516374


As for the CRS transition requirements, 100% pass rate or a complete test suite is not expected. However, we should be able to explain the reason for the test failures, note any known wpt or implementation gaps.

Thanks,

-Anssi

On 5. Mar 2024, at 7.15, Marcos Caceres <caceres_m@apple.com> wrote:

Hi Anssi,

Thanks for sending the CFC! It looks like there are significant number of failures on both WebKit and Gecko in relation to the API:

https://wpt.fyi/results/orientation-event?label=experimental&label=master&aligned


We might need to evaluate if there are things that should be marked “at risk” in the spec due to lack of second implementation (or if the implementations are just buggy… but it’s still a concern that both Gecko and WebKit are have a significant failure rate).

I also didn’t see any tests for permission policy there? It might be good for us to put together a more comprehensive implementation report before proceeding to CR.

Kind regards,
Marcos



On 5 Mar 2024, at 1:58 AM, Kostiainen, Anssi <anssi.kostiainen@intel.com> wrote:

Hi DAS+WebApps WGs,

This is a Call for Consensus to publish the DeviceOrientation Event specification as a new Candidate Recommendation Snapshot (CRS).

Please review the latest Working Draft [1] that will be used as the basis for this publication and reply to this mail by 12 March 2024 if you have any concerns with this publication plan. Silence is considered consent.

The intent of this publication is to match current implementations. An issue triage meeting was organized on 12 Feb 2024 [3] and the remaining open issues [4] were considered non-blocking for this publication.

Wide review status is tracked in [5]. No concerns raised to date. Both a11y and privacy reviews are expected to be closed this week, i18n and security reviews have been completed. TAG review is in flight.

Summary of notable changes since the previous publication:

This specification became a joint deliverable between the Devices and Sensors Working Group and WebApps Working Group on 21 February 2024. The DeviceOrientation Event specification was previously published as a Candidate Recommendation Snapshot-equivalent in August 2016 and was retired in 2017 due to the Geolocation Working Group closure. In 2019 Devices and Sensors Working Group adopted this specification and during 2019-2024 made substantial interoperability, test automation, privacy and editorial improvements as outlined in the Changes section [2].

An update to the status of this document is staged in [6] and welcomes review, including for the Proposed Rec transition requirements.

The chairs will consider all feedback including from wide reviews currently in flight prior to this transition.

Thank you for your contributions and support that make this publication happen.

On behalf of the DAS WG and WebApps WG chairs,

-Anssi (DAS WG co-chair)

[1] https://www.w3.org/TR/orientation-event/

[2] https://www.w3.org/TR/orientation-event/#changes

[3] https://lists.w3.org/Archives/Public/public-device-apis/2024Feb/0003.html

[4] https://github.com/w3c/deviceorientation/issues

[5] https://github.com/w3c/deviceorientation/issues/130

[6] https://github.com/w3c/deviceorientation/pull/142