Re: [w3c/manifest] Editorial: add better example of scope (#958)

@benfrancis commented on this pull request.



> +            anything at the root "/" would be "out of scope" and the manifest
+            wouldn't apply to documents in those paths. Only one scope path is
+            supported. See [[[#nav-scope]]] for the technical details.
+          </p>
+          <p>
+            [=Applying=] a manifest means that any members that affect
+            presentation found in the manifest will come into effect, such as
+            display "fullscreen", or applying a particular screen orientation.
+            As long as the application is navigated to URLs that are
+            [=URL/within scope=], the browser will continue to apply the
+            manifest. However, navigating the web applications "out of scope"
+            will cause the manifest to no longer be applied, and the browser
+            will apply its own defaults. This will cause, for example, the
+            application to no longer be displayed in fullscreen, and instead be
+            displayed as a regular web page in a browser tab. It's left up to
+            implementers to decide how the deal with web pages being navigated

"the" -> "to"/"they"

-- 
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/958#pullrequestreview-604216475

Received on Thursday, 4 March 2021 15:21:25 UTC