[html5] r2716 - [gw] (2) Simplify the cache failure steps.
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jan 27 17:38:17 PST 2009
Author: ianh
Date: 2009-01-27 17:38:16 -0800 (Tue, 27 Jan 2009)
New Revision: 2716
Modified:
index
source
Log:
[gw] (2) Simplify the cache failure steps.
Modified: index
===================================================================
--- index 2009-01-28 01:32:51 UTC (rev 2715)
+++ index 2009-01-28 01:38:16 UTC (rev 2716)
@@ -37680,89 +37680,59 @@
</ol><p>The <dfn id=cache-failure-steps>cache failure steps</dfn> are as follows:</p>
- <dl class=switch><dt>If this was a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
- attempt</a></dt>
+ <ol><li>
- <dd>
+ <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>
- <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>, <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
+ <ol><li><p>Wait for the resource for this entry to have completely
+ downloaded.</p>
+
+ <li><p>Unassociate the <code>Document</code> for this entry from
+ its <a href=#application-cache>application cache</a>, if it has one.</li>
+
+ <li><p><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> 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
- user agent failed to save the application for offline
- use.</li>
+ <code>Document</code> for this entry, if there still is one. 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><p>If appropriate, remove any user interface indicating
- that an update for this cache is in progress.</li>
+ </ol></li>
- <li><p>Discard <var title="">cache group</var> (and its
- <a href=#application-cache>application cache</a>, if any).</p>
+ <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>Abort the update process.</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>
- </ol></dd>
+ <li><p>If <var title="">cache group</var> has an <a href=#application-cache>application
+ cache</a> whose <a href=#concept-appcache-completeness title=concept-appcache-completeness>completeness flag</a> is
+ <i>incomplete</i>, then discard that <a href=#application-cache>application
+ cache</a>.</p>
- <dt>If this was an <a href=#concept-appcache-upgrade title=concept-appcache-upgrade>upgrade
- attempt</a></dt>
+ <li><p>If appropriate, remove any user interface indicating that an
+ update for this cache is in progress.</li>
- <dd>
+ <li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
- <ol><li>
+ <li><p>If this was a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
+ attempt</a>, discard <var title="">cache group</var>
+ altogether.</p>
- <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>
+ <li><p>Abort the update process.</li>
- <ol><li><p>Wait for the resource for this entry to have completely
- downloaded.</p>
-
- <li><p>Unassociate the <code>Document</code> for this entry
- from its <a href=#application-cache>application cache</a>.</li>
-
- <li><p><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> 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 user agent
- failed to save the application for offline use.</p>
-
- </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>
-
- <li><p>If <var title="">cache group</var> has an
- <a href=#application-cache>application cache</a> whose <a href=#concept-appcache-completeness title=concept-appcache-completeness>completeness flag</a> is
- <i>incomplete</i>, then discard that <a href=#application-cache>application
- cache</a>.</p>
-
- <li><p>If appropriate, remove any user interface indicating that
- an update for this cache is in progress.</li>
-
- <li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
-
- <li><p>Abort the update process.</li>
-
- </ol></dd>
-
- </dl><p>Attempts to <a href=#fetch>fetch</a> resources as part of the
+ </ol><p>Attempts to <a href=#fetch>fetch</a> resources as part of the
<a href=#application-cache-update-process>application cache update process</a> may be done with
cache-defeating semantics, to avoid problems with stale or
inconsistent intermediary caches.</p>
Modified: source
===================================================================
--- source 2009-01-28 01:32:51 UTC (rev 2715)
+++ source 2009-01-28 01:38:16 UTC (rev 2716)
@@ -42880,111 +42880,72 @@
<p>The <dfn>cache failure steps</dfn> are as follows:</p>
- <dl class="switch">
+ <ol>
- <dt>If this was a <span title="concept-appcache-cache">cache
- attempt</span></dt>
+ <li>
- <dd>
+ <p>For each entry in <var title="">cache group</var>'s <span
+ title="concept-appcache-pending-masters">list of pending master
+ entries</span>, run the following further substeps. These steps
+ may be run in parallel for two or more entries at a time.</p>
<ol>
- <li><p>For each entry in <var title="">cache group</var>'s
- <span title="concept-appcache-pending-masters">list of pending
- master entries</span>, <span>queue a task</span> to <span>fire
- a simple event</span> called <code
- title="event-error">error</code> at the
+ <li><p>Wait for the resource for this entry to have completely
+ downloaded.</p>
+
+ <li><p>Unassociate the <code>Document</code> for this entry from
+ its <span>application cache</span>, if it has one.</p></li>
+
+ <li><p><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> 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
- user agent failed to save the application for offline
- use.</p></li>
+ <code>Document</code> for this entry, if there still is one. 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><p>If appropriate, remove any user interface indicating
- that an update for this cache is in progress.</p></li>
-
- <li><p>Discard <var title="">cache group</var> (and its
- <span>application cache</span>, if any).</p>
-
- <li><p>Abort the update process.</p></li>
-
</ol>
- </dd>
+ </li>
- <dt>If this was an <span title="concept-appcache-upgrade">upgrade
- attempt</span></dt>
+ <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>
- <dd>
+ <li><p>Empty <var title="">cache group</var>'s <span
+ title="concept-appcache-pending-masters">list of pending master
+ entries</span>.</p></li>
- <ol>
+ <li><p>If <var title="">cache group</var> has an <span>application
+ cache</span> whose <span
+ title="concept-appcache-completeness">completeness flag</span> is
+ <i>incomplete</i>, then discard that <span>application
+ cache</span>.</p>
- <li>
+ <li><p>If appropriate, remove any user interface indicating that an
+ update for this cache is in progress.</p></li>
- <p>For each entry in <var title="">cache group</var>'s <span
- title="concept-appcache-pending-masters">list of pending master
- entries</span>, run the following further substeps. These steps
- may be run in parallel for two or more entries at a time.</p>
+ <li><p>Let the <span
+ title="concept-appcache-status">status</span> of <var
+ title="">cache group</var> be <i>idle</i>.</p></li>
- <ol>
+ <li><p>If this was a <span title="concept-appcache-cache">cache
+ attempt</span>, discard <var title="">cache group</var>
+ altogether.</p>
- <li><p>Wait for the resource for this entry to have completely
- downloaded.</p>
+ <li><p>Abort the update process.</p></li>
- <li><p>Unassociate the <code>Document</code> for this entry
- from its <span>application cache</span>.</p></li>
+ </ol>
- <li><p><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> 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 user agent
- failed to save the application for offline use.</p>
-
- </ol>
-
- </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>
-
- <li><p>If <var title="">cache group</var> has an
- <span>application cache</span> whose <span
- title="concept-appcache-completeness">completeness flag</span> is
- <i>incomplete</i>, then discard that <span>application
- cache</span>.</p>
-
- <li><p>If appropriate, remove any user interface indicating that
- an update for this cache is in progress.</p></li>
-
- <li><p>Let the <span
- title="concept-appcache-status">status</span> of <var
- title="">cache group</var> be <i>idle</i>.</p></li>
-
- <li><p>Abort the update process.</p></li>
-
- </ol>
-
- </dd>
-
- </dl>
-
<p>Attempts to <span>fetch</span> resources as part of the
<span>application cache update process</span> may be done with
cache-defeating semantics, to avoid problems with stale or
More information about the Commit-Watchers
mailing list