Re: [w3ctag/design-reviews] "display_override" field addition to the Web Manifest (#530)

I think that example should probably just be

```json
{
  "display": "standalone"
}
```

No need for the override, right? All user agents must support `display`, and `display` has a defined fallback chain that is expected. What do you expect the fallback behavior to be for your example?

How do you imagine it to work if the new field was a fallback? Would that mean we are redefining the `display` fallback chain? I'd like to avoid that for backwards compatibility (I don't want old/unsupporting browsers to behave differently).

I feel like I failed to describe something here. Another way to think about `display-override` is that it is the 'advanced' mode. If a developer wants a special display mode or if they want extra control over exactly what their fallback chain is, then they use `display-override` (with `display`). Otherwise, they can just use `display`.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/530#issuecomment-655810299