[w3c/manifest] Display mode "standalone" inconsistently handled by browsers (#673)

For display mode `"standalone"`, the [spec](https://www.w3.org/TR/appmanifest/#dfn-display-mode) has the following to say (emphasis mine):

*"Opens the web application to look and feel like a standalone native application. This can include the application having a different window, its own icon in the application launcher, etc. In this mode, the user agent will exclude standard browser UI elements such as an URL bar, but **can include other system UI elements such as a status bar and/or system back button**."*

Now of course Edge and Chrome OS handle this differently **on desktop**, where Edge would [show a back button](https://www.youtube.com/watch?v=6fb-t9ffDvo&feature=youtu.be&t=745) (courtesy of @boyofgreen), and [Chrome OS wouldn't show a back button](https://cdn-images-1.medium.com/max/1200/1*YdAiADb46bjX9O6wNryhsg.jpeg) (courtesy of @kenchris).

**On mobile**, the general idea seems to be to not show any browser UI at all, which causes navigation issues for devices without a dedicated system ("hardware") back button as on Android, for example [in iOS](https://medium.com/@firt/progressive-web-apps-on-ios-are-here-d00430dee3a7#1edc) (see the screenshot, courtesy of @firtman).

The spec should probably add more guidance as to when to show a back button in `"standalone"` mode and when not; basing the decision on the presence or absence of a system ("hardware") back button seems like a reasonable default. 



-- 
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/673