Re: [w3c/manifest] More precise control over app window features (#856)

A modification on the "Allow sites to specify an explicit fallback chain" solution could be (to make it even simpler):

When specifying a display option list, if none are supported, then the user agent defaults to 'browser'. All new display options will correspond to a new display mode string, but will only be available in the 'list' version.

For example, `displayMode: 'standalone'` is valid, but `displayMode: 'tabbed'` would not. `displayMode: ['tabbed', 'minimal-ui']` would be valid, and if the user agent doesn't support any of those, it would fall back to `'browser'`

Not necessarily voicing a preference for this solution - just thinking how it could be simpler.

-- 
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/856#issuecomment-605368617