HTML5 Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/6625

SVNBugCommentTime (UTC)
662513822accuracy2011-10-04 20:00
Index: source
===================================================================
--- source	(revision 6624)
+++ source	(revision 6625)
@@ -2133,10 +2133,10 @@
   data.</p>
 
   <p>In the contexts of events, the terms <dfn title="">fire</dfn> and
-  <dfn title="">dispatch</dfn> are used as defined in the DOM Core
-  specification: firing an event means to create and dispatch it, and
-  dispatching an event means to follow the steps that propagate the
-  event through the tree. The term <dfn
+  <dfn title="concept-event-dispatch">dispatch</dfn> are used as
+  defined in the DOM Core specification: firing an event means to
+  create and dispatch it, and dispatching an event means to follow the
+  steps that propagate the event through the tree. The term <dfn
   title="concept-events-trusted">trusted event</dfn> is used to refer
   to events that have the <span>trusted flag</span> set. <a
   href="#refsDOMCORE">[DOMCORE]</a></p>
@@ -41873,9 +41873,7 @@
     wholesale, with no composition, alpha blending, no shadows,
     etc.</p>
 
-    <p>If the first argument is null, throws a
-    <code>TypeMismatchError</code> exception. Throws a
-    <code>NotSupportedError</code> exception if any of the other
+    <p>Throws a <code>NotSupportedError</code> exception if any of the
     arguments are not finite.</p>
 
    </dd>
@@ -78882,23 +78880,12 @@
   <p>When an event is dispatched at a DOM node in a
   <code>Document</code> in a <span>browsing context</span>, if the
   event is not a <code title="event-load">load</code> event, the user
-  agent must also dispatch the event to the <code>Window</code>, as
-  follows:</p>
+  agent must act as if, for the purposes of <span
+  title="concept-event-dispatch">event dispatching</span>, the
+  <code>Window</code> object is the parent of the
+  <code>Document</code> object. <a
+  href="#refsDOMCORE">[DOMCORE]</a></p>
 
-  <ol>
-
-   <li>In the capture phase, the event must propagate to the
-   <code>Window</code> object before propagating to any of the nodes,
-   as if the <code>Window</code> object was the parent of the
-   <code>Document</code> in the dispatch chain.</li>
-
-   <li>In the bubble phase, the event must propagate up to the
-   <code>Window</code> object at the end of the phase, unless bubbling
-   has been prevented, again as if the <code>Window</code> object was
-   the parent of the <code>Document</code> in the dispatch chain.</li>
-
-  </ol>
-
   </div>
 
 

|