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

(FYI I'm leaving this on hold until #882 lands, which will change the definition of "navigation scope", though it keeps the clause in question.)

> I'm confused why "that can now be true for all URLs"?

The current definition defines navigation scope as "the set of URLs to which an application context can be navigated while the manifest is applied." As of #701 (which landed nearly two years ago), the set of URLs to which an application context can be navigated while the manifest is applied is all URLs. If I navigate an app window on https://mysite.com to https://yoursite.com, the manifest is still _applied_.

So we can't have this definition, if the intention is to allow the manifest to be applied when you navigate out of scope. (This isn't directly contradicted by normative text, but the absence of any text that forbids out-of-scope navigation implies that you can navigate out of scope in an application context where the manifest is applied. A non-normative note directly contradicts this definition: "Nothing prevents an application context from navigating to a URL that is outside of the application's navigation scope , while still having the manifest applied to it.")

> Although the above is true (it's a URL indeed), that doesn't really define the role of the navigation scope as it relates to applying the manifest. That needs to be either here, or somewhere that says roughly "when you navigate, keep applying the manifest until you are no longer within the navigation scope".

Wait: "until you are no longer within the navigation scope" implies that you would not apply the manifest when navigated off-scope. Do we have a disagreement over the meaning of the term "apply"? I am considering a manifest to be applied permanently to the application context, regardless of whether it's navigated off-scope. When you navigate off-scope, it is RECOMMENDED that the application window shows some UI indicating that you are off scope, but the manifest is still applied. We would still show the theme colour, title and icon of the application from the manifest. So the spec needs to state that the manifest is always applied to both in-scope and off-scope documents.

I think we can add some text to "applying the manifest" that says "When a manifest is applied to a top-level browsing context, it is continually applied throughout the lifetime of the browsing context."

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