Early design review of the **updated** Multi-Screen Window Placement API #602
Description
HIQaH! QaH! TAG!
I'm requesting a TAG review of the updated Multi-Screen Window Placement API.
This proposal introduces incremental improvements to existing screen information and window placement APIs, allowing web applications to be intentional about the experiences they offer to users of multi-screen devices. The API shape has been updated since our last TAG review with feedback from partners and web platform API experts (example).
- Explainer: https://github.com/webscreens/window-placement/blob/master/EXPLAINER.md
- Changes since the last TAG review: https://github.com/webscreens/window-placement/blob/master/CHANGES.md
- Security and Privacy self-review: https://github.com/webscreens/window-placement/blob/master/security_and_privacy.md
- GitHub repo: https://github.com/webscreens/window-placement
- Primary contacts:
- @michaelwasserman: Google, Chromium implementer, editor
- @webscreens: W3C Second Screen Community Group (incubation group)
- Organization/project driving the design: Google/Chromium & W3C Second Screen Community Group
- External status/issue trackers for this feature: Chrome Status and Chrome Feature Issue
Further details:
- I have reviewed the TAG's API Design Principles
- The group where the incubation/design work on this is being done: W3C Second Screen Community Group
- The group where standardization of this work is intended to be done: W3C Second Screen Work Group (maybe?)
- Existing major pieces of multi-stakeholder review or discussion of this design: Prior TAG review, (API design discussion), W3C Second Screen CG's Form Factors Explained report.
- Major unresolved issues with or opposition to this design: None
- This work is being funded by: Google
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify @michaelwasserman
Thank you!