search

explainers-by-googlers / html-fullscreen-without-a-gesture

HTML Fullscreen Without A Gesture
Creative Commons Attribution 4.0 International
0 stars 0 forks source link

Does this encompass the following feature request (links in the description) ? #1

Closed projektorius96 closed 2 months ago

projektorius96 commented 5 months ago

As titled :

If this is relevant, then I'd like to add that Microsoft Edge core team has implemented Shy UI, which is currently default UI for Fullscreen mode over same Chromium and it works so smoothly! The Fullscreen mode toast button (X) should be at least controllable via flags, if not programmatically in Chrome.

Please keep in mind. This is year by year requesting by loyal Chrome users and definitely would contribute a lot to (Game) Developers experience, if pushed successfully !

If this DOES NOT encompass the specification draft, then at least please share your best offer to redirect this matter of concern. Thanks in advance, Nooglers !

projektorius96 commented 5 months ago

I think I found Borderless mode explainer.

If anything to add, please re-open the issue.

projektorius96 commented 2 months ago

As a random passer-by, I was kinda following this a bit and wanted to re-open discussion by adding a few remarks.

Currently the Borderless mode feature is blocking due to some implementation bug of Desktop IWA (DPWA) – in other words, as far as I do understand – once the IWA is implemented, Borderless mode is good to go as a feature.
According to this answer the current status of Borderless mode also remains unknown.

Also see this discussion, and this. Perhaps by upvoting the later one, we could get more attention from Nooglers.

michaelwasserman commented 2 months ago

Upvoting the open Chromium issue Feature Request: Hide (X) toast in fullscreen is likely the best way to represent web developer sentiment regarding Chromium's implementation. Similarly, if the HTML Fullscreen Standard for for FullscreenOptions "hide" is insufficient, I'd raise an issue there. Developers should convey their context and use cases for hiding those transient security-sensitive fullscreen UI elements, especially if it's not already reflected in existing open issues, or if a substantial number of users are adversely affected.

FWIW, this explainer (HTML Fullscreen Without a Gesture) directly cites UI overlays as a valuable trait in its Security Considerations.

Borderless mode is a separately proposed web application display mode that hides the window titlebar. Maximized borderless windows wouldn't show the transient fullscreen UI overlays, IIUC, but they would likely be constrained to the available screen area, i.e. not showing over OS taskbars. Discussion of Borderless mode feedback should be directed to the WICG explainer.

Please do reopen if I have misunderstood something, thanks!