[giow] (2) Fix a race condition

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17010 Affected topics: HTML git-svn-id: http://svn.whatwg.org/webapps@7108 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · May 30, 2012 · 5ce5eda · 5ce5eda
1 parent 4eed8a3
commit 5ce5eda
Show file tree

Hide file tree

Showing 3 changed files with 29 additions and 11 deletions.
diff --git a/complete.html b/complete.html
@@ -240,7 +240,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><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 &mdash; Last Updated 29 May 2012</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 30 May 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -26596,11 +26596,17 @@ <h4 id=the-object-element><span class=secno>4.8.4 </span>The <dfn><code>object</
 
    <li>the element changes from <a href=#being-rendered>being rendered</a> to not being rendered, or vice versa,
 
-  </ul><p>...the user agent must <a href=#queue-a-task>queue a task</a> to run the
+  </ul><!-- Changing the base URL doesn't trigger this. --><p>...the user agent must <a href=#queue-a-task>queue a task</a> to run the
   following steps to (re)determine what the <code><a href=#the-object-element>object</a></code>
   element represents. The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#dom-manipulation-task-source>DOM manipulation task
-  source</a>.</p> <!-- Changing the base URL doesn't trigger this.
-  -->
+  source</a>. This <a href=#concept-task title=concept-task>task</a> being
+  <a href=#queue-a-task title="queue a task">queued</a> or actively running must
+  <a href=#delay-the-load-event>delay the load event</a> of the element's document. <!--As
+  described in the algorithm, once the algorithm starts fetching a
+  resource, the fetch is what starts delaying the load event. But to
+  tide us over from when the parser finds the <object> element and the
+  fetching begins, we have to block the load event like this, lest the
+  parse end before this task gets run.--></p>
 
   <ol><li>
 

diff --git a/index b/index
@@ -240,7 +240,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><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 &mdash; Last Updated 29 May 2012</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 30 May 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -26596,11 +26596,17 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
 
    <li>the element changes from <a href=#being-rendered>being rendered</a> to not being rendered, or vice versa,
 
-  </ul><p>...the user agent must <a href=#queue-a-task>queue a task</a> to run the
+  </ul><!-- Changing the base URL doesn't trigger this. --><p>...the user agent must <a href=#queue-a-task>queue a task</a> to run the
   following steps to (re)determine what the <code><a href=#the-object-element>object</a></code>
   element represents. The <a href=#task-source>task source</a> for this <a href=#concept-task title=concept-task>task</a> is the <a href=#dom-manipulation-task-source>DOM manipulation task
-  source</a>.</p> <!-- Changing the base URL doesn't trigger this.
-  -->
+  source</a>. This <a href=#concept-task title=concept-task>task</a> being
+  <a href=#queue-a-task title="queue a task">queued</a> or actively running must
+  <a href=#delay-the-load-event>delay the load event</a> of the element's document. <!--As
+  described in the algorithm, once the algorithm starts fetching a
+  resource, the fetch is what starts delaying the load event. But to
+  tide us over from when the parser finds the <object> element and the
+  fetching begins, we have to block the load event like this, lest the
+  parse end before this task gets run.--></p>
 
   <ol><li>
 

diff --git a/source b/source
@@ -28652,14 +28652,20 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
 
    <li>the element changes from <span>being rendered</span> to not being rendered, or vice versa,
 
-  </ul>
+  </ul> <!-- Changing the base URL doesn't trigger this. -->
 
   <p>...the user agent must <span>queue a task</span> to run the
   following steps to (re)determine what the <code>object</code>
   element represents. The <span>task source</span> for this <span
   title="concept-task">task</span> is the <span>DOM manipulation task
-  source</span>.</p> <!-- Changing the base URL doesn't trigger this.
-  -->
+  source</span>. This <span title="concept-task">task</span> being
+  <span title="queue a task">queued</span> or actively running must
+  <span>delay the load event</span> of the element's document. <!--As
+  described in the algorithm, once the algorithm starts fetching a
+  resource, the fetch is what starts delaying the load event. But to
+  tide us over from when the parser finds the <object> element and the
+  fetching begins, we have to block the load event like this, lest the
+  parse end before this task gets run.--></p>
 
   <ol>