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

OK, I permuted the example the wrong way.  Why should it not be (given the current spec):

```
{
  "display": "minimal-ui",
  "display-override": ["minimal-ui", "standalone"],
}
```
which seems to have the advantage that it would use `minimal-ui` in all implementations that support it.  Or if the developer doesn't want that because they feel it's really critical to avoid `browser` at all costs, then the example ought to say that that's the reason for writing it the way it's written.  (All the explainer says about the example is "The developer prefers `minimal-ui` but can settle for `standalone`.")

This concern feels true with a number of the other examples in the explainer; it's not clear to me why these examples are the recommended ways of achieving the results, at least in the presence of some implementations that support the feature and some that don't.  (I guess that's not a permanent situation, but it's one that probably matters for a while and for the period when the explainer is likely to be relevant.)

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