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

html5/spec Overview.html,1.1515,1.1516

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 16 Oct 2008 01:04:40 +0000
To: public-html-commits@w3.org
Message-Id: <E1KqHI8-0007xR-CN@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv30563

Modified Files:
	Overview.html 
Log Message:
Make fallback namespaces use the whole URL instead of just the path. (whatwg r2343)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1515
retrieving revision 1.1516
diff -u -d -r1.1515 -r1.1516
--- Overview.html	16 Oct 2008 00:54:33 -0000	1.1515
+++ Overview.html	16 Oct 2008 01:04:37 -0000	1.1516
@@ -27509,8 +27509,8 @@
   with the namespace being the first URL of the data line, and the
   corresponding fallback page being the second URL. All the other
   pages to be cached must be listed in explicit sections.<p><a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>Fallback
-  namespaces</a> must have the <a href=#same-origin>same origin</a> as the
-  manifest itself.<p>A <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback
+  namespaces</a> and <a href=#concept-appcache-fallback title=concept-appcache-fallback>fallback entries</a> must have
+  the <a href=#same-origin>same origin</a> as the manifest itself.<p>A <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback
   namespace</a> must not be listed more than once.<p>URLs that the user agent is to put into the <a href=#concept-appcache-onlinewhitelist title=concept-appcache-onlinewhitelist>online whitelist</a>
   must all be specified in online whitelist sections. (This is needed
   for any URL that the page is intending to use to communicate back to
@@ -28058,22 +28058,23 @@
   fallback namespace</dfn> if there exists an <a href=#application-cache>application
   cache</a> whose <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a>'s URL has the
   <a href=#same-origin>same origin</a> as the URL in question, and if that
-  application cache has a <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespace</a> with
-  a <a href=#url-path title=url-path>&lt;path&gt;</a> component that is a
-  <a href=#prefix-match>prefix match</a> for the <a href=#url-path title=url-path>&lt;path&gt;</a> component of the URL being
-  examined. If multiple fallback namespaces match the same URL, the
-  one with the longest <a href=#url-path title=url-path>&lt;path&gt;</a> component is the one
-  that matches. A URL looking for an fallback namespace can match more
-  than one application cache at a time, but only matches one namespace
-  in each cache.<div class=example>
+  application cache has a <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespace</a> that
+  is a <a href=#prefix-match>prefix match</a> for the URL being examined. If
+  multiple fallback namespaces match the same URL, the longest one is
+  the one that matches. A URL looking for an fallback namespace can
+  match more than one application cache at a time, but only matches
+  one namespace in each cache.<div class=example>
 
    <p>If a manifest <code title="">http://example.com/app1/manifest</code> declares that
    <code title="">http://example.com/resources/images</code> is a
-   fallback namespace, and the user navigates to <code title="">http://example.com/resources/images/cat.png</code>, then
-   the user agent will decide that the application cache identified by
-   <code title="">http://example.com/app1/manifest</code> contains a
+   fallback namespace, and the user navigates to <code title="">HTTP://EXAMPLE.COM:80/resources/images/cat.png</code>,
+   then the user agent will decide that the application cache
+   identified by <code title="">http://example.com/app1/manifest</code> contains a
    namespace with a match for that URL.</p>
 
+   <!-- "resolve a url" canonicalises the case for the scheme and host
+   and removes the port if it is the default -->
+
   </div><p>When the <dfn id=concept-appcache-init-with-attribute title=concept-appcache-init-with-attribute>application cache
   selection algorithm</dfn> algorithm is invoked with a manifest URL,
   the user agent must run the first applicable set of steps from the
@@ -28210,8 +28211,8 @@
 
     <p>If the resource's URL has the <a href=#same-origin>same origin</a> as the
     manifest's URL, and there is a <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespace</a> in
-    the <a href=#application-cache>application cache</a> whose &lt;path&gt; component is
-    a <a href=#prefix-match>prefix match</a> for the resource's URL's <a href=#url-path title=url-path>&lt;path&gt;</a> component, then:</p>
+    the <a href=#application-cache>application cache</a> that is a <a href=#prefix-match>prefix
+    match</a> for the resource's URL, then:</p>
 
     <p><a href=#fetch>Fetch</a> the resource normally. If this results in a
     redirect to a resource with another <a href=#origin-0>origin</a>
Received on Thursday, 16 October 2008 01:16:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 October 2008 01:16:24 GMT