Re: [w3c/manifest] "Default display mode" section is super confusing (Issue #1024)

dmurph left a comment (w3c/manifest#1024)

Assigning to @christianliebel to take a look

spec text right now:

> Once a user agent [applies](https://w3c.github.io/manifest/#dfn-apply) a particular [display mode](https://w3c.github.io/manifest/#dfn-display-mode) to an [application context](https://w3c.github.io/manifest/#dfn-application-context), it becomes the default display mode for the [top-level browsing context](https://html.spec.whatwg.org/multipage/document-sequences.html#top-level-browsing-context) (i.e., it is used as the display mode when the window is [navigated](https://html.spec.whatwg.org/multipage/browsing-the-web.html#navigate)). The user agent MAY override the [default display mode](https://w3c.github.io/manifest/#dfn-default-display-mode) for security reasons (e.g., the [top-level browsing context](https://html.spec.whatwg.org/multipage/document-sequences.html#top-level-browsing-context) is [navigated](https://html.spec.whatwg.org/multipage/browsing-the-web.html#navigate) to another origin) and/or the user agent MAY provide the user with a means of switching to another [display mode](https://w3c.github.io/manifest/#dfn-display-mode).

Feedback on that existing spec line:
- The default display mode definition can change to 'effective display mode'
- Then, the next line should be saying...
  - When the manifest is applied, the user agent may choose the application's requseted display mode
  - the user agent may choose a different display mode
    - as the user might have customized this (e.g. chromium you can have apps open in a browser tab, and still have the app features like os itnegration stufff & link_handlign)
    - or, the UA may make the decision for security purposes

Then the requested display mode is just the parsed display field (although the WICG spec here has `display_override` as well to allow better dev control here).


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1024#issuecomment-4216313413
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1024/4216313413@github.com>

Received on Thursday, 9 April 2026 17:50:24 UTC