Re: [w3c/manifest] Describe manifest update behavior (#1011)

@NotWoods commented on this pull request.



> +            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
+              fields like app name and icons. Users should be fully aware if
+              such fields are to be be updated to avoid web applications being
+              installed and silently changed to appear as a different one.
+            </p>

Missing `</section>` tag, which is causing later items to get different section numbers in the table of contents.

-- 
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/1011#pullrequestreview-768144037