From 944d443065ac5192051987e78e539a25c10a9db8 Mon Sep 17 00:00:00 2001
From: Matt Giuca <mgiuca@chromium.org>
Date: Thu, 12 Sep 2019 14:53:03 +1000
Subject: [PATCH] Add a non-normative note that the app can be installed from a
 document that is outside the scope of that app.

Closes #784.
---
 index.html | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 1541e9d5c..ba4447ca7 100644
--- a/index.html
+++ b/index.html
@@ -318,6 +318,25 @@ <h2 id="installable-web-applications">
           Installability signals</a>).
         </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 should 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 <a href=
+          "#navigation-scope">Navigation scope</a>). 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
@@ -842,7 +861,7 @@ <h4>
       </section>
     </section>
     <section>
-      <h2>
+      <h2 id="navigation-scope">
         Navigation scope
       </h2>
       <p data-link-for="WebAppManifest">