W3C home > Mailing lists > Public > public-html-diffs@w3.org > October 2008

spec/Overview.html 1.1522 2349 Appcache: try to clarify some requiremen

From: poot <cvsmail@w3.org>
Date: Sat, 18 Oct 2008 07:43:26 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20081017224326.430B12BC39@toro.w3.mag.keio.ac.jp>

Appcache: try to clarify some requirements. (whatwg r2349)

Fragment identifiers: If the absolute URL of the new resource is the same as the address of the active document of the browsing context being navigated, ignoring any <fragment> components of those URLs, and the new resource is to be fetched using HTTP GET or equivalent, then navigate to that fragment identifier and abort these steps.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1522.html#navigate-fragid-step
cache attempt
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1522.html#concept-appcache-cache
5.7.5.1 Changes to the networking model
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1522.html#changesToNetworkingModel

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1521&r2=1.1522&f=h
http://html5.org/tools/web-apps-tracker?from=2348&to=2349

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1521
retrieving revision 1.1522
diff -u -d -r1.1521 -r1.1522
--- Overview.html	17 Oct 2008 22:38:24 -0000	1.1521
+++ Overview.html	17 Oct 2008 22:40:35 -0000	1.1522
@@ -28026,8 +28026,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>
 
@@ -28350,9 +28350,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>&lt;path&gt;</a>
-    component. Abort these steps.</p>
+    entry</a> corresponding to the matched namespace. Abort these
+    steps.</p>
 
    </li>
 
@@ -29074,10 +29073,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>
Received on Friday, 17 October 2008 22:44:03 GMT

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