[html5] r2714 - [gw] (2) Avoid sending 'error' events twice to some documents. (credit: ap)
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jan 27 17:29:18 PST 2009
Author: ianh
Date: 2009-01-27 17:29:17 -0800 (Tue, 27 Jan 2009)
New Revision: 2714
Modified:
index
source
Log:
[gw] (2) Avoid sending 'error' events twice to some documents. (credit: ap)
Modified: index
===================================================================
--- index 2009-01-28 01:23:39 UTC (rev 2713)
+++ index 2009-01-28 01:29:17 UTC (rev 2714)
@@ -37711,18 +37711,8 @@
<dd>
- <ol><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-error><a href=#event-error>error</a></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 user agent failed to save the application for offline
- use.</li>
+ <ol><li>
- <li>
-
<p>For each entry in <var title="">cache group</var>'s <a href=#concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
entries</a>, run the following further substeps. These steps
may be run in parallel for two or more entries at a time.</p>
@@ -37744,6 +37734,16 @@
</ol></li>
+ <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
+ document</a> is still 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-error><a href=#event-error>error</a></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 user agent failed to save the application for offline
+ use.</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:23:39 UTC (rev 2713)
+++ source 2009-01-28 01:29:17 UTC (rev 2714)
@@ -42919,17 +42919,6 @@
<ol>
- <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-error">error</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 user agent failed to save the application for offline
- use.</p></li>
-
<li>
<p>For each entry in <var title="">cache group</var>'s <span
@@ -42958,6 +42947,17 @@
</li>
+ <li><p>For each <span>browsing context</span> whose <span>active
+ document</span> is still 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-error">error</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 user agent failed to save the application for offline
+ use.</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