#530: "display_override" field addition to the Web Manifest

Visit on Github.

Opened Jun 25, 2020

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 for display).

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

Further details:

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

Discussions

2020-07-20

Minutes

Dan: I wonder if David would be happy to close this based on their updates to the explainer? Let's bump to the plenary?

Alice: for accessibility - it would be interesting if something is stand-alone or full screen thwn you don't have access to the browser UI.

Dan: that's general.

Sangwhan: yes - a general issue that hasn't been touched on.

Alice: it cuts both ways. I've heard from some screen reader using that they don't like focus moving into browser chrome... needs more thought.

Sangwhan: it effects people. Payments had explicit stuff on what browsers should be able to do.

Dan: note - as part of the work on updating the docs in MDN https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps I've asked for Leonie's input.

Alice: I'd be surprised if the result came back as something other than "the web doesn't have as rich accessibility support as native apps". My day job is trying to fix that. It's difficult because of privacy.

Hadley & Dan: [express alarm