spec/Overview.html 1.1866 2696 When getting the manifest fails, don't a

When getting the manifest fails, don't associate the resource with the
cache, since the resource is probably screwed up / too new / a captive
portal anyway. (whatwg r2696)

5.7.5 Matching a fallback namespace
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1866.html#matching-a-fallback-namespace
cache attempt
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1866.html#concept-appcache-cache
cache failure steps
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1866.html#cache-failure-steps
5.7.6 The application cache selection algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1866.html#the-application-cache-selection-algorithm

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1865&r2=1.1866&f=h
http://html5.org/tools/web-apps-tracker?from=2695&to=2696

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1865
retrieving revision 1.1866
diff -u -d -r1.1865 -r1.1866
--- Overview.html 23 Jan 2009 01:01:10 -0000 1.1865
+++ Overview.html 23 Jan 2009 01:11:55 -0000 1.1866
@@ -30307,7 +30307,7 @@
     or the server reported it as "304 Not Modified" <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, anything else?) --><li><p>Let <var title="">cache</var> be the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> <a href=#application-cache>application
+    <ol><li><p>Let <var title="">cache</var> be the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> <a href=#application-cache>application
      cache</a> in <var title="">cache group</var>.</li>
 
      <li>
@@ -30433,10 +30433,12 @@
      <li>
 
       <p><a href=#fetch>Fetch</a> the resource. If this is an <a href=#concept-appcache-upgrade title=concept-appcache-upgrade>upgrade attempt</a>, then
-      use <var title="">cache</var> as an HTTP cache, and honor HTTP
-      caching semantics (such as expiration, ETags, and so forth) with
-      respect to that cache. User agents may also have other caches in
-      place that are also honored.</p>
+      use the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a>
+      <a href=#application-cache>application cache</a> in <var title="">cache
+      group</var> as an HTTP cache, and honor HTTP caching semantics
+      (such as expiration, ETags, and so forth) with respect to that
+      cache. User agents may also have other caches in place that are
+      also honored.</p>
 
       <p class=note>If the resource in question is already being
       downloaded for other reasons then the existing download process
@@ -30695,9 +30697,6 @@
      that the user agent failed to save the application for offline
      use.</li>
 
-     <li><p>Let <var title="">cache</var> be the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> <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
@@ -30707,21 +30706,17 @@
       <ol><li><p>Wait for the resource for this entry to have completely
        downloaded.</p>
 
-       <li><p>If the download was successful, associate the
-       <code>Document</code> for this entry with <var title="">cache</var> (unassociating it from the other
-       <a href=#application-cache>application cache</a> it is associated with, if any),
-       store the resource for this entry in <var title="">cache</var>,
-       if it isn't already there, and categorize its entry as a <a href=#concept-appcache-master title=concept-appcache-master>master entry</a>.</li>
+       <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>
+       <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>
 
@@ -30730,7 +30725,7 @@
 
      <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 discrad that <a href=#application-cache>application
+     <i>incomplete</i>, then discard that <a href=#application-cache>application
      cache</a>.</p>
 
      <li><p>If appropriate, remove any user interface indicating that
@@ -30772,7 +30767,7 @@
 
   </div><h4 id=the-application-cache-selection-algorithm><span class=secno>5.7.6 </span>The application cache selection algorithm</h4><p>When the <dfn id=concept-appcache-init title=concept-appcache-init>application cache
   selection algorithm</dfn> algorithm is invoked with a
-  <code>Document</code> <var title="">document</var> and optinally a
+  <code>Document</code> <var title="">document</var> and optionally a
   manifest <a href=#url>URL</a> <var title="">manifest URL</var>, the user
   agent must run the first applicable set of steps from the following
   list:<dl class=switch><dt>If <var title="">document</var> was loaded from an

Received on Friday, 23 January 2009 01:25:15 UTC