Contact [email protected], [email protected] Explainer https://github.com/bradtriebwasser/fullscreen-popup/blob/main/EXPLAINER.md
SpecificationTBD Summary Adds the ability to open a popup directly to full-screen. Adds an additional windowFeatures <https://developer.mozilla.org/en-US/docs/Web/API/Window/open#windowfeatures> parameter to the window.open() <https://developer.mozilla.org/en-US/docs/Web/API/Window/open> JavaScript API which allows the caller to open a popup directly to full-screen on the display that would contain the popup (based on screenX <https://developer.mozilla.org/en-US/docs/Web/API/Window/open#left>/screenY <https://developer.mozilla.org/en-US/docs/Web/API/Window/open#top>). This eliminates the need for the developer to manually transition a popup into full-screen which could <https://github.com/bradtriebwasser/fullscreen-popup/blob/main/EXPLAINER.md#spec-notes> require a new user activation <https://html.spec.whatwg.org/multipage/interaction.html#tracking-user-activation> signal. Blink componentBlink>Fullscreen <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFullscreen> TAG reviewNot yet requested TAG review statusPending Risks Interoperability and Compatibility *Gecko*: No signal ( https://github.com/mozilla/standards-positions/issues/714) *WebKit*: No signal ( https://github.com/WebKit/standards-positions/issues/101) *Web developers*: Positive https://github.com/w3c/window-placement/issues/7 https://github.com/w3c/window-placement/issues/98#top https://github.com/w3c/window-placement/issues/92 *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? Considered low risk since this is introducing a new API. Goals for experimentation Gain early developer and partner feedback and identify any UX pain points. Ongoing technical constraints Feature is only available when the flag is enabled. Empty popups (about:blank) not working is a known issue. Fix expected in M114. Further constraints (same-origin, permission policy, etc.) which restrict this feature may be introduced in subsequent releases. Debuggability This feature utilizes the existing windowFeatures string parameter in Window.open() <https://developer.mozilla.org/en-US/docs/Web/API/Window/open> and does not modify any structured (i.e. WebIDL) API surface. This feature will integrate with existing fullscreen APIs which developers can use for debugging (document.fullscreenElement, fullscreenchange, and fullscreenerror, etc.). Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?No Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?No. A single-screen test will be added, but web platform tests are limited to single display environments, so testing fullscreen popups across displays will not be possible in web platform tests. Flag name--enable-features=FullscreenPopupWindows Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1142516 Launch bughttps://launch.corp.google.com/launch/4211164 Estimated milestones DevTrial on desktop 113 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/6002307972464640 Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/t8lL5RvfLJY This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALEeEUDUhT8Q18-COhJj%3DcgGCP5869WCP%2BxYwHg%3DUYLh7KUycA%40mail.gmail.com.
