Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) Move the definition of Matching a fallback namespace, which w…
…as in the middle of nowhere, into the earlier definitions section.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7771

git-svn-id: http://svn.whatwg.org/webapps@4167 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 18, 2009
1 parent 7ba724d commit 6d42790
Show file tree
Hide file tree
Showing 3 changed files with 106 additions and 109 deletions.
76 changes: 37 additions & 39 deletions complete.html
Expand Up @@ -736,12 +736,11 @@ <h2 class="no-num no-toc" id=contents>Table of contents</h2>
<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>
Expand Down Expand Up @@ -52797,7 +52796,33 @@ <h4 id=appcache><span class=secno>6.9.2 </span>Application caches</h4>

<li>which application cache the user prefers.

</ul></div>
</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>
Expand Down Expand Up @@ -53966,35 +53991,8 @@ <h4 id=updating-an-application-cache><span class=secno>6.9.4 </span>Updating an



<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
Expand Down Expand Up @@ -54082,7 +54080,7 @@ <h4 id=the-application-cache-selection-algorithm><span class=secno>6.9.6 </span>

</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
Expand Down Expand Up @@ -54147,7 +54145,7 @@ <h4 id=the-application-cache-selection-algorithm><span class=secno>6.9.6 </span>
</div>


<h4 id=expiring-application-caches><span class=secno>6.9.8 </span>Expiring application caches</h4>
<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
Expand All @@ -54163,7 +54161,7 @@ <h4 id=expiring-application-caches><span class=secno>6.9.8 </span>Expiring appli



<h4 id=application-cache-api><span class=secno>6.9.9 </span>Application cache API</h4>
<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> {

Expand Down Expand Up @@ -54378,7 +54376,7 @@ <h4 id=application-cache-api><span class=secno>6.9.9 </span>Application cache AP
</table></div>


<h4 id=browser-state><span class=secno>6.9.10 </span>Browser state</h4>
<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>

Expand Down
76 changes: 37 additions & 39 deletions index
Expand Up @@ -712,12 +712,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>
Expand Down Expand Up @@ -49956,7 +49955,33 @@ clock.js</pre>

<li>which application cache the user prefers.

</ul></div>
</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>
Expand Down Expand Up @@ -51125,35 +51150,8 @@ NETWORK:



<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
Expand Down Expand Up @@ -51241,7 +51239,7 @@ NETWORK:

</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
Expand Down Expand Up @@ -51306,7 +51304,7 @@ NETWORK:
</div>


<h4 id=expiring-application-caches><span class=secno>6.9.8 </span>Expiring application caches</h4>
<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
Expand All @@ -51322,7 +51320,7 @@ NETWORK:



<h4 id=application-cache-api><span class=secno>6.9.9 </span>Application cache API</h4>
<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> {

Expand Down Expand Up @@ -51537,7 +51535,7 @@ NETWORK:
</table></div>


<h4 id=browser-state><span class=secno>6.9.10 </span>Browser state</h4>
<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>

Expand Down
63 changes: 32 additions & 31 deletions source
Expand Up @@ -59469,9 +59469,41 @@ interface <dfn>NavigatorAbilities</dfn> {

</ul>

<hr>

<p>A URL <dfn title="concept-appcache-matches-fallback">matches a
fallback namespace</dfn> if there exists a <span>relevant
application cache</span> whose <span
title="concept-appcache-manifest">manifest</span>'s URL has the
<span>same origin</span> as the URL in question, and that has a
<span title="concept-appcache-fallback-ns">fallback namespace</span>
that is a <span>prefix match</span> 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">The cache manifest syntax</h4>


Expand Down Expand Up @@ -60841,37 +60873,6 @@ NETWORK:



<h4>Matching a fallback namespace</h4>

<p>A URL <dfn title="concept-appcache-matches-fallback">matches a
fallback namespace</dfn> if there exists a <span>relevant
application cache</span> whose <span
title="concept-appcache-manifest">manifest</span>'s URL has the
<span>same origin</span> as the URL in question, and that has a
<span title="concept-appcache-fallback-ns">fallback namespace</span>
that is a <span>prefix match</span> 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>The application cache selection algorithm</h4>

Expand Down

0 comments on commit 6d42790

Please sign in to comment.