[e] (0) add a note about script execution

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10539 git-svn-id: http://svn.whatwg.org/webapps@5597 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Oct 11, 2010 · aa36d14 · aa36d14
1 parent f2311db
commit aa36d14
Show file tree

Hide file tree

Showing 3 changed files with 62 additions and 2 deletions.
diff --git a/complete.html b/complete.html
@@ -214,7 +214,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">Draft Standard &mdash; 7 October 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard &mdash; 11 October 2010</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>-->
@@ -14612,6 +14612,26 @@ <h4 id=script><span class=secno>4.3.1 </span>The <dfn><code>script</code></dfn>
   <code><a href=#document>Document</a></code> is used by the <code><a href=#document>Document</a></code>'s
   parser(s).</p>
 
+  <p class=note>If a <code><a href=#script>script</a></code> element that blocks a
+  parser gets moved to another <code><a href=#document>Document</a></code> before it would
+  normally have stopped blocking that parser, it nonetheless continues
+  blocking that parser until the condition that causes it to be
+  blocking the parser no longer applies (e.g. if the script is a
+  <a href=#pending-parsing-blocking-script>pending parsing-blocking script</a> because there was
+  <a href=#a-style-sheet-that-is-blocking-scripts>a style sheet that is blocking scripts</a> when it was
+  parsed, but then the script is moved to another
+  <code><a href=#document>Document</a></code> before the style sheet loads, the script still
+  blocks the parser until the style sheets are all loaded, at which
+  time the script executes and the parser is unblocked).</p>
+
+  <!-- also (and this would be worth testing): the way the spec is
+  written, if you do not have a style sheet that is blocking scripts,
+  then you parse a <script src>, then while waiting for the script to
+  load you insert an external style sheet, the script will delay until
+  the sheet is loaded, because there's just a binary "are style sheets
+  blocking scripts" state, things aren't defined in terms of which
+  style sheets are blocking which scripts -->
+
   <p><dfn id=executing-a-script-block title="executing a script block">Executing a script
   block</dfn>: When the steps above require that the script block be
   executed, the user agent must act as follows:</p>

diff --git a/index b/index
@@ -218,7 +218,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>HTML5 (including next generation additions still in development)</h1>
-    <h2 class="no-num no-toc">Draft Standard &mdash; 7 October 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard &mdash; 11 October 2010</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>-->
@@ -14589,6 +14589,26 @@ c-end         = "--&gt;"</pre>
   <code><a href=#document>Document</a></code> is used by the <code><a href=#document>Document</a></code>'s
   parser(s).</p>
 
+  <p class=note>If a <code><a href=#script>script</a></code> element that blocks a
+  parser gets moved to another <code><a href=#document>Document</a></code> before it would
+  normally have stopped blocking that parser, it nonetheless continues
+  blocking that parser until the condition that causes it to be
+  blocking the parser no longer applies (e.g. if the script is a
+  <a href=#pending-parsing-blocking-script>pending parsing-blocking script</a> because there was
+  <a href=#a-style-sheet-that-is-blocking-scripts>a style sheet that is blocking scripts</a> when it was
+  parsed, but then the script is moved to another
+  <code><a href=#document>Document</a></code> before the style sheet loads, the script still
+  blocks the parser until the style sheets are all loaded, at which
+  time the script executes and the parser is unblocked).</p>
+
+  <!-- also (and this would be worth testing): the way the spec is
+  written, if you do not have a style sheet that is blocking scripts,
+  then you parse a <script src>, then while waiting for the script to
+  load you insert an external style sheet, the script will delay until
+  the sheet is loaded, because there's just a binary "are style sheets
+  blocking scripts" state, things aren't defined in terms of which
+  style sheets are blocking which scripts -->
+
   <p><dfn id=executing-a-script-block title="executing a script block">Executing a script
   block</dfn>: When the steps above require that the script block be
   executed, the user agent must act as follows:</p>

diff --git a/source b/source
@@ -15491,6 +15491,26 @@ c-end         = "-->"</pre>
   <code>Document</code> is used by the <code>Document</code>'s
   parser(s).</p>
 
+  <p class="note">If a <code>script</code> element that blocks a
+  parser gets moved to another <code>Document</code> before it would
+  normally have stopped blocking that parser, it nonetheless continues
+  blocking that parser until the condition that causes it to be
+  blocking the parser no longer applies (e.g. if the script is a
+  <span>pending parsing-blocking script</span> because there was
+  <span>a style sheet that is blocking scripts</span> when it was
+  parsed, but then the script is moved to another
+  <code>Document</code> before the style sheet loads, the script still
+  blocks the parser until the style sheets are all loaded, at which
+  time the script executes and the parser is unblocked).</p>
+
+  <!-- also (and this would be worth testing): the way the spec is
+  written, if you do not have a style sheet that is blocking scripts,
+  then you parse a <script src>, then while waiting for the script to
+  load you insert an external style sheet, the script will delay until
+  the sheet is loaded, because there's just a binary "are style sheets
+  blocking scripts" state, things aren't defined in terms of which
+  style sheets are blocking which scripts -->
+
   <p><dfn title="executing a script block">Executing a script
   block</dfn>: When the steps above require that the script block be
   executed, the user agent must act as follows:</p>