Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe manifest update behavior #1011

Merged
merged 15 commits into from
Feb 17, 2022
19 changes: 19 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1222,6 +1222,25 @@ <h3>
Updating the manifest
</h3>
<aside class="issue" data-number="446"></aside>
philloooo marked this conversation as resolved.
Show resolved Hide resolved
<p>
The manifest is fetched and processed on every page load. When the
philloooo marked this conversation as resolved.
Show resolved Hide resolved
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>
philloooo marked this conversation as resolved.
Show resolved Hide resolved
<p>
When the user agent fetches a manifest as part of an update check,
philloooo marked this conversation as resolved.
Show resolved Hide resolved
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>
</section>
</section>
Expand Down