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

@marcoscaceres requested changes on this pull request.

@philloooo, happy to work on this together... I can take the HTML spec updates if you'd like. 

> @@ -1222,6 +1222,25 @@ <h3>
             Updating the manifest
           </h3>
           <aside class="issue" data-number="446"></aside>

```suggestion
```

> @@ -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 think we should  move this section to the "processing a manifest" section as part of the algorithm: i.e. something like: 
 
1. If the document "processed manifest" is not null, and document [=processed manifest=]'s id member [=URL/equals=] manifest's id member, return. 

(i.e., prevent overriding an existing "processed manifest").


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

I think we need to update the HTML spec to say this instead. I.e., it should say that, for regular web applications, the manifest is loaded when needed, but for "installed" web applications, the manifest is fetched on page load. 

Then here we can just say point to the HTML spec. 


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