Re: [w3c/manifest] Processing the manifest is no longer a function of document URL (#834)

@dominickng commented on this pull request.



> @@ -304,6 +304,10 @@ <h2>
             </li>
           </ul>
         </li>
+        <li>Otherwise, if |manifest|["{{WebAppManifest/start_url}}"] is not
+        present, or not <a>same origin</a> as the {{Document}}'s
+        {{Document/URL}}, consider the document not <a>installable</a>.

In Chromium we currently enforce that `start_url` and `scope` are same-origin with the document URL, which the spec requires. If that isn't met, we discard the values.

When this happens, Chromium browsers use the document URL in place of the manifest values when a site has a shortcut created for it. That's behaviour outside the scope of the manifest spec and a browser choice.

Since this PR removes that same-origin requirement, we would remove that enforcement in our parsing when updating to match this.

-- 
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/834#discussion_r448712202