Re: [w3c/manifest] minimal-ui "similar to fullscreen" should read "similar to standalone" (#677)

> The reason being that an app in "minimal-ui", was that the app launched fullscreen, then some user gesture caused the UI to appear.

But what does "standalone" mean in that world? Does it mean more permanent UI is on screen than minimal-ui? The text implies that minimal-ui has more stuff in it than standalone.

Also the order is kind of fixed by the fallback chain (explicit in the spec):

fullscreen → standalone → minimal-ui → browser

Since that's the fallback chain, it would imply that each of those modes has a superset of the features of the previous:

fullscreen ⊂ standalone ⊂ minimal-ui ⊂ browser

On this topic, I found another sentence which might be a relic from this era:

"When the fullscreen display mode is applied, it is RECOMMENDED that the user agent provides the end-user a means to consult common information about the web application, such as the origin, start and/or current URL, granted permissions, and associated icon."

I feel like this recommendation shouldn't be specific to fullscreen. Since standalone shows a superset of the UI of fullscreen, it's weird that the above info is recommended in fullscreen but not standalone. Also our security team specifically requested this for standalone mode. Should I delete the qualifier?

-- 
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/677#issuecomment-390859578