- From: Brad Triebwasser <notifications@github.com>
- Date: Tue, 02 May 2023 13:29:55 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/840@github.com>
こんにちは TAG-さん!
I'm requesting a TAG review of Fullscreen Popup Windows.
This proposal aims to reduce user and developer friction for initiating a fullscreen experience on the desired display of a multi-screen device. The proposed web platform enhancement allows web applications to open a new window in HTML [fullscreen](https://fullscreen.spec.whatwg.org/) mode on a specific display with a single user gesture.
- Explainer: https://github.com/bradtriebwasser/fullscreen-popup/blob/main/EXPLAINER.md
- User research: No additional research beyond the feature request (eg: [1](https://github.com/w3c/window-placement/issues/7)) and this feature may be used as a basis for some other feature requests ([2](https://github.com/w3c/window-management/issues/92), [3](https://github.com/w3c/window-placement/issues/92))
- Security and Privacy self-review: https://github.com/bradtriebwasser/fullscreen-popup/blob/main/security_and_privacy.md
- GitHub repo (if you prefer feedback filed there): https://github.com/bradtriebwasser/fullscreen-popup
- Primary contacts (and their relationship to the specification):
- [Author] Brad Triebwasser (@bradtriebwasser) - Google
- [Contributor & author of original Window Management API] Mike Wasserman (@michaelwasserman) - Google
- Joshua Bell (@inexorabletash), [Google] (Spec editor)
- Anssi Kostiainen (@anssiko), [Intel] ([Second Screen WG](https://www.w3.org/2014/secondscreen/) co-chair)
- Organization/project driving the design: Google Chrome
- External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/6002307972464640?context=myfeatures
Further details:
- [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
- The group where the incubation/design work on this is being done (or is intended to be done in the future): [Second Screen WG](https://www.w3.org/2014/secondscreen/)
- The group where standardization of this work is intended to be done ("unknown" if not known): [Second Screen WG](https://www.w3.org/2014/secondscreen/)
- Existing major pieces of multi-stakeholder review or discussion of this design:
- A design & discussion was discussed internally and is not publicly available. There is some additional public discussion in the [feature request](https://github.com/w3c/window-management/issues/7) as well as the [feature repository.](https://github.com/bradtriebwasser/fullscreen-popup/issues).
- [Mozilla Standard Position Request](https://github.com/mozilla/standards-positions/issues/714)
- Previous TAG Reviews on the Window Management API: Issue #522, Issue #602, Issue #767
- Major unresolved issues with or opposition to this design: None
- This work is being funded by: Google Chrome
You should also know that...
This feature is mainly an extension to the features already shipped in the Window Management API (Issue #522, Issue #602, Issue #767). This feature adds an alternative & simplified method of creating a fullscreen popup and entering full screen on any display which is already possible with the API (which normally requires user activations). This feature reduces it to a single user activation.
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 [@bradtriebwasser]
------------------------------------------------------------------------------------
--
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/840
You are receiving this because you are subscribed to this thread.
Message ID: <w3ctag/design-reviews/issues/840@github.com>
Received on Tuesday, 2 May 2023 20:30:01 UTC