[html5] r5943 - [e] (0) Clarify the weird interaction of <object> and manifest=''. Fixing http:/ [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Mar 4 15:29:40 PST 2011
Author: ianh
Date: 2011-03-04 15:29:38 -0800 (Fri, 04 Mar 2011)
New Revision: 5943
Modified:
complete.html
index
source
Log:
[e] (0) Clarify the weird interaction of <object> and manifest=''.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12024
Modified: complete.html
===================================================================
--- complete.html 2011-03-04 02:56:49 UTC (rev 5942)
+++ complete.html 2011-03-04 23:29:38 UTC (rev 5943)
@@ -24164,6 +24164,11 @@
until the <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking task
source</a> once the resource has been <a href=#fetch title=fetch>fetched</a> (defined next) has been run.</p>
+ <p>For the purposes of the <a href=#application-cache>application cache</a>
+ networking model, this <a href=#fetch>fetch</a> operation is not for a
+ <a href=#child-browsing-context>child browsing context</a> (though it might end up
+ being used for one after all, as defined below).</p>
+
</li>
<li><p>If the resource is not yet available (e.g. because the
@@ -24457,12 +24462,19 @@
to the value of this attribute; otherwise, the <a href=#browsing-context-name>browsing
context name</a> must be set to the empty string.</p>
- <p class=note>It's possible that the <a href=#navigate title=navigate>navigation</a> of the <a href=#browsing-context>browsing
- context</a> will actually obtain the resource from a
- different <a href=#application-cache>application cache</a>. Even if the resource
- is then found to have a different type, it is still used as
- part of a <a href=#nested-browsing-context>nested browsing context</a>; this algorithm
- doesn't restart with the new resource.</p>
+ <p class=note>In certain situations, e.g. if the resource
+ was <a href=#fetch title=fetch>fetched</a> from an
+ <a href=#application-cache>application cache</a> but it is an HTML file with a
+ <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute
+ that points to a different <a href=#concept-appcache-manifest title=concept-appcache-manifest>application cache
+ manifest</a>, the <a href=#navigate title=navigate>navigation</a>
+ of the <a href=#browsing-context>browsing context</a> will be restarted so as
+ to load the resource afresh from the network or a different
+ <a href=#application-cache>application cache</a>. Even if the resource is then
+ found to have a different type, it is still used as part of a
+ <a href=#nested-browsing-context>nested browsing context</a>: only the
+ <a href=#navigate>navigate</a> algorithm is restarted, not this
+ <code><a href=#the-object-element>object</a></code> algorithm.</p>
<!-- note that malformed XML files don't cause fallback -->
@@ -60587,12 +60599,18 @@
<li>
- <p>If the new resource is to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, then
- check if there are any <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>. If so, then the
+ <p>If the resource has already been obtained (e.g. because it is
+ being used to populate an <code><a href=#the-object-element>object</a></code> element's new
+ <a href=#child-browsing-context>child browsing context</a>), then skip this step.</p>
+
+ <p>Otherwise:</p>
+
+ <p>If the new resource is 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>, then the
user agent must then get the resource from the <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application
cache</a> of those that match.</p>
@@ -60608,9 +60626,8 @@
application cache at all; the submission will be made to the
network.</p>
- <p>Otherwise, unless it has already been obtained<!-- it's
- obtained by <object>, for instance -->, <a href=#fetch>fetch</a> the new
- resource, with the <i>manual redirect flag</i> set.</p>
+ <p>Otherwise, <a href=#fetch>fetch</a> the new resource, with the
+ <i>manual redirect flag</i> set.</p>
<p>If the resource is being fetched using a method other than one
<a href=#concept-http-equivalent-get title=concept-http-equivalent-get>equivalent to</a>
Modified: index
===================================================================
--- index 2011-03-04 02:56:49 UTC (rev 5942)
+++ index 2011-03-04 23:29:38 UTC (rev 5943)
@@ -24147,6 +24147,11 @@
until the <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking task
source</a> once the resource has been <a href=#fetch title=fetch>fetched</a> (defined next) has been run.</p>
+ <p>For the purposes of the <a href=#application-cache>application cache</a>
+ networking model, this <a href=#fetch>fetch</a> operation is not for a
+ <a href=#child-browsing-context>child browsing context</a> (though it might end up
+ being used for one after all, as defined below).</p>
+
</li>
<li><p>If the resource is not yet available (e.g. because the
@@ -24440,12 +24445,19 @@
to the value of this attribute; otherwise, the <a href=#browsing-context-name>browsing
context name</a> must be set to the empty string.</p>
- <p class=note>It's possible that the <a href=#navigate title=navigate>navigation</a> of the <a href=#browsing-context>browsing
- context</a> will actually obtain the resource from a
- different <a href=#application-cache>application cache</a>. Even if the resource
- is then found to have a different type, it is still used as
- part of a <a href=#nested-browsing-context>nested browsing context</a>; this algorithm
- doesn't restart with the new resource.</p>
+ <p class=note>In certain situations, e.g. if the resource
+ was <a href=#fetch title=fetch>fetched</a> from an
+ <a href=#application-cache>application cache</a> but it is an HTML file with a
+ <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute
+ that points to a different <a href=#concept-appcache-manifest title=concept-appcache-manifest>application cache
+ manifest</a>, the <a href=#navigate title=navigate>navigation</a>
+ of the <a href=#browsing-context>browsing context</a> will be restarted so as
+ to load the resource afresh from the network or a different
+ <a href=#application-cache>application cache</a>. Even if the resource is then
+ found to have a different type, it is still used as part of a
+ <a href=#nested-browsing-context>nested browsing context</a>: only the
+ <a href=#navigate>navigate</a> algorithm is restarted, not this
+ <code><a href=#the-object-element>object</a></code> algorithm.</p>
<!-- note that malformed XML files don't cause fallback -->
@@ -60570,12 +60582,18 @@
<li>
- <p>If the new resource is to be fetched using HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or equivalent</a>, then
- check if there are any <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>. If so, then the
+ <p>If the resource has already been obtained (e.g. because it is
+ being used to populate an <code><a href=#the-object-element>object</a></code> element's new
+ <a href=#child-browsing-context>child browsing context</a>), then skip this step.</p>
+
+ <p>Otherwise:</p>
+
+ <p>If the new resource is 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>, then the
user agent must then get the resource from the <a href=#concept-appcache-selection title=concept-appcache-selection>most appropriate application
cache</a> of those that match.</p>
@@ -60591,9 +60609,8 @@
application cache at all; the submission will be made to the
network.</p>
- <p>Otherwise, unless it has already been obtained<!-- it's
- obtained by <object>, for instance -->, <a href=#fetch>fetch</a> the new
- resource, with the <i>manual redirect flag</i> set.</p>
+ <p>Otherwise, <a href=#fetch>fetch</a> the new resource, with the
+ <i>manual redirect flag</i> set.</p>
<p>If the resource is being fetched using a method other than one
<a href=#concept-http-equivalent-get title=concept-http-equivalent-get>equivalent to</a>
Modified: source
===================================================================
--- source 2011-03-04 02:56:49 UTC (rev 5942)
+++ source 2011-03-04 23:29:38 UTC (rev 5943)
@@ -25916,6 +25916,11 @@
source</span> once the resource has been <span
title="fetch">fetched</span> (defined next) has been run.</p>
+ <p>For the purposes of the <span>application cache</span>
+ networking model, this <span>fetch</span> operation is not for a
+ <span>child browsing context</span> (though it might end up
+ being used for one after all, as defined below).</p>
+
</li>
<li><p>If the resource is not yet available (e.g. because the
@@ -26244,13 +26249,20 @@
to the value of this attribute; otherwise, the <span>browsing
context name</span> must be set to the empty string.</p>
- <p class="note">It's possible that the <span
- title="navigate">navigation</span> of the <span>browsing
- context</span> will actually obtain the resource from a
- different <span>application cache</span>. Even if the resource
- is then found to have a different type, it is still used as
- part of a <span>nested browsing context</span>; this algorithm
- doesn't restart with the new resource.</p>
+ <p class="note">In certain situations, e.g. if the resource
+ was <span title="fetch">fetched</span> from an
+ <span>application cache</span> but it is an HTML file with a
+ <code title="attr-html-manifest">manifest</code> attribute
+ that points to a different <span
+ title="concept-appcache-manifest">application cache
+ manifest</span>, the <span title="navigate">navigation</span>
+ of the <span>browsing context</span> will be restarted so as
+ to load the resource afresh from the network or a different
+ <span>application cache</span>. Even if the resource is then
+ found to have a different type, it is still used as part of a
+ <span>nested browsing context</span>: only the
+ <span>navigate</span> algorithm is restarted, not this
+ <code>object</code> algorithm.</p>
<!-- note that malformed XML files don't cause fallback -->
@@ -68799,14 +68811,19 @@
<li>
+ <p>If the resource has already been obtained (e.g. because it is
+ being used to populate an <code>object</code> element's new
+ <span>child browsing context</span>), then skip this step.</p>
+
+ <p>Otherwise:</p>
+
<p>If the new resource is to be fetched using HTTP GET <span
- title="concept-http-equivalent-get">or equivalent</span>, then
- check if there are any <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>. If so, then the
+ 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>, then the
user agent must then get the resource from the <span
title="concept-appcache-selection">most appropriate application
cache</span> of those that match.</p>
@@ -68823,9 +68840,8 @@
application cache at all; the submission will be made to the
network.</p>
- <p>Otherwise, unless it has already been obtained<!-- it's
- obtained by <object>, for instance -->, <span>fetch</span> the new
- resource, with the <i>manual redirect flag</i> set.</p>
+ <p>Otherwise, <span>fetch</span> the new resource, with the
+ <i>manual redirect flag</i> set.</p>
<p>If the resource is being fetched using a method other than one
<span title="concept-http-equivalent-get">equivalent to</span>
More information about the Commit-Watchers
mailing list