W3C home > Mailing lists > Public > public-html-diffs@w3.org > January 2009

spec/Overview.html 1.1863 2693 Make it possible for appcaches to become

From: poot <cvsmail@w3.org>
Date: Fri, 23 Jan 2009 09:12:23 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090123001223.A4D4C2BC0F@toro.w3.mag.keio.ac.jp>

Make it possible for appcaches to become obsolete. (whatwg r2693)

list of pending master entries
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#concept-appcache-pending-masters
IDLE
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#dom-appcache-idle
UPDATEREADY
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#dom-appcache-updateready
Status of this document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#status-of-this-document
5.7.7 Application cache API
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#application-cache-api
A vocabulary and associated APIs for HTML and XHTML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#a-vocabulary-and-associated-apis-for-html-and-xhtml
update()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#dom-appcache-update
OBSOLETE
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#dom-appcache-obsolete
cache attempt
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#concept-appcache-cache
CHECKING
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#dom-appcache-checking
swapCache()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#dom-appcache-swapcache
Editor's Draft 23 January 2009
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#editor-s-draft-date-zzz-9-june-2008
obsolete
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1863.html#concept-appcache-obsolete

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1862&r2=1.1863&f=h
http://html5.org/tools/web-apps-tracker?from=2692&to=2693

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1862
retrieving revision 1.1863
diff -u -d -r1.1862 -r1.1863
--- Overview.html	22 Jan 2009 12:27:33 -0000	1.1862
+++ Overview.html	23 Jan 2009 00:09:13 -0000	1.1863
@@ -8,7 +8,7 @@
    <p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
    <h1>HTML 5</h1>
    <h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->22 January 2009</h2>
+   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->23 January 2009</h2>
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2009/WD-html5-20090610/">http://www.w3.org/TR/2009/WD-html5-20090610/</a></dd>
@@ -97,7 +97,7 @@
   specification's progress along the W3C Recommendation
   track.
   <!--ZZZ:-->
-  This specification is the 22 January 2009 <!--ZZZ "Working Draft"-->Editor's Draft.
+  This specification is the 23 January 2009 <!--ZZZ "Working Draft"-->Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -29740,7 +29740,9 @@
   <i>complete</i>.<p>Each <a href=#application-cache-group>application cache group</a> has a <dfn id=concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
   entries</dfn>. Each entry in this list consists of a resource and a
   corresponding <code>Document</code> object. It is used during the
-  update process to ensure that new master entries are cached.</p><hr><p>A <code>Document</code> initially is not associated with an
+  update process to ensure that new master entries are cached.<p>An <a href=#application-cache-group>application cache group</a> can be marked as <dfn id=concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</dfn>, meaning that it
+  must be ignored when looking at what <a href=#application-cache-group title="application cache
+  group">application cache groups</a> exist.</p><hr><p>A <code>Document</code> initially is not associated with an
   <a href=#application-cache>application cache</a>, but steps <a href=#parser-appcache>in the parser</a> and in the <a href=#navigate title=navigate>navigation</a> sections cause <a href=#concept-appcache-init title=concept-appcache-init>cache selection</a> to occur early
   in the page load process.<p>Multiple <a href=#application-cache title="application cache">application
   caches</a> in different <a href=#application-cache-group title="application cache
@@ -30222,7 +30224,11 @@
     response <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or
     equivalent</a>, then run these substeps:</p>
 
-    <ol><!-- XXX can they be merged with the cache failure steps? (event name is different, this always disassociates even for upgrades, anything else?) --><li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
+    <ol><li><p>Mark <var title="">cache group</var> as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>. This <var title="">cache group</var> no longer exists for any purpose other
+     than the processing of <code>Document</code> objects already
+     associated with an <a href=#application-cache>application cache</a> in the <var title="">cache group</var>.</li>
+
+     <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-obsolete>obsolete</code> at the
@@ -30232,16 +30238,26 @@
      that the application is no longer available for offline
      use.</li>
 
-     <li><p>Unassociate any <code>Document</code> associated with an
-     <a href=#application-cache>application cache</a> in <var title="">cache
-     group</var>.</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>, <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> (not
+     <code title=event-obsolete>obsolete</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>
 
-     <li><p>If appropriate, remove any user interface indicating
-     that an update for this cache is in progress.</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>Discard <var title="">cache group</var> and its associated
-     <a href=#application-cache title="application cache">application caches</a>, if
-     any.</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>
 
@@ -30862,6 +30878,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
@@ -30905,9 +30922,10 @@
    <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
    an <a href=#application-cache>application cache</a> whose <a href=#application-cache-group>application cache
    group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update
-   status</a> is <i>idle</i>, and that application cache is the
-   <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> cache in its
-   group.</dd>
+   status</a> is <i>idle</i>, and that <a href=#application-cache>application
+   cache</a> is the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> cache in its
+   <a href=#application-cache-group>application cache group</a>, and the <a href=#application-cache-group>application
+   cache group</a> is not marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>.</dd>
 
    <dt><dfn id=dom-appcache-checking title=dom-appcache-CHECKING><code>CHECKING</code></dfn>
    (numeric value 2)</dt>
@@ -30931,17 +30949,25 @@
    <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
    an <a href=#application-cache>application cache</a> whose <a href=#application-cache-group>application cache
    group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update
-   status</a> is <i>idle</i>, but that application cache is
-   <em>not</em> the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a>
-   cache in its group.</dd>
+   status</a> is <i>idle</i>, and whose <a href=#application-cache-group>application cache
+   group</a> is not marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, but that
+   <a href=#application-cache>application cache</a> is <em>not</em> the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> 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 <a href=#application-cache-group>application cache
+   group</a> is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>.</dd>
 
   </dl><hr><p>If the <dfn id=dom-appcache-update title=dom-appcache-update><code>update()</code></dfn> method is
   invoked, the user agent must invoke the <a href=#application-cache-update-process>application cache
   update process</a>, in the background, for the <a href=#application-cache>application
   cache</a> with which the <code><a href=#applicationcache>ApplicationCache</a></code> object is
   associated, but with no <a href=#browsing-context>browsing context</a>. If there is
-  no such application cache, then the method must raise an
-  <code><a href=#invalid_state_err>INVALID_STATE_ERR</a></code> exception instead.<p>If the <dfn id=dom-appcache-swapcache title=dom-appcache-swapCache><code>swapCache()</code></dfn> method
+  no such application cache, or if it is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, then the method
+  must raise an <code><a href=#invalid_state_err>INVALID_STATE_ERR</a></code> exception instead.<p>If the <dfn id=dom-appcache-swapcache title=dom-appcache-swapCache><code>swapCache()</code></dfn> method
   is invoked, the user agent must run the following steps:
 
   <ol><li><p>Let <var title="">document</var> be the
@@ -30958,6 +30984,11 @@
    associated. (By definition, this is the same as the one that was
    found in the previous step.)</li>
 
+   <li><p>If <var title="">cache</var>'s <a href=#application-cache-group>application cache
+   group</a> is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, then raise an
+   <code><a href=#invalid_state_err>INVALID_STATE_ERR</a></code> exception and abort these
+   steps.</li>
+
    <li><p>Check that there is an application cache in the same
    <a href=#application-cache-group>application cache group</a> as <var title="">cache</var>
    whose <a href=#concept-appcache-completeness title=concept-appcache-completeness>completeness
Received on Friday, 23 January 2009 00:13:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:57 GMT