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

@marcoscaceres commented on this pull request.



> @@ -1222,6 +1222,25 @@ <h3>
             Updating the manifest
           </h3>
           <aside class="issue" data-number="446"></aside>
+          <p>
+            The manifest is fetched and processed 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. 
+          </p>
+          <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>
+          <p>
+            When the user agent fetches a manifest as part of an update check,

I just realized that [=URL/equals=] allows us to "exclude fragments" as an argument, which might mean we can keep the fragment in the `id`, but ignore it for these comparisons. That might simplify `id` a little bit, because we don't need to chop the fragments anymore. 

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