[html5] r1050 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2007-10-11 16:32:14 -0700 (Thu, 11 Oct 2007)
New Revision: 1050

Modified:
   index
   source
Log:
[] (0) split the concept of 'update ready' from the concept of the cache group being idle/checking/downloading.

Modified: index
===================================================================
--- index	2007-10-11 22:53:55 UTC (rev 1049)
+++ index	2007-10-11 23:32:14 UTC (rev 1050)
@@ -25888,12 +25888,13 @@
    manifest which is used to populate the cache.
 
   <p>Application caches are versioned, and there can be different instances
-   of caches for the same manifest URI, each having a different version.
+   of caches for the same manifest URI, each having a different version. A
+   cache is newer than another if it was created after the other (in other
+   words, caches in a group have a chronological order).
 
   <p>Each group of application caches for the same manifest URI have a common
    <dfn id=update0 title=concept-appcache-status>update status</dfn>, which
-   is one of the following: <i>idle</i>, <i>checking</i>, <i>downloading</i>,
-   <i>update ready</i>.
+   is one of the following: <i>idle</i>, <i>checking</i>, <i>downloading</i>.
 
   <p id="#appcache-history-1">A <a href="#browsing0">browsing context</a> can
    be associated with an application cache. A <a href="#child">child browsing
@@ -26661,7 +26662,7 @@
      title=concept-appcache-upgrade>upgrade attempt</a>:</p>
 
     <p>Set the <a href="#update0" title=concept-appcache-status>status</a> of
-     <var title="">cache group</var> to <i>update ready</i>.</p>
+     <var title="">cache group</var> to <i>idle</i>.</p>
 
     <p><a href="#firing2">Fire a simple event</a> called <code
      title=event-updateready>updateready</code> at the <code><a
@@ -26973,7 +26974,10 @@
     <p>The <code><a href="#applicationcache">ApplicationCache</a></code>
      object is associated with an <a href="#application0">application
      cache</a> whose group is in the <i>idle</i> <span
-     title=concept-appcache-states>update status</span>.
+     title=concept-appcache-states>update status</span>, and that application
+     cache is the newest cache in its group that contains a resource
+     categorised as a <a href="#the-manifest"
+     title=concept-appcache-manifest>manifest</a>.
 
    <dt><dfn id=checking
     title=dom-appcache-CHECKING><code>CHECKING</code></dfn> (numeric value 2)
@@ -27001,8 +27005,11 @@
    <dd>
     <p>The <code><a href="#applicationcache">ApplicationCache</a></code>
      object is associated with an <a href="#application0">application
-     cache</a> whose group is in the <i>update ready</i> <span
-     title=concept-appcache-states>update status</span>.
+     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 categorised as a <a href="#the-manifest"
+     title=concept-appcache-manifest>manifest</a>.
   </dl>
 
   <p>The <dfn id=length6 title=dom-appcache-length><code>length</code></dfn>

Modified: source
===================================================================
--- source	2007-10-11 22:53:55 UTC (rev 1049)
+++ source	2007-10-11 23:32:14 UTC (rev 1050)
@@ -23499,12 +23499,14 @@
 
   <p>Application caches are versioned, and there can be different
   instances of caches for the same manifest URI, each having a
-  different version.</p>
+  different version. A cache is newer than another if it was created
+  after the other (in other words, caches in a group have a
+  chronological order).</p>
 
   <p>Each group of application caches for the same manifest URI have a
   common <dfn title="concept-appcache-status">update status</dfn>,
   which is one of the following: <i>idle</i>, <i>checking</i>,
-  <i>downloading</i>, <i>update ready</i>.</p>
+  <i>downloading</i>.</p>
 
   <p id="#appcache-history-1">A <span>browsing context</span> can be
   associated with an application cache. A <span>child browsing
@@ -24304,8 +24306,8 @@
     <p>Otherwise, this is an <span
     title="concept-appcache-upgrade">upgrade attempt</span>:</p>
 
-    <p>Set the <span title="concept-appcache-status">status</span> of <var title="">cache group</var> to <i>update
-    ready</i>.</p>
+    <p>Set the <span title="concept-appcache-status">status</span> of
+    <var title="">cache group</var> to <i>idle</i>.</p>
 
     <p><span>Fire a simple event</span> called <code
     title="event-updateready">updateready</code> at the
@@ -24634,8 +24636,10 @@
 
    <dd><p>The <code>ApplicationCache</code> object is associated with
    an <span>application cache</span> whose group is in the <i>idle</i>
-   <span title="concept-appcache-states">update
-   status</span>.</p></dd>
+   <span title="concept-appcache-states">update status</span>, and
+   that application cache is the newest cache in its group that
+   contains a resource categorised as a <span
+   title="concept-appcache-manifest">manifest</span>.</p></dd>
 
    <dt><dfn title="dom-appcache-CHECKING"><code>CHECKING</code></dfn>
    (numeric value 2)</dt>
@@ -24657,9 +24661,11 @@
    (numeric value 4)</dt>
 
    <dd><p>The <code>ApplicationCache</code> object is associated with
-   an <span>application cache</span> whose group is in the <i>update
-   ready</i> <span title="concept-appcache-states">update
-   status</span>.</p></dd>
+   an <span>application cache</span> 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 categorised as a <span
+   title="concept-appcache-manifest">manifest</span>.</p></dd>
 
   </dl>