W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2011

html5/spec Overview.html,1.5312,1.5313

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 04 Oct 2011 20:03:19 +0000
To: public-html-commits@w3.org
Message-Id: <E1RBBCx-0002UM-Uy@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv9510

Modified Files:
	Overview.html 
Log Message:
accuracy (whatwg r6625)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5312
retrieving revision 1.5313
diff -u -d -r1.5312 -r1.5313
--- Overview.html	4 Oct 2011 19:58:28 -0000	1.5312
+++ Overview.html	4 Oct 2011 20:03:15 -0000	1.5313
@@ -2656,10 +2656,10 @@
   attributes and methods on that object <span class="impl">must</span>
   operate on the actual underlying data, not a snapshot of the
   data.<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 id="concept-events-trusted" title="concept-events-trusted">trusted event</dfn> is used to refer
+  <dfn id="concept-event-dispatch" 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 id="concept-events-trusted" 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><h4 id="plugins"><span class="secno">2.1.5 </span>Plugins</h4><p>The term <dfn id="plugin">plugin</dfn> refers to a user-agent defined set of
   content handlers used by the user agent that can take part in the
   user agent's rendering of a <code><a href="#document">Document</a></code> object, but that
@@ -50511,20 +50511,11 @@
   <p>When an event is dispatched at a DOM node in a
   <code><a href="#document">Document</a></code> in a <a href="#browsing-context">browsing context</a>, if the
   event is not a <code title="event-load">load</code> event, the user
-  agent must also dispatch the event to the <code><a href="#window">Window</a></code>, as
-  follows:</p>
-
-  <ol><li>In the capture phase, the event must propagate to the
-   <code><a href="#window">Window</a></code> object before propagating to any of the nodes,
-   as if the <code><a href="#window">Window</a></code> object was the parent of the
-   <code><a href="#document">Document</a></code> in the dispatch chain.</li>
-
-   <li>In the bubble phase, the event must propagate up to the
-   <code><a href="#window">Window</a></code> object at the end of the phase, unless bubbling
-   has been prevented, again as if the <code><a href="#window">Window</a></code> object was
-   the parent of the <code><a href="#document">Document</a></code> in the dispatch chain.</li>
+  agent must act as if, for the purposes of <a href="#concept-event-dispatch" title="concept-event-dispatch">event dispatching</a>, the
+  <code><a href="#window">Window</a></code> object is the parent of the
+  <code><a href="#document">Document</a></code> object. <a href="#refsDOMCORE">[DOMCORE]</a></p>
 
-  </ol></div><h3 id="atob"><span class="secno">6.2 </span>Base64 utility methods</h3><p>The <code title="dom-windowbase64-atob"><a href="#dom-windowbase64-atob">atob()</a></code> and <code title="dom-windowbase64-btoa"><a href="#dom-windowbase64-btoa">btoa()</a></code> methods allow authors to
+  </div><h3 id="atob"><span class="secno">6.2 </span>Base64 utility methods</h3><p>The <code title="dom-windowbase64-atob"><a href="#dom-windowbase64-atob">atob()</a></code> and <code title="dom-windowbase64-btoa"><a href="#dom-windowbase64-btoa">btoa()</a></code> methods allow authors to
   transform content to and from the base64 encoding.</p><pre class="idl">[NoInterfaceObject]
 interface <dfn id="windowbase64">WindowBase64</dfn> {
   DOMString <a href="#dom-windowbase64-btoa" title="dom-windowbase64-btoa">btoa</a>(DOMString btoa);
Received on Tuesday, 4 October 2011 20:03:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 October 2011 20:03:22 GMT