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

I feel this waters down the definition somewhat...  the practical intent is for the manifest members to affect the web application while it's in scope - 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. 

This is also reiterated nicely below... 

Can we keep the original definition? 

> @@ -1157,10 +1156,22 @@ <h3 id="applying">
           Applying the manifest
         </h3>
         <p>
-          A <a>manifest</a> is <dfn data-lt="apply|applying">applied</dfn> to a
-          <a>top-level browsing context</a>, meaning that the members of the
-          <a>manifest</a> are affecting the presentation or behavior of a
-          browsing context.
+          A <a>manifest</a> can be <dfn data-lt="apply|applying">applied</dfn>
+          to a <a>top-level browsing context</a>, meaning that the members of
+          the <a>manifest</a> are affecting the presentation or behavior of a
+          browsing context. Whenever a <a>top-level browsing context</a> is
+          created, the user agent MAY <a>apply</a> a manifest to it, before

```suggestion
          created, the user agent MAY <a>apply</a> a manifest to it before
```

> +          A <a>manifest</a> can be <dfn data-lt="apply|applying">applied</dfn>
+          to a <a>top-level browsing context</a>, meaning that the members of
+          the <a>manifest</a> are affecting the presentation or behavior of a
+          browsing context. Whenever a <a>top-level browsing context</a> is
+          created, the user agent MAY <a>apply</a> a manifest to it, before
+          [=navigate|navigation=] begins.
+        </p>
+        <p class="note">
+          Whether to [=apply=] a manifest, and which manifest to apply, is at
+          the discretion of the user agent, based on the user's actions. For
+          example, if the user launched an application from the system menu or
+          from a [=launching a shortcut|shortcut=], the user agent might create
+          a new [=top-level browsing context=] with that application's
+          [=manifest=] [=applied=], but it might not do so if the user simply
+          clicked a bookmark to a URL within the application's [=navigation
+          scope=].

... or could even apply a user configured one... 

-- 
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#pullrequestreview-420670092