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

@philloooo 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. I agree the above section is very hand-wavy, and the privacy/security section warns about what NOT to do (update identity related information without user consent). And leave the rest to individual implementation. How should I describe this better? Or I just move this as the next paragraph to:
```
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 application contexts associated with the application.
```
?

-- 
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_r713436707