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

Hey folks,

I did a lot of brainstorming and I came up with the following proposal:
https://github.com/dmurph/display-mode/blob/master/explainer.md

I call it `display-override`, but I'm open to other names. I think it really neatly solves at least one of the problems here (fallbacks), and leaves room for future improvements like display-modifier if necessary, with the added benefit of fallback logic.

I propose this API change as a first step, allowing new display modes like `tabbed` and `customized` (or whatever that one is be called) in a way that gives developers control of the fallback chain. If only a few more display modes are needed, then this design should work out just fine, and if demand increases for (exponentially different) display customization as more options are introduced, I outline some ideas in the "Future Considerations" section that show how we can accomplish this as well.

Can you all please take a look and tell me what you think? I would love feedback here :)

-- 
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-631645191