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

html5/spec Overview.html,1.3313,1.3314

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 18 Oct 2009 10:47:27 +0000
To: public-html-commits@w3.org
Message-Id: <E1MzTIO-0001zm-2y@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv7656

Modified Files:
	Overview.html 
Log Message:
Move the definition of Matching a fallback namespace, which was in the middle of nowhere, into the earlier definitions section. (whatwg r4167)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3313
retrieving revision 1.3314
diff -u -d -r1.3313 -r1.3314
--- Overview.html	18 Oct 2009 10:37:05 -0000	1.3313
+++ Overview.html	18 Oct 2009 10:47:24 -0000	1.3314
@@ -859,12 +859,11 @@
        <li><a href="#writing-cache-manifests"><span class="secno">6.9.3.2 </span>Writing cache manifests</a></li>
        <li><a href="#parsing-cache-manifests"><span class="secno">6.9.3.3 </span>Parsing cache manifests</a></ol></li>
      <li><a href="#updating-an-application-cache"><span class="secno">6.9.4 </span>Updating an application cache</a></li>
-     <li><a href="#matching-a-fallback-namespace"><span class="secno">6.9.5 </span>Matching a fallback namespace</a></li>
-     <li><a href="#the-application-cache-selection-algorithm"><span class="secno">6.9.6 </span>The application cache selection algorithm</a></li>
-     <li><a href="#changesToNetworkingModel"><span class="secno">6.9.7 </span>Changes to the networking model</a></li>
-     <li><a href="#expiring-application-caches"><span class="secno">6.9.8 </span>Expiring application caches</a></li>
-     <li><a href="#application-cache-api"><span class="secno">6.9.9 </span>Application cache API</a></li>
-     <li><a href="#browser-state"><span class="secno">6.9.10 </span>Browser state</a></ol></li>
+     <li><a href="#the-application-cache-selection-algorithm"><span class="secno">6.9.5 </span>The application cache selection algorithm</a></li>
+     <li><a href="#changesToNetworkingModel"><span class="secno">6.9.6 </span>Changes to the networking model</a></li>
+     <li><a href="#expiring-application-caches"><span class="secno">6.9.7 </span>Expiring application caches</a></li>
+     <li><a href="#application-cache-api"><span class="secno">6.9.8 </span>Application cache API</a></li>
+     <li><a href="#browser-state"><span class="secno">6.9.9 </span>Browser state</a></ol></li>
    <li><a href="#history"><span class="secno">6.10 </span>Session history and navigation</a>
     <ol>
      <li><a href="#the-session-history-of-browsing-contexts"><span class="secno">6.10.1 </span>The session history of browsing contexts</a></li>
@@ -44788,7 +44787,32 @@
 
    <li>which application cache the user prefers.
 
-  </ul></div><h4 id="manifests"><span class="secno">6.9.3 </span>The cache manifest syntax</h4><h5 id="a-sample-manifest"><span class="secno">6.9.3.1 </span>A sample manifest</h5><p><i>This section is non-normative.</i><p>This example manifest requires two images and a style sheet to be
+  </ul><hr><p>A URL <dfn id="concept-appcache-matches-fallback" title="concept-appcache-matches-fallback">matches a
+  fallback namespace</dfn> if there exists a <a href="#relevant-application-cache">relevant
+  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 that 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 a fallback namespace can
+  match more than one application cache at a time, but only matches
+  one namespace in each cache.</p>
+
+  <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: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>
+
+  </div><h4 id="manifests"><span class="secno">6.9.3 </span>The cache manifest syntax</h4><h5 id="a-sample-manifest"><span class="secno">6.9.3.1 </span>A sample manifest</h5><p><i>This section is non-normative.</i><p>This example manifest requires two images and a style sheet to be
   cached and whitelists a CGI script.<pre>CACHE MANIFEST
 # the above line is required
 
@@ -45900,35 +45924,8 @@
 
 
 
-  <h4 id="matching-a-fallback-namespace"><span class="secno">6.9.5 </span>Matching a fallback namespace</h4>
 
