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

> It seems a very different UX from re-install as it's performed without user action.

On second thought, I'm unsure if all UAs will do this without user action (although, implemented in multiple OSs... like Chrome OS and Windows). I feel like this might still be an area where we might see some variation on how different implementations handle this. 

In any case, I think the text you've proposed covers the privacy/security aspects that are of most concern with respect to upgrades. 


-- 
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#discussion_r714417810