Re: [w3c/screen-orientation] TPAC 2026 Status Report (Issue #282)

marcoscaceres left a comment (w3c/screen-orientation#282)

**1. Progress in the last 12 months**

Two changes since TPAC 2025: a clarification of what the natural screen orientation means (#278) and @LJWatson added as a co-editor (#280). The busier period on this spec, including the privacy review fixes (#266) and the pre-lock conditions restructure (#267), lands just before Kobe rather than after it.

**2. Blockers to CR**

The spec went through a full wide review round from September 2025. The TAG closed w3ctag/design-reviews#1155 as satisfied, marking API design, web architecture, privacy and accessibility all complete. Privacy closed w3cping/privacy-request#173. Security closed w3c/security-request#101 with "please refer to the specific issues", which means security is not finished with us: the two issues it handed over are the real blockers. #277 asks us to raise the anti-fingerprinting requirements from SHOULD to MUST, and #276 asks for permissions policy integration so an embedder can control orientation data in iframes. The internationalization request, w3c/i18n-request#274, is still open. Six pull requests are also open, including #268 (iframe promise rejection during unload), #270 (continuous monitoring of pre-lock conditions) and #272 (hidden document monitoring during the parallel lock steps).

**3. Testing plan**

web-platform-tests/screen-orientation holds 16 test files.

**4. Next steps, and help wanted**

Resolve #277 and #276, land the open pull requests, and close out the i18n request. After that the spec is in reach of CR.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/screen-orientation/issues/282#issuecomment-5869958499
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/screen-orientation/issues/282/5869958499@github.com>