-  <p>A URL <dfn id="concept-appcache-matches-fallback" title="concept-appcache-matches-fallback">matches a
-  fallback namespace</dfn> if there exists a <a href="#relevant-application-cache">relevant
-  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 that 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 a fallback namespace can
-  match more than one application cache at a time, but only matches
-  one namespace in each cache.</p>
-
-  <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: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>
-
-
-  <h4 id="the-application-cache-selection-algorithm"><span class="secno">6.9.6 </span>The application cache selection algorithm</h4>
+  <h4 id="the-application-cache-selection-algorithm"><span class="secno">6.9.5 </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
@@ -46016,7 +46013,7 @@
 
    </dd>
 
-  </dl><h4 id="changesToNetworkingModel"><span class="secno">6.9.7 </span>Changes to the networking model</h4>
+  </dl><h4 id="changesToNetworkingModel"><span class="secno">6.9.6 </span>Changes to the networking model</h4>
 
   <p>When a <a href="#cache-host">cache host</a> is associated with an
   <a href="#application-cache">application cache</a> whose <a href="#concept-appcache-completeness" title="concept-appcache-completeness">completeness flag</a> is
@@ -46078,7 +46075,7 @@
   primed the first time), making the testing of offline applications
   simpler.</p>
 
-  </div><h4 id="expiring-application-caches"><span class="secno">6.9.8 </span>Expiring application caches</h4><p>As a general rule, user agents should not expire application
+  </div><h4 id="expiring-application-caches"><span class="secno">6.9.7 </span>Expiring application caches</h4><p>As a general rule, user agents should not expire application
   caches, except on request from the user, or after having been left
   unused for an extended period of time.<p>Implementors are encouraged to expose application caches in a
   manner related to HTTP cookies, allowing caches to be expired
@@ -46086,7 +46083,7 @@
   caches and cookies have similar implications with respect to privacy
   (e.g. if the site can identify the user when providing the cache, it
   can store data in the cache that can be used for cookie
-  resurrection).<h4 id="application-cache-api"><span class="secno">6.9.9 </span>Application cache API</h4><pre class="idl">interface <dfn id="applicationcache">ApplicationCache</dfn> {
+  resurrection).<h4 id="application-cache-api"><span class="secno">6.9.8 </span>Application cache API</h4><pre class="idl">interface <dfn id="applicationcache">ApplicationCache</dfn> {
 
   // <a href="#concept-appcache-status" title="concept-appcache-status">update status</a>
   const unsigned short <a href="#dom-appcache-uncached" title="dom-appcache-UNCACHED">UNCACHED</a> = 0;
@@ -46292,7 +46289,7 @@
     <tr><td><dfn id="handler-appcache-onupdateready" title="handler-appcache-onupdateready"><code>onupdateready</code></dfn> <td> <code title="event-appcache-updateready"><a href="#event-appcache-updateready">updateready</a></code>
     <tr><td><dfn id="handler-appcache-oncached" title="handler-appcache-oncached"><code>oncached</code></dfn> <td> <code title="event-appcache-cached"><a href="#event-appcache-cached">cached</a></code>
     <tr><td><dfn id="handler-appcache-onobsolete" title="handler-appcache-onobsolete"><code>onobsolete</code></dfn> <td> <code title="event-appcache-obsolete"><a href="#event-appcache-obsolete">obsolete</a></code>
-  </table></div><h4 id="browser-state"><span class="secno">6.9.10 </span>Browser state</h4><dl class="domintro"><dt><var title="">window</var> . <code title="dom-navigator"><a href="#dom-navigator">navigator</a></code> . <code title="dom-navigator-onLine"><a href="#dom-navigator-online">onLine</a></code></dt>
+  </table></div><h4 id="browser-state"><span class="secno">6.9.9 </span>Browser state</h4><dl class="domintro"><dt><var title="">window</var> . <code title="dom-navigator"><a href="#dom-navigator">navigator</a></code> . <code title="dom-navigator-onLine"><a href="#dom-navigator-online">onLine</a></code></dt>
 
    <dd>
 
Received on Sunday, 18 October 2009 10:47:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 18 October 2009 10:47:30 GMT