Re: [w3c/manifest] Clarify the definition of "navigation scope", "applied", and off-scope theming (#880)

@mgiuca commented on this pull request.



> @@ -439,10 +439,9 @@ <h2>
       </h2>
       <p data-link-for="WebAppManifest">
         A <dfn data-export="">navigation scope</dfn> is a <a>URL</a> that
-        represents the set of URLs to which an <a>application context</a> can
-        be navigated while the manifest is <a>applied</a>. The <a>navigation
-        scope</a> of a manifest <var>manifest</var> is
-        <var>manifest</var>["<a>scope</a>"].
+        represents the set of URLs which are considered to be part of an

We just discussed this in our F2F. Agreed that the manifest _is_ applied to the out-of-scope page, based on testing Chrome, Firefox and Safari (the last of those we're not 100% sure but we suspect that's happening).

There isn't any normative text that says this, but it's implied by the fact that we do not make changes to the HTML navigation system, therefore navigation is expected to proceed as normal to an out-of-scope URL.

There is non-normative text that supports this:

> Unlike previous versions of this specification, user agents are no longer required or allowed to block off-scope navigations, or open them in a new top-level browsing context. This practice broke some sites that navigate to an off-scope URL (e.g., to perform third-party authentication). See Issue 646.

I proposed that since it's been 2 years, we collapse this text to not mention the history of it, just say that user agents are not allowed to block or transfer the navigation to another TLBC.

@marcoscaceres let me know if I misunderstood something.

-- 
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/880#discussion_r433091252