- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 16 Oct 2008 10:53:30 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv5359
Modified Files:
Overview.html
Log Message:
Allow an obsolete appcache to be renewed. Move the manifest storing to later in the process to reduce more race conditions. Use 'obsolete' as the event name instead of 'error' when the cache is made obsolete. Support obsolete caches in the API. (whatwg r2347)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1519
retrieving revision 1.1520
diff -u -d -r1.1519 -r1.1520
--- Overview.html 16 Oct 2008 10:32:37 -0000 1.1519
+++ Overview.html 16 Oct 2008 10:53:27 -0000 1.1520
@@ -27320,14 +27320,11 @@
chronological order).<p>Each group of application caches for the same manifest URL has a
common <dfn id=concept-appcache-status title=concept-appcache-status>update status</dfn>,
which is one of the following: <i>idle</i>, <i>checking</i>,
- <i>downloading</i>. Initially, the <a href=#concept-appcache-status title=concept-appcache-status>update status</a> of a group of
- application caches is <i>idle</i>.<p>Each group of application caches for the same manifest URL also
+ <i>downloading</i>.<p>Each group of application caches for the same manifest URL also
has a common <dfn id=concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle
status</dfn>, which is one of the following: <i>new</i>,
- <i>mature</i>, <i>obsolete</i>. Initially, when the first applicaion
- cache in a group is created, its <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle status</a> is
- <i>new</i>. A <dfn id=relevant-application-cache>relevant application cache</dfn> is an
- <a href=#application-cache>application cache</a> whose <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle status</a> is
+ <i>mature</i>, <i>obsolete</i>. A <dfn id=relevant-application-cache>relevant application
+ cache</dfn> is an <a href=#application-cache>application cache</a> whose <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle status</a> is
<i>mature</i>.<p id=appcache-history-1>A <a href=#browsing-context>browsing context</a> is
associated with the application cache appropriate for its
<a href=#active-document>active document</a>, if any. A <code>Document</code>
@@ -27774,7 +27771,8 @@
specific cache), and there is no <a href=#application-cache>application cache</a>
identified by <var title="">manifest URL</var> whose <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle status</a> is not
<i>obsolete</i>, then create a new <a href=#application-cache>application cache</a>
- identified with that URL.</li>
+ identified with that URL and set the group's <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle status</a> to
+ <i>new</i>.</li>
<li id=flagAsCandidateForCache><p>If these steps were invoked
with a new <a href=#concept-appcache-master title=concept-appcache-master>master</a>
@@ -28039,10 +28037,6 @@
</ol></li>
- <li><p>Store <var title="">manifest</var> in <var title="">new
- cache</var>, if it's not there already, and categorize this entry
- (whether newly added or not) as <a href=#concept-appcache-manifest title=concept-appcache-manifest>the manifest</a>.</li>
-
<li><p>Store the list of <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespaces</a>,
and the URLs of the <a href=#concept-appcache-fallback title=concept-appcache-fallback>fallback entries</a> that they
map to, in <var title="">new cache</var>.</li>
@@ -28068,6 +28062,10 @@
</li>
+ <li><p>Store <var title="">manifest</var> in <var title="">new
+ cache</var>, if it's not there already, and categorize this entry
+ (whether newly added or not) as <a href=#concept-appcache-manifest title=concept-appcache-manifest>the manifest</a>.</li>
+
<li>
<p>If this is a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
@@ -28116,13 +28114,13 @@
attempt</a>, then discard <var title="">cache</var> and abort
the update process.</li>
- <li><p><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
+ <li><p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-obsolete>obsolete</code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of each <a href=#browsing-context>browsing
context</a> whose <a href=#active-document>active document</a> is associated
with a cache in <var title="">cache group</var>. The default action
of this event should be the display of some sort of user interface
indicating to the user that the application is no longer available
- for offline use.</li> <!-- XXX another event maybe? -->
+ for offline use.</li>
<li><p>Set the <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle
status</a> of <var title="">cache group</var> to
@@ -28342,6 +28340,7 @@
const unsigned short <a href=#dom-appcache-checking title=dom-appcache-CHECKING>CHECKING</a> = 2;
const unsigned short <a href=#dom-appcache-downloading title=dom-appcache-DOWNLOADING>DOWNLOADING</a> = 3;
const unsigned short <a href=#dom-appcache-updateready title=dom-appcache-UPDATEREADY>UPDATEREADY</a> = 4;
+ const unsigned short <a href=#dom-appcache-obsolete title=dom-appcache-OBSOLETE>OBSOLETE</a> = 5;
readonly attribute unsigned short <a href=#dom-appcache-status title=dom-appcache-status>status</a>;
// updates
@@ -28362,6 +28361,7 @@
attribute <span>EventListener</span> <a href=#handler-appcache-onprogress title=handler-appcache-onprogress>onprogress</a>;
attribute <span>EventListener</span> <a href=#handler-appcache-onupdateready title=handler-appcache-onupdateready>onupdateready</a>;
attribute <span>EventListener</span> <a href=#handler-appcache-oncached title=handler-appcache-oncached>oncached</a>;
+ attribute <span>EventListener</span> <a href=#handler-appcache-onobsolete title=handler-appcache-onobsolete>onobsolete</a>;
};</pre><p>Objects implementing the <code><a href=#applicationcache>ApplicationCache</a></code> interface
must also implement the <code>EventTarget</code> interface.<p>There is a one-to-one mapping from <code>Document</code> objects
@@ -28392,34 +28392,44 @@
<dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
an <a href=#application-cache>application cache</a> whose group is in the <i>idle</i>
- <span title=concept-appcache-states>update status</span>, and
- that application cache is the newest cache in its group that
- contains a resource categorized as a <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a>.</dd>
+ <a href=#concept-appcache-status title=concept-appcache-status>update status</a> and the
+ <i>mature</i> <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle
+ status</a> and that application cache is the newest cache in its
+ group.</dd>
<dt><dfn id=dom-appcache-checking title=dom-appcache-CHECKING><code>CHECKING</code></dfn>
(numeric value 2)</dt>
<dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
an <a href=#application-cache>application cache</a> whose group is in the
- <i>checking</i> <span title=concept-appcache-states>update
- status</span>.</dd>
+ <i>checking</i> <a href=#concept-appcache-status title=concept-appcache-status>update
+ status</a>.</dd>
<dt><dfn id=dom-appcache-downloading title=dom-appcache-DOWNLOADING><code>DOWNLOADING</code></dfn>
(numeric value 3)</dt>
<dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
an <a href=#application-cache>application cache</a> whose group is in the
- <i>downloading</i> <span title=concept-appcache-states>update
- status</span>.</dd>
+ <i>downloading</i> <a href=#concept-appcache-status title=concept-appcache-status>update
+ status</a>.</dd>
<dt><dfn id=dom-appcache-updateready title=dom-appcache-UPDATEREADY><code>UPDATEREADY</code></dfn>
(numeric value 4)</dt>
<dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
an <a href=#application-cache>application cache</a> whose group is in the <i>idle</i>
- <span title=concept-appcache-states>update status</span>, but
- that application cache is <em>not</em> the newest cache in its
- group that contains a resource categorized as a <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a>.</dd>
+ <a href=#concept-appcache-status title=concept-appcache-status>update status</a> and the
+ <i>mature</i> <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle
+ status</a> but that application cache is <em>not</em> the newest
+ cache in its group.</dd>
+
+ <dt><dfn id=dom-appcache-obsolete title=dom-appcache-OBSOLETE><code>OBSOLETE</code></dfn>
+ (numeric value 5)</dt>
+
+ <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
+ an <a href=#application-cache>application cache</a> whose group is in the
+ <i>obsolete</i> <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle
+ status</a>.</dd>
</dl><p>The <dfn id=dom-appcache-length title=dom-appcache-length><code>length</code></dfn>
attribute must return the number of <a href=#concept-appcache-dynamic title=concept-appcache-dynamic>dynamic entries</a> in the
@@ -28527,11 +28537,16 @@
associated. (By definition, this is the same as the one that was
found in the previous step.)</li>
- <li><p>Check that there is an application cache in the same group
- as <var title="">cache</var> which has an entry categorized as a
- <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a> that has is
- newer than <var title="">cache</var>. If there is not, then raise
- an <code>INVALID_STATE_ERR</code> exception and abort these
+ <li><p>If the group of <a href=#application-cache title="application cache">application
+ caches</a> to which <var title="">cache</var> belongs has the
+ <a href=#concept-appcache-lifecycle title=concept-appcache-lifecycle>lifecycle status</a>
+ <i>obsolete</i>, unassociate <var title="">document</var> from <var title="">cache</var> and abort these steps.</li>
+
+ <li><p>Otherwise, check that there is an application cache in the
+ same group as <var title="">cache</var> which has an entry
+ categorized as a <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a> that is newer
+ than <var title="">cache</var>. If there is not, then raise an
+ <code>INVALID_STATE_ERR</code> exception and abort these
steps.</li>
<li><p>Let <var title="">new cache</var> be the newest
@@ -28584,6 +28599,12 @@
<dd><p>Must be invoked whenever a <code title=event-cached>cached</code> event is targeted at or bubbles
through the <code><a href=#applicationcache>ApplicationCache</a></code> object.</dd>
+
+ <dt><dfn id=handler-appcache-onobsolete title=handler-appcache-onobsolete><code>onobsolete</code></dfn></dt>
+
+ <dd><p>Must be invoked whenever an <code title=event-obsolete>obsolete</code> event is targeted at or bubbles
+ through the <code><a href=#applicationcache>ApplicationCache</a></code> object.</dd>
+
</dl><h4 id=browser-state><span class=secno>5.7.7 </span>Browser state</h4><p>The <dfn id=dom-navigator-online title=dom-navigator-onLine><code>navigator.onLine</code></dfn>
attribute must return false if the user agent will not contact the
network when the user follows links or when a script requests a
Received on Thursday, 16 October 2008 10:53:39 UTC