[html5] r5715 - [giow] (1) Define 'pause' as running synchronous sections.

[whatwg at whatwg.org]

Author: ianh
Date: 2010-12-08 14:04:19 -0800 (Wed, 08 Dec 2010)
New Revision: 5715

Modified:
   complete.html
   index
   source
Log:
[giow] (1) Define 'pause' as running synchronous sections.

Modified: complete.html
===================================================================
--- complete.html	2010-12-08 20:50:59 UTC (rev 5714)
+++ complete.html	2010-12-08 22:04:19 UTC (rev 5715)
@@ -63355,15 +63355,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><p>If necessary, update the rendering or user interface of any
+   <code><a href=#document>Document</a></code> or <a href=#browsing-context>browsing context</a> to reflect
+   the current state.</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.</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>
 

Modified: index
===================================================================
--- index	2010-12-08 20:50:59 UTC (rev 5714)
+++ index	2010-12-08 22:04:19 UTC (rev 5715)
@@ -63356,15 +63356,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><p>If necessary, update the rendering or user interface of any
+   <code><a href=#document>Document</a></code> or <a href=#browsing-context>browsing context</a> to reflect
+   the current state.</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.</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>
 

Modified: source
===================================================================
--- source	2010-12-08 20:50:59 UTC (rev 5714)
+++ source	2010-12-08 22:04:19 UTC (rev 5715)
@@ -72112,16 +72112,34 @@
 
   <p>Some of the algorithms in this specification, for historical
   reasons, require the user agent to <dfn>pause</dfn> while running a
-  <span title="concept-task">task</span> until some condition has been
-  met. While a user agent has a paused <span
-  title="concept-task">task</span>, the corresponding <span>event
-  loop</span> must not run further <span
-  title="concept-task">tasks</span>, and any script in the currently
-  running <span title="concept-task">task</span> must block. User
-  agents should remain responsive to user input while paused, however,
-  albeit in a reduced capacity since the <span>event loop</span> will
-  not be doing anything.</p>
+  <span title="concept-task">task</span> until a condition <var
+  title="">goal</var> is met. This means running the following
+  steps:</p>
 
+  <ol>
+
+   <li><p>If any asynchronously-running algorithms are <span
+   title="await a stable state">awaiting a stable state</span>, then
+   run their <span>synchronous section</span> and then resume running
+   their asynchronous algorithm. (See the <span>event loop</span>
+   processing model definition above for details.)</p>
+
+   <li><p>If necessary, update the rendering or user interface of any
+   <code>Document</code> or <span>browsing context</span> 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 <span
+   title="concept-task">task</span>, the corresponding <span>event
+   loop</span> must not run further <span
+   title="concept-task">tasks</span>, and any script in the currently
+   running <span title="concept-task">task</span> must block. User
+   agents should remain responsive to user input while paused,
+   however, albeit in a reduced capacity since the <span>event
+   loop</span> will not be doing anything.</p></li>
+
+  </ol>
+
   <hr>
 
   <p>When a user agent is to <dfn>obtain the storage mutex</dfn> as