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

git-svn-id: http://svn.whatwg.org/webapps@5715 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Dec 8, 2010 · f1ee8a9 · f1ee8a9
1 parent 2851b09
commit f1ee8a9
Show file tree

Hide file tree

Showing 3 changed files with 69 additions and 27 deletions.
diff --git a/complete.html b/complete.html
@@ -63355,15 +63355,27 @@ <h5 id=processing-model-2><span class=secno>7.1.4.2 </span>Processing model</h5>
 
   </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>
-
-  <hr><p>When a user agent is to <dfn id=obtain-the-storage-mutex>obtain the storage mutex</dfn> as
+  <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>
+
+  <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>
 

diff --git a/index b/index
@@ -63356,15 +63356,27 @@ NETWORK:
 
   </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>
-
-  <hr><p>When a user agent is to <dfn id=obtain-the-storage-mutex>obtain the storage mutex</dfn> as
+  <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>
+
+  <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>
 

diff --git a/source b/source
@@ -72112,15 +72112,33 @@ NETWORK:
 
   <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>