Re: [w3c/manifest] Add id member to manifest (#988)

@marcoscaceres commented on this pull request.



> +          <p>
+            User agents SHOULD re-fetch and process the manifest on every page
+            load. When the processing is successful, user agents MAY apply updated
+            manifest to any current and future <a>application contexts</a>
+            associated with the application. When the user agent fetches a
+            manifest as part of an update check, it MUST [=url/equal|compare=] the fetched
+            processed manifest's [=manifest/identity=] with the identity of the
+            app being updated. If it is not equal, the user agent MUST NOT
+            update the installed application's manifest. 
+          </p>
+          <section>
+            <h3>
+              Privacy and security consideration
+            </h3>
+            <p>
+              User agents SHOULD be careful about performing update to manifest

I think we need to just fold this into the section above. We probably don't need to call it out.... in fact, I think an update is really just a "re-install", so we might be able to leverage what's already in the installation section. 

-- 
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/988#pullrequestreview-759301012