[html5] r2715 - [gw] (2) Fire 'noupdate' for all browsing contexts, not just the new ones. (cred [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jan 27 17:32:52 PST 2009
Author: ianh
Date: 2009-01-27 17:32:51 -0800 (Tue, 27 Jan 2009)
New Revision: 2715
Modified:
index
source
Log:
[gw] (2) Fire 'noupdate' for all browsing contexts, not just the new ones. (credit: ap)
Modified: index
===================================================================
--- index 2009-01-28 01:29:17 UTC (rev 2714)
+++ index 2009-01-28 01:32:51 UTC (rev 2715)
@@ -37351,15 +37351,7 @@
<p>Otherwise, associate the <code>Document</code> for this entry
with <var title="">cache</var>; store the resource for this
entry in <var title="">cache</var>, if it isn't already there,
- and categorize its entry as a <a href=#concept-appcache-master title=concept-appcache-master>master entry</a>; and
- <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-noupdate>noupdate</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a> whose <a href=#active-document>active document</a> is the
- <code>Document</code> for this entry, if there still is one. The
- default action of this event should be the display of some sort
- of user interface indicating to the user that the application is
- up to date.</p>
+ and categorize its entry as a <a href=#concept-appcache-master title=concept-appcache-master>master entry</a>.</p>
<p class=note>HTTP caching rules, such as <code title="">Cache-Control: no-store</code>, are ignored for the
purposes of the <a href=#application-cache-update-process>application cache update
@@ -37367,6 +37359,15 @@
</li>
+ <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
+ document</a> is associated with an <a href=#application-cache>application
+ cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-noupdate>noupdate</code> at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
+ context</a>. The default action of these events should be the
+ display of some sort of user interface indicating to the user
+ that the application is up to date.</li>
+
<li><p>Empty <var title="">cache group</var>'s <a href=#concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
entries</a>.</li>
Modified: source
===================================================================
--- source 2009-01-28 01:29:17 UTC (rev 2714)
+++ source 2009-01-28 01:32:51 UTC (rev 2715)
@@ -42499,15 +42499,7 @@
with <var title="">cache</var>; store the resource for this
entry in <var title="">cache</var>, if it isn't already there,
and categorize its entry as a <span
- title="concept-appcache-master">master entry</span>; and
- <span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-noupdate">noupdate</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span> whose <span>active document</span> is the
- <code>Document</code> for this entry, if there still is one. The
- default action of this event should be the display of some sort
- of user interface indicating to the user that the application is
- up to date.</p>
+ title="concept-appcache-master">master entry</span>.</p>
<p class="note">HTTP caching rules, such as <code
title="">Cache-Control: no-store</code>, are ignored for the
@@ -42516,6 +42508,16 @@
</li>
+ <li><p>For each <span>browsing context</span> whose <span>active
+ document</span> is associated with an <span>application
+ cache</span> in <var title="">cache group</var>, <span>queue a
+ task</span> to <span>fire a simple event</span> called <code
+ title="event-noupdate">noupdate</code> at the
+ <code>ApplicationCache</code> singleton of the <span>browsing
+ context</span>. The default action of these events should be the
+ display of some sort of user interface indicating to the user
+ that the application is up to date.</p></li>
+
<li><p>Empty <var title="">cache group</var>'s <span
title="concept-appcache-pending-masters">list of pending master
entries</span>.</p></li>
More information about the Commit-Watchers
mailing list