html5/spec Overview.html,1.1260,1.1261

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

Modified Files:
	Overview.html 
Log Message:
Clarify that we don't currently define the 'user interaction task source'; hopefully DOM3 Events will handle something like this eventually. (whatwg r2088)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1260
retrieving revision 1.1261
diff -u -d -r1.1260 -r1.1261
--- Overview.html	19 Aug 2008 23:29:55 -0000	1.1260
+++ Overview.html	20 Aug 2008 01:21:22 -0000	1.1261
@@ -27,7 +27,7 @@
     for HTML and XHTML</h2>
 
    <h2 class="no-num no-toc" id=editors0><!-- "W3C Working Draft" -->
-    Editor's Draft <!--ZZZ-->19 August 2008</h2>
+    Editor's Draft <!--ZZZ-->20 August 2008</h2>
 
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
@@ -199,7 +199,7 @@
 
   <p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is
    the W3C working group responsible for this specification's progress along
-   the W3C Recommendation track. <!--ZZZ:--> This specification is the 19
+   the W3C Recommendation track. <!--ZZZ:--> This specification is the 20
    August 2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
   <!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST -->
   <!-- relationship to other work (required) -->
@@ -32864,12 +32864,12 @@
 
   <p class=example>For example, a user agent could have one <a
    href="#task-queues">task queue</a> for mouse and key events (the
-   <span>user interaction task source</span><!-- XXX xref -->), and another
-   for everything else. The user agent could then give keyboard and mouse
-   events preference over other tasks three quarters of the time, keeping the
-   interface responsive but not starving other task queues, and never
-   processing events from any one <a href="#task-source">task source</a> out
-   of order.
+   <span>user interaction task source</span>, not defined in this
+   specification<!-- XXX xref -->), and another for everything else. The user
+   agent could then give keyboard and mouse events preference over other
+   tasks three quarters of the time, keeping the interface responsive but not
+   starving other task queues, and never processing events from any one <a
+   href="#task-source">task source</a> out of order.
 
   <p>An <a href="#event3">event loop</a> must continually run through the
    following steps for as long as it exists:

Received on Wednesday, 20 August 2008 01:22:00 UTC