Skip to content

Commit

Permalink
clarify the definition of "navigation scope", "applied", and off-scop…
Browse files Browse the repository at this point in the history
…e theming (#1151)
  • Loading branch information
marcoscaceres authored Nov 7, 2024
1 parent 40cf2c7 commit ec8a23b
Showing 1 changed file with 30 additions and 19 deletions.
49 changes: 30 additions & 19 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1076,12 +1076,17 @@ <h3>
</p>
<p>
If the user agent honors the value of the [=manifest/theme_color=]
member as the <a>default theme color</a>, then that color serves as
the <a>theme color</a> for all browsing contexts to which the
manifest is <a>applied</a>. However, a document may override the
<a>default theme color</a> through the inclusion of a valid [[HTML]]
[^meta^] element whose [^meta/name^] attribute value is
`"theme-color"`.
member as the [=default theme color=], then that color serves as the
[=theme color=] for all [=browsing contexts=] to which the manifest
is [=applied=]. However, the user agent MAY override the [=default
theme color=] if a [=document=] whose [=Document/URL=] is
[=URL/within scope=] of the [=application context=]'s [=manifest=]
includes a [^meta^] element whose [^meta/name^] attribute is
"[^meta/name/theme-color^]". However, the user agent SHOULD NOT
override the [=default theme color=] via a [^meta^] element whose
[^meta/name^] attribute is "theme-color" for [=documents=]'
[=Document/URL=] are not [=URL/within scope=], since the application
has no control over these documents.
</p>
<p data-cite="CSS-COLOR-4">
The user agent MAY ignore the <a>theme color</a>'s [=alpha
Expand Down Expand Up @@ -1703,12 +1708,23 @@ <h3 id="applying">
Applying the manifest
</h3>
<p>
A [=Document/processed manifest=] is <dfn data-export=""
data-local-lt="apply|applying">applied</dfn> to a <a>top-level
browsing context</a>, meaning that the members of the
[=Document/processed manifest=] are affecting the presentation or
behavior of a browsing context.
A [=Document/processed manifest=] is <dfn data-lt=
"apply|applying">applied</dfn> to a [=top-level browsing context=],
meaning that the members of the [=manifest=] are affecting the
presentation and/or behavior of the browsing context. Whenever a
[=top-level browsing context=] is created, the user agent MAY
[=apply=] a manifest to it before [=navigate|navigation=] begins.
</p>
<aside class="note">
Whether to [=apply=] a manifest, and which manifest to apply, is at
the discretion of the user agent, based on the user's actions. For
example, if the user launched an application from the system menu
or from a [=launching a shortcut|shortcut=], the user agent might
create a new [=top-level browsing context=] with that application's
[=manifest=] [=applied=], but it might not do so if the user simply
clicked a bookmark to a URL within the application's
[=manifest/navigation scope=].
</aside>
<p>
A <a>top-level browsing context</a> that has a manifest applied to
it is referred to as an <dfn data-export="">application
Expand All @@ -1730,11 +1746,6 @@ <h3 id="applying">
changed it when the application was <a>installed</a>.
</p>
</aside>
<p>
The appropriate time to <a>apply</a> a manifest is when the
<a>application context</a> is created and before
[=navigate|navigation=] to the <a>start URL</a> begins.
</p>
</section>
<section id="updating">
<h3>
Expand Down Expand Up @@ -2575,9 +2586,9 @@ <h2>
</h2>
<p>
The <dfn data-dfn-for="manifest" data-lt="navigation scope"
data-export="">navigation scope of a manifest</dfn> is the "scope" item
of a [=Document/processed manifest=]. The navigation scope restricts
the set of URLs to which an [=application context=] can be
data-export="">navigation scope of a manifest</dfn> is the
"[=manifest/scope=]" member of a [=Document/processed manifest=]. The
navigation scope is the URLs to which an [=application context=] can be
[=navigated=] while the manifest is [=applied=].
</p>
<div class="note">
Expand Down

0 comments on commit ec8a23b

Please sign in to comment.