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

@tomayac if you look in the video at https://youtu.be/6fb-t9ffDvo?t=762 
I'm not sure why Microsoft is not opening the app actually in full screen. For games, it makes a lot of sense to open directly in fullscreen. 

Here a problem arises. For Chrome, full screen is properly interpreted as taking up entire display area, which follows the spec. For Microsoft, it takes up only the entire area of the window effectively becoming standalone.

If my app manages the back button its self, I would not want the OS to manage it. 
To implement the correct behavior across both browsers, when I detect the useragent as Chrome, in the PWA, I'll have to send manifest with the display property as standalone. When the useragent is Edge, I'd have to send another version of the manifest that has display property as fullscreen to give an expected experience. 

Can we not make the spec strict so that if a developer says something the browser actually has to follow it, or at-least offer a strict version such as fullscreen-strict or standalone-strict. This hacky way I am having to do to provide a consistent with Edge is going to become a maintenance nightmare. 

And maybe we should document the default behavior for all 3 major browsers for all properties (Chrome, Edge and Safari)  because even I am confused despite reading all the documentation. 

-- 
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#issuecomment-394556868