[gw] (2) Avoid sending 'error' events twice to some documents. (credi…

…t: ap) git-svn-id: http://svn.whatwg.org/webapps@2714 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jan 28, 2009 · 15a56e6 · 15a56e6
1 parent 59208c1
commit 15a56e6
Show file tree

Hide file tree

Showing 2 changed files with 22 additions and 22 deletions.
diff --git a/index b/index
@@ -37711,17 +37711,7 @@ style/default.css</pre>
 
    <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>
-
-     <li>
+    <ol><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
@@ -37744,6 +37734,16 @@ style/default.css</pre>
 
       </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>
 

diff --git a/source b/source
@@ -42919,17 +42919,6 @@ style/default.css</pre>
 
     <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 @@ style/default.css</pre>
 
      </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>