Skip to content

Commit ebc7550

Browse files
committed
Add a non-normative note that the app can be installed from a document that is outside the scope of that app.
Closes #784.
1 parent f897c44 commit ebc7550

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

index.html

+20-1
Original file line numberDiff line numberDiff line change
@@ -326,6 +326,25 @@ <h2 id="installable-web-applications">
326326
(at the user agent's discretion; see [[[#installability-signals]]]).
327327
</li>
328328
</ol>
329+
<div class="note" data-link-for="WebAppManifest">
330+
<p>
331+
The {{Document}} might not be <a data-lt=
332+
"within-scope-manifest">within scope</a> of the linked manifest, by
333+
design. For example, a page at <code>https://example.com</code> might
334+
link a manifest with <a>scope</a> <code>"/installable/"</code>,
335+
allowing the top-level page of the site (which itself is not part of
336+
the installable web application) to show installation UI.
337+
</p>
338+
<p>
339+
Implementors should be aware of this possibility. One consequence is
340+
that if, post install, the user agent opens the document URL in an
341+
<a>application context</a>, it would immediately start showing the
342+
"out of scope" warning UI (that is recommended in <a href=
343+
"#navigation-scope">Navigation scope</a>). Hence, implementors might
344+
wish to avoid doing this if the {{Document}} is <a data-lt=
345+
"within-scope-manifest">out of scope</a>.
346+
</p>
347+
</div>
329348
<section>
330349
<h3>
331350
Authority of the manifest's metadata
@@ -851,7 +870,7 @@ <h4>
851870
</section>
852871
</section>
853872
<section>
854-
<h2>
873+
<h2 id="navigation-scope">
855874
Navigation scope
856875
</h2>
857876
<p data-link-for="WebAppManifest">

0 commit comments

Comments
 (0)