W3C home > Mailing lists > Public > public-html-commits@w3.org > December 2010

html5/spec Overview.html,1.4579,1.4580

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 08 Dec 2010 22:04:28 +0000
To: public-html-commits@w3.org
Message-Id: <E1PQS7g-00058r-7M@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv19751

Modified Files:
	Overview.html 
Log Message:
Define 'pause' as running synchronous sections. (whatwg r5715)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4579
retrieving revision 1.4580
diff -u -d -r1.4579 -r1.4580
--- Overview.html	8 Dec 2010 20:51:04 -0000	1.4579
+++ Overview.html	8 Dec 2010 22:04:23 -0000	1.4580
@@ -47402,15 +47402,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>
 
Received on Wednesday, 8 December 2010 22:04:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 December 2010 22:04:31 GMT