[html5] r5810 - [giow] (1) make sure online whitelists override fallback namespaces even for bro [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Jan 31 16:13:34 PST 2011
Author: ianh
Date: 2011-01-31 16:13:33 -0800 (Mon, 31 Jan 2011)
New Revision: 5810
Modified:
complete.html
index
source
Log:
[giow] (1) make sure online whitelists override fallback namespaces even for browsing context navigation loads.
Modified: complete.html
===================================================================
--- complete.html 2011-01-31 23:58:16 UTC (rev 5809)
+++ complete.html 2011-02-01 00:13:33 UTC (rev 5810)
@@ -221,7 +221,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 31 January 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 1 February 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -60481,9 +60481,14 @@
URL <a href=#concept-appcache-matches-fallback title=concept-appcache-matches-fallback>matches the
fallback namespace</a> of one or more <a href=#relevant-application-cache title="relevant
application cache">relevant application caches</a>, and the
- user didn't cancel the navigation attempt during the previous
- step, and the navigation attempt failed (e.g. the server returned
- a 4xx or 5xx status code <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>, or
+ <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate
+ application cache</a> of those that match does not have an
+ entry in its <a href=#concept-appcache-onlinewhitelist title=concept-appcache-onlinewhitelist>online
+ whitelist</a> that has the <a href=#same-origin>same origin</a> as the
+ resource's URL and that is a <a href=#prefix-match>prefix match</a> for the
+ resource's URL, and the user didn't cancel the navigation attempt
+ during the previous step, and the navigation attempt failed (e.g.
+ the server returned a 4xx or 5xx status code <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>, or
there was a DNS error), then:</p> <!-- note that a redirect can
never reach this point as it is handled earlier, meaning that a
captive portal captures URLs in fallback namespaces and you can't
Modified: index
===================================================================
--- index 2011-01-31 23:58:16 UTC (rev 5809)
+++ index 2011-02-01 00:13:33 UTC (rev 5810)
@@ -225,7 +225,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 31 January 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 1 February 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -60463,9 +60463,14 @@
URL <a href=#concept-appcache-matches-fallback title=concept-appcache-matches-fallback>matches the
fallback namespace</a> of one or more <a href=#relevant-application-cache title="relevant
application cache">relevant application caches</a>, and the
- user didn't cancel the navigation attempt during the previous
- step, and the navigation attempt failed (e.g. the server returned
- a 4xx or 5xx status code <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>, or
+ <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate
+ application cache</a> of those that match does not have an
+ entry in its <a href=#concept-appcache-onlinewhitelist title=concept-appcache-onlinewhitelist>online
+ whitelist</a> that has the <a href=#same-origin>same origin</a> as the
+ resource's URL and that is a <a href=#prefix-match>prefix match</a> for the
+ resource's URL, and the user didn't cancel the navigation attempt
+ during the previous step, and the navigation attempt failed (e.g.
+ the server returned a 4xx or 5xx status code <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>, or
there was a DNS error), then:</p> <!-- note that a redirect can
never reach this point as it is handled earlier, meaning that a
captive portal captures URLs in fallback namespaces and you can't
Modified: source
===================================================================
--- source 2011-01-31 23:58:16 UTC (rev 5809)
+++ source 2011-02-01 00:13:33 UTC (rev 5810)
@@ -68711,9 +68711,14 @@
URL <span title="concept-appcache-matches-fallback">matches the
fallback namespace</span> of one or more <span title="relevant
application cache">relevant application caches</span>, and the
- user didn't cancel the navigation attempt during the previous
- step, and the navigation attempt failed (e.g. the server returned
- a 4xx or 5xx status code <span
+ <span title="concept-appcache-selection">most appropriate
+ application cache</span> of those that match does not have an
+ entry in its <span title="concept-appcache-onlinewhitelist">online
+ whitelist</span> that has the <span>same origin</span> as the
+ resource's URL and that is a <span>prefix match</span> for the
+ resource's URL, and the user didn't cancel the navigation attempt
+ during the previous step, and the navigation attempt failed (e.g.
+ the server returned a 4xx or 5xx status code <span
title="concept-http-equivalent-codes">or equivalent</span>, or
there was a DNS error), then:</p> <!-- note that a redirect can
never reach this point as it is handled earlier, meaning that a
More information about the Commit-Watchers
mailing list