- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Thu, 16 Apr 2026 07:27:26 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/pull/1215/review/4121652286@github.com>
@saschanaz commented on this pull request.
> </p>
<p>
When the [=manifest/display=] member is missing, or if there is no
valid [=manifest/display=] member, the user agent uses the [=display
- mode/browser=] <a>display mode</a> as the <a>default display mode</a>.
- As such, the user agent MUST support the [=display mode/browser=]
- <a>display mode</a>.
+ mode/browser=] <a>display mode</a> as the <a>applied display
+ mode</a>. As such, the user agent MUST support the [=display
+ mode/browser=] <a>display mode</a>.
link to display mode twice?
> @@ -2937,21 +2937,21 @@ <h2>
returns `false`.
</p>
<p>
- Once a user agent [=applies=] a particular <a>display mode</a> to an
- <a>application context</a>, it becomes the <dfn>default display
- mode</dfn> for the <a>top-level browsing context</a> (i.e., it is used
- as the display mode when the window is <a>navigated</a>). The user
- agent MAY override the <a>default display mode</a> for security reasons
- (e.g., the <a>top-level browsing context</a> is <a>navigated</a> to
- another origin) and/or the user agent MAY provide the user with a means
- of switching to another <a>display mode</a>.
+ Once a manifest is [=applied=] to a <a>top-level browsing context</a>,
+ the resulting <a>display mode</a> becomes the <dfn>applied display
result becomes the result? maybe "resulting display mode is referred as" or something like it?
> @@ -2937,21 +2937,21 @@ <h2>
returns `false`.
</p>
<p>
- Once a user agent [=applies=] a particular <a>display mode</a> to an
- <a>application context</a>, it becomes the <dfn>default display
- mode</dfn> for the <a>top-level browsing context</a> (i.e., it is used
- as the display mode when the window is <a>navigated</a>). The user
- agent MAY override the <a>default display mode</a> for security reasons
- (e.g., the <a>top-level browsing context</a> is <a>navigated</a> to
- another origin) and/or the user agent MAY provide the user with a means
- of switching to another <a>display mode</a>.
+ Once a manifest is [=applied=] to a <a>top-level browsing context</a>,
+ the resulting <a>display mode</a> becomes the <dfn>applied display
+ mode</dfn> for that <a>top-level browsing context</a> (i.e., it is the
+ display mode used when the window is <a>navigated</a>). The user agent
+ MAY override the <a>applied display mode</a> for security reasons
override or affect? "applied display mode" sounds like the final result so being able to override it sounds like final-really-final.
--
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1215#pullrequestreview-4121652286
You are receiving this because you are subscribed to this thread.
Message ID: <w3c/manifest/pull/1215/review/4121652286@github.com>
Received on Thursday, 16 April 2026 14:27:30 UTC