Re: [w3c/manifest] chore: refactor and export scope terms (#882)

@marcoscaceres commented on this pull request.



> @@ -522,13 +521,13 @@ <h2>
       </div>
       <p>
         If the <a>application context</a>'s <a>active document</a>'s
-        [=Document/URL=] is not <a data-lt="within-scope-manifest">within
-        scope</a> of the <a>application context</a>'s manifest, the user agent
-        SHOULD show a prominent UI element indicating the [=Document/URL=] or
-        at least its <a>origin</a>, including whether it is served over a
-        secure connection. This UI SHOULD differ from any UI used when the
-        [=Document/URL=] is <a>within scope</a>, in order to make it obvious
-        that the user is navigating off scope.
+        [=Document/URL=] is not [=within manifest scope=] of the <a>application

Happy to change them to simpler ones... um... how about:

```
[=manifest/within scope of=]
[=URL/within scope of=]
```

Then it takes the complexity out of reading the sentences, but puts the problem on the spec editor... they just get displayed as "within scope of" and links to the right thing. 

-- 
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/882#discussion_r432287059