Re: [w3c/manifest] `display-mode` CSS media feature should include `"display_override"` values (#952)

I think the difficulty here, the thing to keep in mind, is that these fallback chains are really tricky for these advanced use cases (maskable, tabbed, etc). What works for one developer might not work for another. This is why we slightly preferred having the new display modes only be supported by specifying in display_override, as this would make the fallback chain more obvious for the developer and they could actively make that choice, instead of having a 'default' fallback chain and then wonder whey
1. Why browsers that don't support `tabbed` don't support their webapp (say fallback for tabbed is just browser), or
2. Why their app, which requires `maskable` to operate correctly, shows up as `standalone` on certain browsers that don't support that display mode (say fallback for is defined as you mentioned above).

They can still get out of those problems by using `display_override`, but it's a little less obvious. Something to consider here before we jump to adding stuff to this list 😄 

-- 
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/952#issuecomment-781524185