[html5] r2088 - [e] (0) Clarify that we don't currently define the 'user interaction task source [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2008-08-19 18:21:01 -0700 (Tue, 19 Aug 2008)
New Revision: 2088

Modified:
   index
   source
Log:
[e] (0) Clarify that we don't currently define the 'user interaction task source'; hopefully DOM3 Events will handle something like this eventually.

Modified: index
===================================================================
--- index	2008-08-19 23:30:05 UTC (rev 2087)
+++ index	2008-08-20 01:21:01 UTC (rev 2088)
@@ -28,7 +28,7 @@
 
    <h1 id=html-5>HTML 5</h1>
 
-   <h2 class="no-num no-toc" id=draft>Draft Recommendation — 19 August
+   <h2 class="no-num no-toc" id=draft>Draft Recommendation — 20 August
     2008</h2>
 
    <p>You can take part in this work. <a
@@ -32856,12 +32856,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:

Modified: source
===================================================================
--- source	2008-08-19 23:30:05 UTC (rev 2087)
+++ source	2008-08-20 01:21:01 UTC (rev 2088)
@@ -30150,12 +30150,13 @@
 
   <p class="example">For example, a user agent could have one
   <span>task queue</span> 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 <span>task source</span>
-  out of order.</p>
+  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 <span>task source</span> out of
+  order.</p>
 
   <p>An <span>event loop</span> must continually run through the
   following steps for as long as it exists:</p>