[w3c/manifest] Require document to be in scope to be styled by the manifest (#791)

This change (choose one):

* [ ] Breaks existing normative behavior (please add label "breaking")
* [X] Adds new normative requirements
* [ ] Adds new normative recommendations or optional items
* [ ] Makes only editorial changes (only changes informative sections, or
  changes normative sections without changing behavior)
* [ ] Is a "chore" (metadata, formatting, fixing warnings, etc).

Implementation commitment (delete if not making normative changes):

* [ ] Safari (link to issue)
* [ ] Chrome (link to issue)
* [ ] Firefox (link to issue)
* [ ] Edge (public signal)

Commit message:

Require document to be in scope to be styled by the manifest.

This introduces a small new normative requirement that the manifest NOT be
applied to a document that it outside of its scope. A note explains that this
only applies to the authority of the metadata, not the installation.

Adds a non-normative note that the app can be installed from a document that is
outside the scope of that app.

Closes #784.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/manifest/pull/791

-- Commit Summary --

  * Rewrote install prompts and installation process.
  * Fix usage of in parallel.
  * Clarify that install prompt may only be shown if the document is installable.
  * Clarify that the user agent doesn't *have* to make the document installable.
  * Authority of the manifest's metadata: require the document to be in scope.
  * Add a non-normative note that the app can be installed from a document that is outside the scope of that app.

-- File Changes --

    M index.html (273)

-- Patch Links --

https://github.com/w3c/manifest/pull/791.patch
https://github.com/w3c/manifest/pull/791.diff

-- 
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/791