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

> URLs outside the scope can still be part of the web application (e.g., an about.html page that opens in an overlay window), it's just that the manifest members are no longer in effect there.

But the manifest members _are_ in effect there. That's exactly why I'm making this change. When you're off-scope, all of the manifest members are still affecting the application context, because we want it to still feel like you're in the app.

Are you disagreeing with the _behaviour_ allowed by this change, or just the wording? i.e., do you think Chrome should not render about.html page in an overlay window with the full theming of the app manifest behind it (the theme colour, app name, icon, display mode, etc)? Or do you just disagree on the semantics?

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