[html5] r2349 - [e] (0) Appcache: try to clarify some requirements.

[whatwg at whatwg.org]

Author: ianh
Date: 2008-10-17 15:40:30 -0700 (Fri, 17 Oct 2008)
New Revision: 2349

Modified:
   index
   source
Log:
[e] (0) Appcache: try to clarify some requirements.

Modified: index
===================================================================
--- index	2008-10-17 22:38:18 UTC (rev 2348)
+++ index	2008-10-17 22:40:30 UTC (rev 2349)
@@ -34603,8 +34603,8 @@
 
        <dd>
 
-        <p>Copy the resource and its metadata from <var title="">cache</var>, and ignore the resource obtained from
-        the network.</p>
+        <p>Copy the resource and its metadata from <var title="">cache</var>, and act as if that was the fetched
+        resource, ignoring the resource obtained from the network.</p>
 
        </dd>
 
@@ -34947,9 +34947,8 @@
     equivalent, or if there were network errors (but not if the user
     canceled the download), then instead get, from the cache, the
     resource of the <a href=#concept-appcache-fallback title=concept-appcache-fallback>fallback
-    entry</a> corresponding to the namespace with the longest
-    matching <a href=#url-path title=url-path><path></a>
-    component. Abort these steps.</p>
+    entry</a> corresponding to the matched namespace. Abort these
+    steps.</p>
 
    </li>
 
@@ -35864,10 +35863,12 @@
     on session history, e.g. bookmarking) the user agent must use the
     URL of the resource that was requested (the one that matched the
     <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback
-    namespace</a>), not the fallback resource. However, the user
-    agent may indicate to the user that the original page load failed,
-    that the page used was a fallback resource, and what the URL of
-    the fallback resource actually is.</p>
+    namespace</a>), not the fallback resource, as the resource's
+    <span title="the document's address">address</span><!-- XXXDOCURL
+    -->. However, the user agent may indicate to the user that the
+    original page load failed, that the page used was a fallback
+    resource, and what the URL of the fallback resource actually
+    is.</p>
 
    </li>
 

Modified: source
===================================================================
--- source	2008-10-17 22:38:18 UTC (rev 2348)
+++ source	2008-10-17 22:40:30 UTC (rev 2349)
@@ -39295,8 +39295,8 @@
        <dd>
 
         <p>Copy the resource and its metadata from <var
-        title="">cache</var>, and ignore the resource obtained from
-        the network.</p>
+        title="">cache</var>, and act as if that was the fetched
+        resource, ignoring the resource obtained from the network.</p>
 
        </dd>
 
@@ -39701,9 +39701,8 @@
     equivalent, or if there were network errors (but not if the user
     canceled the download), then instead get, from the cache, the
     resource of the <span title="concept-appcache-fallback">fallback
-    entry</span> corresponding to the namespace with the longest
-    matching <span title="url-path"><path></span>
-    component. Abort these steps.</p>
+    entry</span> corresponding to the matched namespace. Abort these
+    steps.</p>
 
    </li>
 
@@ -40766,10 +40765,12 @@
     on session history, e.g. bookmarking) the user agent must use the
     URL of the resource that was requested (the one that matched the
     <span title="concept-appcache-fallback-ns">fallback
-    namespace</span>), not the fallback resource. However, the user
-    agent may indicate to the user that the original page load failed,
-    that the page used was a fallback resource, and what the URL of
-    the fallback resource actually is.</p>
+    namespace</span>), not the fallback resource, as the resource's
+    <span title="the document's address">address</span><!-- XXXDOCURL
+    -->. However, the user agent may indicate to the user that the
+    original page load failed, that the page used was a fallback
+    resource, and what the URL of the fallback resource actually
+    is.</p>
 
    </li>