Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Require document to be in scope to be styled by the manifest #791

Closed
wants to merge 4 commits into from
Closed

Require document to be in scope to be styled by the manifest #791

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f897c44
Authority of the manifest's metadata: require the document to be in s…
mgiuca Sep 9, 2019
ebc7550
Add a non-normative note that the app can be installed from a documen…
mgiuca Sep 12, 2019
5c2f0a4
Respec stuff.
mgiuca Sep 26, 2019
6fe490b
Update index.html
marcoscaceres Oct 31, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 39 additions & 9 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,7 +269,7 @@ <h3>
</section>
</section>
<section>
<h2>
<h2 id="installable-web-applications">
Installable web applications
</h2>
<p>
Expand Down Expand Up @@ -326,18 +326,48 @@ <h2>
(at the user agent's discretion; see [[[#installability-signals]]]).
</li>
</ol>
<div class="note" data-link-for="WebAppManifest">
<p>
The {{Document}} might not be <a data-lt=
"within-scope-manifest">within scope</a> of the linked manifest, by
design. For example, a page at <code>https://example.com</code> might
link a manifest with <a>scope</a> <code>"/installable/"</code>,
allowing the top-level page of the site (which itself is not part of
the installable web application) to show installation UI.
</p>
<p>
Implementors need to be aware of this possibility. One consequence is
that if, post install, the user agent opens the document URL in an
<a>application context</a>, it would immediately start showing the
"out of scope" warning UI (that is recommended in
[[[#navigation-scope]]]). Hence, implementors might wish to avoid
Comment on lines +341 to +343
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<a>application context</a>, it would immediately start showing the
"out of scope" warning UI (that is recommended in
[[[#navigation-scope]]]). Hence, implementors might wish to avoid
<a>application context</a>, it would start exhibiting the
"out of scope" behavior (that is recommended in
[[[#navigation-scope]]]). Hence, implementors might wish to avoid

doing this if the {{Document}} is <a data-lt=
"within-scope-manifest">out of scope</a>.
</p>
</div>
<section>
<h3>
Authority of the manifest's metadata
</h3>
<p>
When a <a>manifest</a> is linked from a {{Document}}, it indicates to
the user agent that the metadata is <dfn>authoritative</dfn>: that
is, the user agent SHOULD use the metadata of the manifest instead of
the one in the {{Document}}. However, in cases where metadata is
missing, or in error, a user agent MAY fallback to the {{Document}}
to find suitable replacements for missing manifest members (e.g.,
using `application-name` in place of `short_name`).
When a <a>manifest</a> is linked from a {{Document}}, and the
{{Document}} is <a data-lt="within-scope-manifest">within scope</a>
of the manifest, it indicates to the user agent that the metadata is
<dfn>authoritative</dfn>: that is, the user agent SHOULD use the
metadata of the manifest instead of the one in the {{Document}}.
However, in cases where metadata is missing, or in error, a user
agent MAY fallback to the {{Document}} to find suitable replacements
for missing manifest members (e.g., using `application-name` in place
of `short_name`). The user agent MUST NOT apply the metadata of a
manifest to a {{Document}} that is not <a data-lt=
"within-scope-manifest">within scope</a> of that manifest.
</p>
<p class="note">
A {{Document}} that is not <a data-lt="within-scope-manifest">within
scope</a> of a linked manifest can still be used to install the web
application associated with the manifest, it just can't have the
manifest's metadata applied directly to the document. See the note in
[[[#installable-web-applications]]].
</p>
</section>
<section data-link-for="WebAppManifest">
Expand Down Expand Up @@ -839,7 +869,7 @@ <h4>
</section>
</section>
<section>
<h2>
<h2 id="navigation-scope">
Navigation scope
</h2>
<p data-link-for="WebAppManifest">
Expand Down