Re: [w3c/manifest] [Breaking] "scope" member now defaults to parent of "start_url" (#647)

mgiuca commented on this pull request.



>        </p>
+      <div class="note" data-link-for="WebAppManifest">
+        <p>
+          If the <a>scope</a> member is not present in the manifest, it
+          defaults to the parent path of the <a>start_url</a> member. For
+          example, if <a>start_url</a> is <code>/pages/welcome.html</code>, and
+          <a>scope</a> is missing, the navigation scope will be
+          <code>/pages/</code> on the same origin. If <a>start_url</a> is
+          <code>/pages/</code> (the trailing slash is important!), the
+          navigation scope will be <code>/pages/</code>.
+        </p>
+        <p>
+          Developers should take care, if they rely on the default behaviour,
+          that all of the application's page URLs begin with the parent path of

Is this still needed, given the above? Technically, I do, because if you click on "scope" in that sentence, it links to the parent path algorithm defined in [scope member](https://pr-preview.s3.amazonaws.com/mgiuca/manifest/pull/647.html#scope-member).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/647#discussion_r165221085