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

Saluton TAG!

I'm requesting a TAG review of `display_override`.

Add a new field to the web manifest, "display-override", where a developer can specify an explicit display fallback chain they would like applied.

Example of a website that wants "minimal-ui" to fall back to "standalone" (currently not possible [due to the static fallback chain in the spec ](https://w3c.github.io/manifest/#display-modes) for `display`).

```json
{
  "display": "standalone",
  "display-override": ["minimal-ui"],
}
```

  - Explainer¹ (minimally containing user needs and example code): https://github.com/dmurph/display-mode/blob/master/explainer.md

  - Security and Privacy self-review²: [url]
  - GitHub repo (if you prefer feedback filed there): https://github.com/dmurph/display-mode

  - Primary contacts (and their relationship to the specification):
      - Daniel Murphy (@dmurph), Google
      - Matt Giuca (@mgiuca), Google
  - Organization/project driving the design: Google
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/features/5728570678706176


Further details:

  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - The group where the incubation/design work on this is being done (or is intended to be done in the future): w3c/Manifest
  - The group where standardization of this work is intended to be done ("unknown" if not known): w3c
  - Existing major pieces of multi-stakeholder review or discussion of this design:  
    - https://github.com/dmurph/display-mode/issues

    - https://groups.google.com/a/chromium.org/g/blink-dev/c/WvIeZT8uSzw

  - Major unresolved issues with or opposition to this design:
    - I like https://github.com/dmurph/display-mode/issues/10

  - This work is being funded by: Google

You should also know that...

This is intended to be a minor behavioral change to the way display modes are processed & specified. This is currently blocking new display modes like tabbed & custom window overlay mode, as they cannot place themselves in the current display list without significant problems.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  🐛 open issues in our GitHub repo for **each point of feedback**


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