[w3ctag/design-reviews] WG Revision: Screen Orientation (Issue #1155)

siusin created an issue (w3ctag/design-reviews#1155)

### Specification

https://www.w3.org/TR/2023/WD-screen-orientation-20230809/

### Explainer

https://w3c.github.io/screen-orientation/demo/index.html

### Links

- The WG's request for this TAG review: [Web Applications Working Group](https://www.w3.org/groups/wg/webapps)
- TAG review of the previous version of this specification, if any: https://github.com/w3ctag/design-reviews/issues/157; https://github.com/w3ctag/design-reviews/issues/33; https://github.com/w3ctag/design-reviews/issues/7
- A description of what has changed since our previous review: This spec has already been reviewed by the TAG multiple times, so feel free to skip it

Feature 1: Prevent hidden documents from locking orientation
- An introduction to the feature, aimed at unfamiliar audiences: https://www.w3.org/TR/2023/WD-screen-orientation-20230809/#handling-page-visibility-changes
- A description of the problems that end-users were facing before this proposal: https://github.com/w3c/screen-orientation/issues/221
- Examples of how to use the proposal to solve the end-users' problems: https://w3c.github.io/screen-orientation/demo/index.html
- What do the end-users experience with this proposal: https://www.w3.org/TR/2023/WD-screen-orientation-20230809/#handling-page-visibility-changes
- User research you did to validate the problem and/or design, if any: https://github.com/w3c/screen-orientation/pull/232#issue-1425156650
- Web Platform Tests:  https://github.com/web-platform-tests/wpt/pull/38511

Feature 2: Resolving the promise after the change event is fired
- An introduction to the feature, aimed at unfamiliar audiences: https://www.w3.org/TR/2023/WD-screen-orientation-20230809/#applying-an-orientation-lock
- A description of the problems that end-users were facing before this proposal: https://github.com/w3c/screen-orientation/issues/120
- Examples of how to use the proposal to solve the end-users' problems: 
- What do the end-users experience with this proposal: 
- User research you did to validate the problem and/or design, if any: [Previous discussion with the TAG](https://github.com/w3c/screen-orientation/pull/147#issuecomment-460476428)
- Web Platform Tests:  https://github.com/web-platform-tests/wpt/pull/15267

### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo: https://github.com/w3c/screen-orientation/
- Primary contacts:
  - Marcos Cáceres (@marcoscaceres ),  Apple Inc., Editor, co-chair of the WebApps WG
- Organization/project driving the specification: W3C
- This work is being funded by: W3C WebApps WG
- Primary standards group developing this feature: [Web Applications Working Group](https://www.w3.org/groups/wg/webapps)
- Incubation and standards groups that have discussed the design: https://github.com/w3ctag/design-reviews/issues/7


### Feedback so far

- Active horizontal reviews: https://github.com/w3cping/privacy-request/issues/173; https://github.com/w3c/security-request/issues/101; https://github.com/w3c/i18n-request/issues/274; https://github.com/w3c/a11y-request/issues/126

- Multi-stakeholder feedback:
  - Chromium comments: supported
  - Mozilla comments: supported, but not listed in the dashboard
  - WebKit comments: supported, but not listed in the dashboard
- Major unresolved issues with or opposition to this specification: None
- Status/issue trackers for implementations:

### You should also know that...

_No response_

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1155


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1155
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1155@github.com>