[html5] r7772 - [giow] (3) Appcache: Fallback when you're offline for prefer-online caches shoul [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Mar 25 16:39:43 PDT 2013
Author: ianh
Date: 2013-03-25 16:39:41 -0700 (Mon, 25 Mar 2013)
New Revision: 7772
Modified:
complete.html
index
source
Log:
[giow] (3) Appcache: Fallback when you're offline for prefer-online caches should prefer the cached copy of the real resource over a fallback resource if both exist.
Affected topics: HTML, Rendering
Modified: complete.html
===================================================================
--- complete.html 2013-03-25 23:36:37 UTC (rev 7771)
+++ complete.html 2013-03-25 23:39:41 UTC (rev 7772)
@@ -66869,6 +66869,36 @@
<li>
+ <p><strong>Fallback in prefer-online mode</strong>: If the resource was not fetched from an
+ <a href=#application-cache>application cache</a>, and was to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, and there are <a href=#relevant-application-cache title="relevant
+ application cache">relevant application caches</a> that are identified by a URL with the
+ <a href=#same-origin>same origin</a> as the URL in question, and that have this URL as one of their entries,
+ excluding entries marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, and whose
+ <a href=#concept-appcache-mode title=concept-appcache-mode>mode</a> is <a href=#concept-appcache-mode-prefer-online title=concept-appcache-mode-prefer-online>prefer-online</a>, and the user didn't cancel the
+ navigation attempt during the earlier 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>
+
+ <p>Let <var title="">candidate</var> be the resource identified by the URL in question from the
+ <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application cache</a> of those that
+ match.</p> <!-- note that a redirect can never reach this point as it is handled earlier,
+ meaning that a captive portal captures URLs in "prefer-online" caches and you can't ever get to
+ the cached resource of a prefer-online cache if you have a captive portal -->
+
+ <p>If <var title="">candidate</var> is not marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, then the user agent must discard the failed
+ load and instead continue along these steps using <var title="">candidate</var> as the resource.
+ The user agent may indicate to the user that the original page load failed, and that the page
+ used was a previously cached resource.</p>
+
+ <p class=note>This does not affect the <i>address of the resource from which Request-URIs are
+ obtained</i>, as used to set <a href="#the-document's-referrer">the document's referrer</a> in the <a href=#create-a-document-object>create a Document
+ object</a> steps below; they still use the value as computed by the original
+ <a href=#fetch>fetch</a> algorithm.</p>
+
+ </li>
+
+ <li>
+
<p><strong>Fallback for fallback entries</strong>: If the resource was not fetched from an
<a href=#application-cache>application cache</a>, and was to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, and its 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 <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application cache</a> of those that match
@@ -66903,37 +66933,6 @@
<li>
-<!--XXXswap-->
- <p><strong>Fallback in prefer-online mode</strong>: If the resource was not fetched from an
- <a href=#application-cache>application cache</a>, and was to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, and there are <a href=#relevant-application-cache title="relevant
- application cache">relevant application caches</a> that are identified by a URL with the
- <a href=#same-origin>same origin</a> as the URL in question, and that have this URL as one of their entries,
- excluding entries marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, and whose
- <a href=#concept-appcache-mode title=concept-appcache-mode>mode</a> is <a href=#concept-appcache-mode-prefer-online title=concept-appcache-mode-prefer-online>prefer-online</a>, and the user didn't cancel the
- navigation attempt during the earlier 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>
-
- <p>Let <var title="">candidate</var> be the resource identified by the URL in question from the
- <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application cache</a> of those that
- match.</p> <!-- note that a redirect can never reach this point as it is handled earlier,
- meaning that a captive portal captures URLs in "prefer-online" caches and you can't ever get to
- the cached resource of a prefer-online cache if you have a captive portal -->
-
- <p>If <var title="">candidate</var> is not marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, then the user agent must discard the failed
- load and instead continue along these steps using <var title="">candidate</var> as the resource.
- The user agent may indicate to the user that the original page load failed, and that the page
- used was a previously cached resource.</p>
-
- <p class=note>This does not affect the <i>address of the resource from which Request-URIs are
- obtained</i>, as used to set <a href="#the-document's-referrer">the document's referrer</a> in the <a href=#create-a-document-object>create a Document
- object</a> steps below; they still use the value as computed by the original
- <a href=#fetch>fetch</a> algorithm.</p>
-
- </li>
-
- <li>
-
<p><i>Resource handling</i>: If the resource's out-of-band metadata (e.g. HTTP headers), not
counting any <a href=#content-type title=Content-Type>type information</a> (such as the Content-Type HTTP
header), requires some sort of processing that will not affect the browsing context, then
@@ -92414,7 +92413,8 @@
their expected behavior by translating from the CSS rules given in this section.</p>
<p>In the absence of style-layer rules to the contrary (e.g. author style sheets), user agents are
- expected to render an element so that it conveys to the user the meaning that the element <span title=represent>represents</span>, as described by this specification.</p>
+ expected to render an element so that it conveys to the user the meaning that the element
+ <a href=#represents>represents</a>, as described by this specification.</p>
<p>The suggestions in this section generally assume a visual output medium with a resolution of
96dpi or greater, but HTML is intended to apply to multiple media (it is a
Modified: index
===================================================================
--- index 2013-03-25 23:36:37 UTC (rev 7771)
+++ index 2013-03-25 23:39:41 UTC (rev 7772)
@@ -66869,6 +66869,36 @@
<li>
+ <p><strong>Fallback in prefer-online mode</strong>: If the resource was not fetched from an
+ <a href=#application-cache>application cache</a>, and was to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, and there are <a href=#relevant-application-cache title="relevant
+ application cache">relevant application caches</a> that are identified by a URL with the
+ <a href=#same-origin>same origin</a> as the URL in question, and that have this URL as one of their entries,
+ excluding entries marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, and whose
+ <a href=#concept-appcache-mode title=concept-appcache-mode>mode</a> is <a href=#concept-appcache-mode-prefer-online title=concept-appcache-mode-prefer-online>prefer-online</a>, and the user didn't cancel the
+ navigation attempt during the earlier 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>
+
+ <p>Let <var title="">candidate</var> be the resource identified by the URL in question from the
+ <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application cache</a> of those that
+ match.</p> <!-- note that a redirect can never reach this point as it is handled earlier,
+ meaning that a captive portal captures URLs in "prefer-online" caches and you can't ever get to
+ the cached resource of a prefer-online cache if you have a captive portal -->
+
+ <p>If <var title="">candidate</var> is not marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, then the user agent must discard the failed
+ load and instead continue along these steps using <var title="">candidate</var> as the resource.
+ The user agent may indicate to the user that the original page load failed, and that the page
+ used was a previously cached resource.</p>
+
+ <p class=note>This does not affect the <i>address of the resource from which Request-URIs are
+ obtained</i>, as used to set <a href="#the-document's-referrer">the document's referrer</a> in the <a href=#create-a-document-object>create a Document
+ object</a> steps below; they still use the value as computed by the original
+ <a href=#fetch>fetch</a> algorithm.</p>
+
+ </li>
+
+ <li>
+
<p><strong>Fallback for fallback entries</strong>: If the resource was not fetched from an
<a href=#application-cache>application cache</a>, and was to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, and its 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 <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application cache</a> of those that match
@@ -66903,37 +66933,6 @@
<li>
-<!--XXXswap-->
- <p><strong>Fallback in prefer-online mode</strong>: If the resource was not fetched from an
- <a href=#application-cache>application cache</a>, and was to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, and there are <a href=#relevant-application-cache title="relevant
- application cache">relevant application caches</a> that are identified by a URL with the
- <a href=#same-origin>same origin</a> as the URL in question, and that have this URL as one of their entries,
- excluding entries marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, and whose
- <a href=#concept-appcache-mode title=concept-appcache-mode>mode</a> is <a href=#concept-appcache-mode-prefer-online title=concept-appcache-mode-prefer-online>prefer-online</a>, and the user didn't cancel the
- navigation attempt during the earlier 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>
-
- <p>Let <var title="">candidate</var> be the resource identified by the URL in question from the
- <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application cache</a> of those that
- match.</p> <!-- note that a redirect can never reach this point as it is handled earlier,
- meaning that a captive portal captures URLs in "prefer-online" caches and you can't ever get to
- the cached resource of a prefer-online cache if you have a captive portal -->
-
- <p>If <var title="">candidate</var> is not marked as <a href=#concept-appcache-foreign title=concept-appcache-foreign>foreign</a>, then the user agent must discard the failed
- load and instead continue along these steps using <var title="">candidate</var> as the resource.
- The user agent may indicate to the user that the original page load failed, and that the page
- used was a previously cached resource.</p>
-
- <p class=note>This does not affect the <i>address of the resource from which Request-URIs are
- obtained</i>, as used to set <a href="#the-document's-referrer">the document's referrer</a> in the <a href=#create-a-document-object>create a Document
- object</a> steps below; they still use the value as computed by the original
- <a href=#fetch>fetch</a> algorithm.</p>
-
- </li>
-
- <li>
-
<p><i>Resource handling</i>: If the resource's out-of-band metadata (e.g. HTTP headers), not
counting any <a href=#content-type title=Content-Type>type information</a> (such as the Content-Type HTTP
header), requires some sort of processing that will not affect the browsing context, then
@@ -92414,7 +92413,8 @@
their expected behavior by translating from the CSS rules given in this section.</p>
<p>In the absence of style-layer rules to the contrary (e.g. author style sheets), user agents are
- expected to render an element so that it conveys to the user the meaning that the element <span title=represent>represents</span>, as described by this specification.</p>
+ expected to render an element so that it conveys to the user the meaning that the element
+ <a href=#represents>represents</a>, as described by this specification.</p>
<p>The suggestions in this section generally assume a visual output medium with a resolution of
96dpi or greater, but HTML is intended to apply to multiple media (it is a
Modified: source
===================================================================
--- source 2013-03-25 23:36:37 UTC (rev 7771)
+++ source 2013-03-25 23:39:41 UTC (rev 7772)
@@ -79492,6 +79492,39 @@
<li>
+ <p><strong>Fallback in prefer-online mode</strong>: If the resource was not fetched from an
+ <span>application cache</span>, and was to be fetched using HTTP GET <span
+ title="concept-http-equivalent-get">or equivalent</span>, and there are <span title="relevant
+ application cache">relevant application caches</span> that are identified by a URL with the
+ <span>same origin</span> as the URL in question, and that have this URL as one of their entries,
+ excluding entries marked as <span title="concept-appcache-foreign">foreign</span>, and whose
+ <span title="concept-appcache-mode">mode</span> is <span
+ title="concept-appcache-mode-prefer-online">prefer-online</span>, and the user didn't cancel the
+ navigation attempt during the earlier 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>
+
+ <p>Let <var title="">candidate</var> be the resource identified by the URL in question from the
+ <span title="concept-appcache-selection">most appropriate application cache</span> of those that
+ match.</p> <!-- note that a redirect can never reach this point as it is handled earlier,
+ meaning that a captive portal captures URLs in "prefer-online" caches and you can't ever get to
+ the cached resource of a prefer-online cache if you have a captive portal -->
+
+ <p>If <var title="">candidate</var> is not marked as <span
+ title="concept-appcache-foreign">foreign</span>, then the user agent must discard the failed
+ load and instead continue along these steps using <var title="">candidate</var> as the resource.
+ The user agent may indicate to the user that the original page load failed, and that the page
+ used was a previously cached resource.</p>
+
+ <p class="note">This does not affect the <i>address of the resource from which Request-URIs are
+ obtained</i>, as used to set <span>the document's referrer</span> in the <span>create a Document
+ object</span> steps below; they still use the value as computed by the original
+ <span>fetch</span> algorithm.</p>
+
+ </li>
+
+ <li>
+
<p><strong>Fallback for fallback entries</strong>: If the resource was not fetched from an
<span>application cache</span>, and was to be fetched using HTTP GET <span
title="concept-http-equivalent-get">or equivalent</span>, and its URL <span
@@ -79530,40 +79563,6 @@
<li>
-<!--XXXswap-->
- <p><strong>Fallback in prefer-online mode</strong>: If the resource was not fetched from an
- <span>application cache</span>, and was to be fetched using HTTP GET <span
- title="concept-http-equivalent-get">or equivalent</span>, and there are <span title="relevant
- application cache">relevant application caches</span> that are identified by a URL with the
- <span>same origin</span> as the URL in question, and that have this URL as one of their entries,
- excluding entries marked as <span title="concept-appcache-foreign">foreign</span>, and whose
- <span title="concept-appcache-mode">mode</span> is <span
- title="concept-appcache-mode-prefer-online">prefer-online</span>, and the user didn't cancel the
- navigation attempt during the earlier 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>
-
- <p>Let <var title="">candidate</var> be the resource identified by the URL in question from the
- <span title="concept-appcache-selection">most appropriate application cache</span> of those that
- match.</p> <!-- note that a redirect can never reach this point as it is handled earlier,
- meaning that a captive portal captures URLs in "prefer-online" caches and you can't ever get to
- the cached resource of a prefer-online cache if you have a captive portal -->
-
- <p>If <var title="">candidate</var> is not marked as <span
- title="concept-appcache-foreign">foreign</span>, then the user agent must discard the failed
- load and instead continue along these steps using <var title="">candidate</var> as the resource.
- The user agent may indicate to the user that the original page load failed, and that the page
- used was a previously cached resource.</p>
-
- <p class="note">This does not affect the <i>address of the resource from which Request-URIs are
- obtained</i>, as used to set <span>the document's referrer</span> in the <span>create a Document
- object</span> steps below; they still use the value as computed by the original
- <span>fetch</span> algorithm.</p>
-
- </li>
-
- <li>
-
<p><i>Resource handling</i>: If the resource's out-of-band metadata (e.g. HTTP headers), not
counting any <span title="Content-Type">type information</span> (such as the Content-Type HTTP
header), requires some sort of processing that will not affect the browsing context, then
@@ -108173,8 +108172,8 @@
their expected behavior by translating from the CSS rules given in this section.</p>
<p>In the absence of style-layer rules to the contrary (e.g. author style sheets), user agents are
- expected to render an element so that it conveys to the user the meaning that the element <span
- title="represent">represents</span>, as described by this specification.</p>
+ expected to render an element so that it conveys to the user the meaning that the element
+ <span>represents</span>, as described by this specification.</p>
<p>The suggestions in this section generally assume a visual output medium with a resolution of
96dpi or greater, but HTML is intended to apply to multiple media (it is a
More information about the Commit-Watchers
mailing list