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.

Sign up for GitHub

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

Fix(updates): remove text about updates (closes #384) #457

Merged
merged 1 commit into from
Apr 26, 2016
+2 −27
Merged

Fix(updates): remove text about updates (closes #384) #457

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 2 additions & 27 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -911,8 +911,7 @@ <h2>
<p>
This section defines algorithms for <a href="#obtaining">obtaining</a>,
<a href="#processing">processing</a>, and <a>applying</a> a
<a>manifest</a>, and gives recommendations to implementers on how to
react when the manifest is <a href="#updating">updated</a>.
<a>manifest</a>.
</p>
<section id="obtaining">
<h3>
Expand Down Expand Up @@ -1201,31 +1200,7 @@ <h3 id="applying">
<h3>
Updating the manifest
</h3>
<div class="issue" data-number="384"></div>
<p>
By using the <a>manifest URL</a>, a user agent MAY periodically check
if the contents of a manifest has been modified (e.g., by honoring
HTTP cache directives associated with the manifest or by checking for
updates after the web application has been launched). In the event
that the members of the manifest have been updated, as determined by
running the <a>steps for processing a manifest</a> and seeing if
anything has changed, the user agent MAY update the metadata
corresponding to the web application (e.g., by replacing the name,
icons, <a>navigation scope</a>, or whatever other data has been
changed).
</p>
<p>
In addition, even if the manifest has not been modified, the user
agents MAY periodically check if resources referenced from a manifest
(e.g., the icons) have been modified by honoring HTTP cache
directives. If any resources have been modified, the user agent MAY
replace any stale resources.
</p>
<p>
To avoid one application masquerading as another, it is RECOMMENDED
that users be made aware of any such updates using implementation or
platform specific conventions.
</p>
<div class="issue" data-number="446"></div>
</section>
</section>
<section>
Expand Down