html5/spec spec.html,1.1349,1.1350 tokenization.html,1.53,1.54 webappapis.html,1.147,1.148

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv25396

Modified Files:
	spec.html tokenization.html webappapis.html 
Log Message:
Don't spin the event loop before each script in the parser, only do it if necessary. (whatwg r5716)

[updated by splitter]


Index: tokenization.html
===================================================================
RCS file: /sources/public/html5/spec/tokenization.html,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -d -r1.53 -r1.54
--- tokenization.html	5 Dec 2010 09:44:16 -0000	1.53
+++ tokenization.html	8 Dec 2010 22:46:39 -0000	1.54
@@ -4865,7 +4865,10 @@
        for this instance of the <a href="parsing.html#html-parser">HTML parser</a>, such that
        the <a href="webappapis.html#event-loop">event loop</a> will not run <a href="webappapis.html#concept-task" title="concept-task">tasks</a> that invoke the <a href="#tokenization" title="tokenization">tokenizer</a>.</p></li>
 
-       <li><p><a href="webappapis.html#spin-the-event-loop">Spin the event loop</a> until the parser's
+       <li><p>If the parser's <code><a href="infrastructure.html#document">Document</a></code> <a href="semantics.html#has-a-style-sheet-that-is-blocking-scripts">has a style
+       sheet that is blocking scripts</a> or <var title="">the
+       script</var>'s <a href="scripting-1.html#ready-to-be-parser-executed">"ready to be parser-executed"</a> flag
+       is not set: <a href="webappapis.html#spin-the-event-loop">spin the event loop</a> until the parser's
        <code><a href="infrastructure.html#document">Document</a></code> <a href="semantics.html#has-no-style-sheet-that-is-blocking-scripts">has no style sheet that is blocking
        scripts</a> and <var title="">the script</var>'s
        <a href="scripting-1.html#ready-to-be-parser-executed">"ready to be parser-executed"</a> flag is

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1349
retrieving revision 1.1350
diff -u -d -r1.1349 -r1.1350
--- spec.html	8 Dec 2010 21:46:46 -0000	1.1349
+++ spec.html	8 Dec 2010 22:46:39 -0000	1.1350
@@ -385,7 +385,7 @@
     <a href="Overview.html">single page HTML</a>,
     <a href="spec.html">multipage HTML</a>,
     <a href="author/">web developer edition</a>.
-This is revision 1.4579.
+This is revision 1.4581.
    </p> 
      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2010 <a href="http://www.w3.org/"><abbr title="World Wide

Index: webappapis.html
===================================================================
RCS file: /sources/public/html5/spec/webappapis.html,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -d -r1.147 -r1.148
--- webappapis.html	8 Dec 2010 21:46:46 -0000	1.147
+++ webappapis.html	8 Dec 2010 22:46:39 -0000	1.148
@@ -866,15 +866,27 @@
 
   </ol><hr><p>Some of the algorithms in this specification, for historical
   reasons, require the user agent to <dfn id="pause">pause</dfn> while running a
-  <a href="#concept-task" title="concept-task">task</a> until some condition has been
-  met. While a user agent has a paused <a href="#concept-task" title="concept-task">task</a>, the corresponding <a href="#event-loop">event
-  loop</a> must not run further <a href="#concept-task" title="concept-task">tasks</a>, and any script in the currently
-  running <a href="#concept-task" title="concept-task">task</a> must block. User
-  agents should remain responsive to user input while paused, however,
-  albeit in a reduced capacity since the <a href="#event-loop">event loop</a> will
-  not be doing anything.</p>
+  <a href="#concept-task" title="concept-task">task</a> until a condition <var title="">goal</var> is met. This means running the following
+  steps:</p>
 
-  <hr><p>When a user agent is to <dfn id="obtain-the-storage-mutex">obtain the storage mutex</dfn> as
+  <ol><li><p>If any asynchronously-running algorithms are <a href="#await-a-stable-state" title="await a stable state">awaiting a stable state</a>, then
+   run their <a href="#synchronous-section">synchronous section</a> and then resume running
+   their asynchronous algorithm. (See the <a href="#event-loop">event loop</a>
+   processing model definition above for details.)</p>
+
+   </li><li><p>If necessary, update the rendering or user interface of any
+   <code><a href="infrastructure.html#document">Document</a></code> or <a href="browsers.html#browsing-context">browsing context</a> to reflect
+   the current state.</p></li>
+
+   <li><p>Wait until the condition <var title="">goal</var> is met.
+   While a user agent has a paused <a href="#concept-task" title="concept-task">task</a>, the corresponding <a href="#event-loop">event
+   loop</a> must not run further <a href="#concept-task" title="concept-task">tasks</a>, and any script in the currently
+   running <a href="#concept-task" title="concept-task">task</a> must block. User
+   agents should remain responsive to user input while paused,
+   however, albeit in a reduced capacity since the <a href="#event-loop">event
+   loop</a> will not be doing anything.</p></li>
+
+  </ol><hr><p>When a user agent is to <dfn id="obtain-the-storage-mutex">obtain the storage mutex</dfn> as
   part of running a <a href="#concept-task" title="concept-task">task</a>, it must
   run through the following steps:</p>

Received on Wednesday, 8 December 2010 22:46:43 UTC