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

@marcoscaceres 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

> OK maybe we can workshop this. I don't want to return to the old definition, since it directly ties the scope to the set of URLs that the manifest "applies" to, where "applies" has a strict technical definition of having all of its members used by the top-level browsing context (and that can now be true for all URLs).

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

> So 2 and 3 are taken care of elsewhere. All that this definitional sentence really needs to do is say "it's a URL".

> "A navigation scope is a URL.

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


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