[w3c/manifest] Proposal: Display Mode 'standalone-no-ui' (#659)

It's common for desktop applications to hide the default window controls provided by the operating system, and instead provide their own custom-styled controls. For instance, [Discord](https://discordapp.com/), a text and voice chat app, does this:

![Discord's custom window control UI](https://i.imgur.com/cL6Sksx.png)

It doesn't seem that this is currently possible with the existing four display modes: `fullscreen`, `standalone`, `minimal-ui`, and `browser`. Specifically, the `standalone` display mode uses the operating system's default window chrome. For example, the [Notes](https://sii.im/playground/notes/) app appears like this:

![Notes' default operating system window chrome](https://i.imgur.com/6VZLyrz.png)

It would be really useful to have a display mode like `standalone-no-ui`, which would hide the operating system's default window chrome. The Web app would then essentially have a blank slate on which it could apply structure, styling, and functionality as it wishes.

This display mode is intended for desktop, and I'm unsure how it would apply to mobile. On mobile, it could fall back to the normal `standalone`.

`minimize()`, `maximize()`, and `close()` methods would also be required in JavaScript. Their use would probably be restricted to only work in the `standalone` and `standalone-no-ui` contexts, as their functionality in normal browser websites could allow undesirable user experiences.

The specific proposals outlined here may or may not be the best way to go about achieving the general idea, but I hope they can get the ball rolling on working out a way to achieve that general idea by some means, because it would be super useful.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/659