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>.

I agree with @annevk but I was trying to be consistent with the writing in the rest of this document (in fact on the very next line: "Let scope URL be a new URL using value as input and manifest URL as the base URL."). There are six existing instances of this "new URL using X as input" in the Manifest spec.

I'll do a pass over it afterwards and fix up the invocations of URL parsing, but I think it's more urgent to land this to keep implementation divergence from getting out of control.

-- 
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_r165548524