hixie: Clarify the weird interaction of <object> and manifest=''. (whatwg r5943)

hixie: Clarify the weird interaction of <object> and manifest=''.
(whatwg r5943)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4783&r2=1.4784&f=h
http://html5.org/tools/web-apps-tracker?from=5942&to=5943

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4783
retrieving revision 1.4784
diff -u -d -r1.4783 -r1.4784
--- Overview.html 4 Mar 2011 02:56:55 -0000 1.4783
+++ Overview.html 4 Mar 2011 23:29:48 -0000 1.4784
@@ -20872,6 +20872,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
@@ -21165,12 +21170,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 -->
 
@@ -21454,7 +21466,7 @@
   &lt;/body&gt;
 &lt;/html&gt;</pre>
 
-  </div><h4 id="video"><span class="secno">4.8.6 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-accessibility) and <a href="http://www.w3.org/html/wg/tracker/issues/142">ISSUE-142</a> (poster-alt) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
+  </div><h4 id="video"><span class="secno">4.8.6 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/142">ISSUE-142</a> (poster-alt) blocks progress to Last Call</span><dl class="element"><dt>Categories</dt>
    <dd><a href="#flow-content">Flow content</a>.</dd>
    <dd><a href="#phrasing-content">Phrasing content</a>.</dd>
    <dd><a href="#embedded-content">Embedded content</a>.</dd>
@@ -22046,7 +22058,7 @@
  ...
 &lt;/video&gt;</pre>
 
-  </div><!--KEEP-END w3c-html--><!--TT--><!--<div data-component="other Hixie drafts (editor: Ian Hickson)">--><h4 id="the-track-element"><span class="secno">4.8.9 </span>The <dfn><code>track</code></dfn> element</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-accessibility) blocks progress to Last Call</span><dl class="element"><dt>Categories</dt>
+  </div><!--KEEP-END w3c-html--><!--TT--><!--<div data-component="other Hixie drafts (editor: Ian Hickson)">--><h4 id="the-track-element"><span class="secno">4.8.9 </span>The <dfn><code>track</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
    <dd>None.</dd>
    <dt>Contexts in which this element can be used:</dt>
    <dd>As a child of a <a href="#media-element">media element</a>, before any <a href="#flow-content">flow content</a>.</dd>
@@ -44510,12 +44522,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>
 
@@ -44531,9 +44549,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>

Received on Friday, 4 March 2011 23:31:03 UTC