expanded 'resize' definition, reformatted markup
authorschepers
Mon, 01 Feb 2010 16:16:07 +0900
changeset 239 1a53f03a33a6
parent 238 030d734f6990
child 240 7dae8478167a
expanded 'resize' definition, reformatted markup
html/DOM3-Events.html
--- a/html/DOM3-Events.html	Mon Feb 01 16:13:59 2010 +0900
+++ b/html/DOM3-Events.html	Mon Feb 01 16:16:07 2010 +0900
@@ -1,19 +1,15 @@
-<?xml version="1.0"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
     <title>Document Object Model (DOM) Level 3 Events Specification</title>
-    <link rel="author" href="mailto:[email protected]" />
+    <link rel="author" href="mailto:[email protected]" />
     <link rel="help" href="http://www.w3.org/DOM/" />
-    
     <link rel="alternate stylesheet" type="text/css" media="screen" title="geek" href="geek.css" />
     <link rel="stylesheet" type="text/css" href="./spec.css" />
-    
     <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/w3c-tr.css" />
     <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED" />
     <!-- <link rel="local stylesheet" type="text/css" href="W3C-WD.css" /> -->
-
   </head>
   <body>
     <div id="Overview" class="head">
@@ -24,24 +20,19 @@
       </p>
       <h1 id="Overview-title">Document Object Model (DOM) Level 3 Events Specification</h1>
 <!-- @@@ -->
-      <h2 id="Overview-W3C-doctype">W3C Editor's Draft <time datetime="2010-01-30">30 January 2010</time></h2>
+      <h2 id="Overview-W3C-doctype">W3C Editor's Draft <time datetime="2010-02-01">01 February 2010</time></h2>
       <dl>
         <dt>This version:</dt>
-        <dd>
-          <a href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.117">http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.117</a>
-        </dd>
+        <dd><a href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.118">http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.118</a></dd>
+
         <dt>Latest stable version:</dt>
-        <dd>
-          <a href="http://www.w3.org/TR/DOM-Level-3-Events">http://www.w3.org/TR/DOM-Level-3-Events</a>
-        </dd>
+        <dd><a href="http://www.w3.org/TR/DOM-Level-3-Events">http://www.w3.org/TR/DOM-Level-3-Events</a></dd>
+
         <dt>Previous version:</dt>
-        <dd>
-          <a href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.116">http://dev.w3.org/cvsweb/~checkout~/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.116</a>
-        </dd>
+        <dd><a href="http://dev.w3.org/cvsweb/~checkout~/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.117">http://dev.w3.org/cvsweb/~checkout~/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.117</a></dd>
+
         <dt>Editor's Draft:</dt>
-        <dd>
-          <a href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html">http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html</a>
-        </dd>
+        <dd><a href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html">http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html</a></dd>
       </dl>
       <dl>
         <dt>Editors:</dt>
@@ -58,6 +49,7 @@
     </div>
     <hr title="separator from header" />
     <h2><a id="Overview-abstract" href="#Overview-abstract">Abstract</a></h2>
+
     <div class="abstract">
       <p>This specification defines the Document Object Model Events Level 3, a generic platform- and language-neutral event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2 [<a href="#references-DOM2Events">DOM2 Events</a>].</p>
     </div>
@@ -65,7 +57,6 @@
     <div>
       <p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a>  at http://www.w3.org/TR/.</em></p>
       <p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
-      
       <p id="this-document-was-produced-by-a-group-op">This document was
         produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
         2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of any patent disclosures</a> made in
@@ -100,96 +91,56 @@
         before it eventually reaches the Candidate Recommendation stage should
         join the aforementioned mailing lists and take part in the discussions.</p>
     </div>
+    
     <h2 id="Overview-table-of-contents">
       <a id="Overview-contents">Table of Contents</a>
     </h2>
     <ul class="toc">
-      <li>
-        <a href="#dom-events">1. Document Object Model Events</a>
+      <li><a href="#dom-events">1. Document Object Model Events</a>
         <ul class="toc">
-          <li>
-            <a href="#dom-events-overview">1.1 Introduction</a>
-          </li>
-          <li>
-            <a href="#dom-events-conformance">1.2 Conformance</a>
-          </li>
-          <li>
-            <a href="#feature-detection">1.3 Feature Detection</a>
-          </li>
-          <li>
-            <a href="#style-conventions">1.4 Stylistic Conventions</a>
-          </li>
+          <li><a href="#dom-events-overview">1.1 Introduction</a></li>
+          <li><a href="#dom-events-conformance">1.2 Conformance</a></li>
+          <li><a href="#feature-detection">1.3 Feature Detection</a></li>
+          <li><a href="#style-conventions">1.4 Stylistic Conventions</a></li>
         </ul>
       </li>
-      <li>
-        <a href="#glossary" class="glossary">2. Glossary</a>
-      </li>
-      <li>
-        <a href="#dom-event-architecture">3. DOM Event Architecture</a>
+      <li><a href="#glossary" class="glossary">2. Glossary</a></li>
+      <li><a href="#dom-event-architecture">3. DOM Event Architecture</a>
         <ul class="toc">
-          <li>
-            <a href="#event-flow">3.1 Event dispatch and DOM event flow</a>
-          </li>
-          <li>
-            <a href="#event-flow-default-cancel">3.2 Default actions and cancelable events</a>
-          </li>
-          <li>
-            <a href="#sync-async">3.3 Synchronous and asynchronous events</a>
-          </li>
-          <li>
-            <a href="#trusted-events">3.4 Trusted events</a>
-          </li>
-          <li>
-            <a href="#event-flow-activation">3.5 Activation triggers and behavior</a>
+          <li><a href="#event-flow">3.1 Event dispatch and DOM event flow</a></li>
+          <li><a href="#event-flow-default-cancel">3.2 Default actions and cancelable events</a></li>
+          <li><a href="#sync-async">3.3 Synchronous and asynchronous events</a></li>
+          <li><a href="#trusted-events">3.4 Trusted events</a></li>
+          <li><a href="#event-flow-activation">3.5 Activation triggers and behavior</a>
             <ul class="toc">
-              <li>
-                <a href="#events-activation-event-order">3.5.1 Activation Event Order</a>
-              </li>
+              <li><a href="#events-activation-event-order">3.5.1 Activation Event Order</a></li>
             </ul>
           </li>
         </ul>
       </li>
-      <li>
-        <a href="#event-interfaces">4. Basic Event Interfaces</a>
+      <li><a href="#event-interfaces">4. Basic Event Interfaces</a>
         <ul class="toc">
-          <li>
-            <a href="#interface-Event">4.1 Interface Event</a>
-          </li>
-          <li>
-            <a href="#interface-CustomEvent">4.2 Interface CustomEvent</a>
-          </li>
-          <li>
-            <a href="#interface-EventTarget">4.3 Interface EventTarget</a>
-          </li>
-          <li>
-            <a href="#interface-EventListener">4.4 Interface EventListener</a>
-          </li>
-          <li>
-            <a href="#interface-DocumentEvent">4.5 Interface DocumentEvent</a>
+          <li><a href="#interface-Event">4.1 Interface Event</a></li>
+          <li><a href="#interface-CustomEvent">4.2 Interface CustomEvent</a></li>
+          <li><a href="#interface-EventTarget">4.3 Interface EventTarget</a></li>
+          <li><a href="#interface-EventListener">4.4 Interface EventListener</a></li>
+          <li><a href="#interface-DocumentEvent">4.5 Interface DocumentEvent</a>
             <ul class="toc">
-              <li>
-                <a href="#event-creation">4.5.1 Event creation</a>
-              </li>
+              <li><a href="#event-creation">4.5.1 Event creation</a></li>
             </ul>
           </li>
         </ul>
       </li>
-      <li>
-        <a href="#events-module">5. Events Module</a>
+      <li><a href="#events-module">5. Events Module</a>
         <ul class="toc">
-          <li>
-            <a href="#event-types">5.1 Event Types</a>
+          <li><a href="#event-types">5.1 Event Types</a>
             <ul class="toc">
-              <li>
-                <a href="#event-types-list">5.1.1 List of DOM3 Event Types</a>
-              </li>
+              <li><a href="#event-types-list">5.1.1 List of DOM3 Event Types</a></li>
             </ul>
           </li>
-          <li>
-            <a href="#event-definitions">5.2 Event Module Definitions</a>
+          <li><a href="#event-definitions">5.2 Event Module Definitions</a>
             <ul class="toc">
-              <li>
-                <a href="#events-uievents">5.2.1 User Interface Event Types</a>
+              <li><a href="#events-uievents">5.2.1 User Interface Event Types</a>
                 <ul class="toc">
                   <li><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-load"><code>load</code> event</a></li>
@@ -201,8 +152,7 @@
                   <li><a class="eventtype" href="#event-type-scroll"><code>scroll</code> event</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#events-focusevent">5.2.2 Focus Event Types</a>
+              <li><a href="#events-focusevent">5.2.2 Focus Event Types</a>
                 <ul class="toc">
                   <li><a href="#events-focusevent-event-order">5.2.1.1 Focus Interface Event Order</a></li>
                   <li><a href="#events-focusevent-doc-focus">5.2.1.2 Document Focus and Focus Context</a></li>
@@ -214,8 +164,7 @@
                   <li><a class="eventtype" href="#event-type-focusout"><code>focusout</code> event</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#events-mouseevents">5.2.3 Mouse Event Types</a>
+              <li><a href="#events-mouseevents">5.2.3 Mouse Event Types</a>
                 <ul class="toc">
                   <li><a href="#events-mouseevent-event-order">5.2.3.2 Mouse Event Order</a></li>
                   <li><a class="eventtype" href="#event-type-click"><code>click</code> event</a></li>
@@ -225,30 +174,21 @@
                   <li><a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-mouseover"><code>mouseover</code> event</a></li>
-                  <li><a class="eventtype" href="#event-type-mouseout"><code>mouseout</code> event</a></li>                  
+                  <li><a class="eventtype" href="#event-type-mouseout"><code>mouseout</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-mouseup"><code>mouseup</code> event</a></li>
                 </ul>
               </li>
-              <!-- <li>
-                <a href="#events-mousewheelevents">5.2.4 Mouse Wheel Event Types</a>
+              <li><a href="#events-wheelevents">5.2.4 Wheel Event Types</a>
                 <ul class="toc">
-                  <li><a class="eventtype" href="#event-type-mousewheel"><code>mousewheel</code> event</a></li>
-                </ul>
-              </li> -->
-              <li>
-                <a href="#events-wheelevents">5.2.4 Wheel Event Types</a>
-                <ul class="toc">
-                  <li><a class="eventtype" href="#event-type-wheel"><code>wheel</code> event</a></li>                  
+                  <li><a class="eventtype" href="#event-type-wheel"><code>wheel</code> event</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#events-textevents">5.2.5 Text Events Types</a>
+              <li><a href="#events-textevents">5.2.5 Text Events Types</a>
                 <ul class="toc">
                   <li><a class="eventtype" href="#event-type-textInput"><code>textInput</code> event</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#events-keyboardevents">5.2.6 Keyboard Event Types</a>
+              <li><a href="#events-keyboardevents">5.2.6 Keyboard Event Types</a>
                 <ul class="toc">
                   <li><a href="#events-keyboard-event-order">5.2.6.1 Keyboard Event Order</a></li>
                   <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code> event</a></li>
@@ -256,20 +196,16 @@
                   <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code> event</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#events-compositionevents">5.2.7 Composition Events Types</a>
+              <li><a href="#events-compositionevents">5.2.7 Composition Events Types</a>
                 <ul class="toc">
                   <li><a href="#events-composition-event-order">5.2.7.1 Composition Event Order</a></li>
                   <li><a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-compositionend"><code>compositionend</code> event</a></li>
-                  <li>
-                    <a href="#handwriting">5.2.7.2 Handwriting Recognition Systems</a>
-                  </li>
+                  <li><a href="#handwriting">5.2.7.2 Handwriting Recognition Systems</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#events-mutationevents">5.2.8 Mutation Events</a>
+              <li><a href="#events-mutationevents">5.2.8 Mutation Events</a>
                 <ul class="toc">
                   <li><a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code> event</a></li>
@@ -280,8 +216,7 @@
                   <li><a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code> event</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#events-mutationnameevents">5.2.9 Mutation Name Event Types</a>
+              <li><a href="#events-mutationnameevents">5.2.9 Mutation Name Event Types</a>
                 <ul class="toc">
                   <li><a class="eventtype" href="#event-type-DOMAttributeNameChanged"><code>DOMAttributeNameChanged</code> event</a></li>
                   <li><a class="eventtype" href="#event-type-DOMElementNameChanged"><code>DOMElementNameChanged</code> event</a></li>
@@ -291,142 +226,89 @@
           </li>
         </ul>
       </li>
-      <li>
-        <a href="#keyset">6. Keyboard events and key values</a>
+      <li><a href="#keyset">6. Keyboard events and key values</a>
         <ul class="toc">
-          <li>
-            <a href="#keyboard-input">6.1 Keyboard Input</a>
+          <li><a href="#keyboard-input">6.1 Keyboard Input</a>
             <ul class="toc">
-              <li>
-                <a href="#key-legends">6.1.1 Key Legends</a>
-              </li>
-              <li>
-                <a href="#keyboard-layout">6.1.2 Keyboard Layout</a>
+              <li><a href="#key-legends">6.1.1 Key Legends</a></li>
+              <li><a href="#keyboard-layout">6.1.2 Keyboard Layout</a>
                 <ul class="toc">
-                  <li>
-                    <a href="#keyboard-desktop">6.1.2.1 Desktop and Laptop Keyboards</a>
-                  </li>
-                  <li>
-                    <a href="#keyboard-mobile">6.1.2.2 Mobile Keypads</a>
-                  </li>
+                  <li><a href="#keyboard-desktop">6.1.2.1 Desktop and Laptop Keyboards</a></li>
+                  <li><a href="#keyboard-mobile">6.1.2.2 Mobile Keypads</a></li>
                 </ul>
               </li>
             </ul>
           </li>
-          <li>
-            <a href="#keyset-keyvalues">6.2 Key Values</a>
+          <li><a href="#keyset-keyvalues">6.2 Key Values</a>
             <ul class="toc">
-              <li>
-                <a href="#keyset-unicode">6.2.1 Key Values and Unicode</a>
-              </li>
-              <li>
-                <a href="#keyset-Modifiers">6.2.2 Modifier keys</a>
-              </li>
-              <li>
-                <a href="#keyset-DeadKeys">6.2.3 Dead keys</a>
-              </li>
-              <li>
-                <a href="#keyset-IME">6.2.4 Input Method Editors</a>
+              <li><a href="#keyset-unicode">6.2.1 Key Values and Unicode</a></li>
+              <li><a href="#keyset-Modifiers">6.2.2 Modifier keys</a></li>
+              <li><a href="#keyset-DeadKeys">6.2.3 Dead keys</a></li>
+              <li><a href="#keyset-IME">6.2.4 Input Method Editors</a>
                 <ul class="toc">
-                  <li>
-                    <a href="#keyset-IME_keys">6.2.4.1 Input Method Editor mode keys</a>
-                  </li>
+                  <li><a href="#keyset-IME_keys">6.2.4.1 Input Method Editor mode keys</a></li>
                 </ul>
               </li>
-              <li>
-                <a href="#keyset-cancelable_keys">6.2.5 Default actions and cancelable keyboard events</a>
-              </li>
-              <li>
-                <a href="#keyset-Guide">6.2.6 Guidelines for selecting and defining key values</a>
-              </li>
-              <li>
-                <a href="#key-values">6.2.7 Key Values Set</a>
-              </li>
-              <li>
-                <a href="#keyset-keyCode-charCode">6.2.8 Key values, keyCode, and charCode</a>
-              </li>
+              <li><a href="#keyset-cancelable_keys">6.2.5 Default actions and cancelable keyboard events</a></li>
+              <li><a href="#keyset-Guide">6.2.6 Guidelines for selecting and defining key values</a></li>
+              <li><a href="#key-values">6.2.7 Key Values Set</a></li>
+              <li><a href="#keyset-keyCode-charCode">6.2.8 Key values, keyCode, and charCode</a></li>
             </ul>
           </li>
         </ul>
       </li>
-      <li>
-        <a href="#extending_events">Appendix A: Extending Events</a>
+      <li><a href="#extending_events">Appendix A: Extending Events</a>
         <ul class="toc">
-          <li>
-            <a href="#extending_events-intro">A.1 Introduction</a>
-          </li>
-          <li>
-            <a href="#extending_events-Custom_Events">A.2 Custom Events</a>
-          </li>
-          <li>
-            <a href="#extending_events-Impl_Extensions">A.3 Implementation-Specific Extensions</a>
+          <li><a href="#extending_events-intro">A.1 Introduction</a></li>
+          <li><a href="#extending_events-Custom_Events">A.2 Custom Events</a></li>
+          <li><a href="#extending_events-Impl_Extensions">A.3 Implementation-Specific Extensions</a>
             <ul class="toc">
-              <li>
-                <a href="#extending_events-prefixes">A.3.1 Known Implementation-Specific Prefixes</a>
-              </li>
+              <li><a href="#extending_events-prefixes">A.3.1 Known Implementation-Specific Prefixes</a></li>
             </ul>
           </li>
         </ul>
       </li>
-      <li>
-        <a href="#security-considerations-Security">Appendix B: Security Considerations</a>
-      </li>
-      <li>
-        <a href="#changes-Changes">Appendix C: Changes</a>
+      <li><a href="#security-considerations-Security">Appendix B: Security Considerations</a></li>
+      <li><a href="#changes-Changes">Appendix C: Changes</a>
         <ul class="toc">
-          <li>
-            <a href="#changes-DOMEvents2to3Changes">C.1 Changes between DOM Level 2 Events and DOM Level 3 Events</a>
+          <li><a href="#changes-DOMEvents2to3Changes">C.1 Changes between DOM Level 2 Events and DOM Level 3 Events</a>
             <ul class="toc">
-              <li>
-                <a href="#changes-DOMEvents2to3Changes-flow">C.1.1 Changes to DOM Level 2 event flow</a>
-              </li>
-              <li>
-                <a href="#changes-DOMEvents2to3Changes-event-types">C.1.2 Changes to DOM Level 2 event types</a>
-              </li>
-              <li>
-                <a href="#changes-DOMLevel2to3Changes">C.1.3 Changes to DOM Level 2 Events interfaces</a>
-              </li>
-              <li>
-                <a href="#changes-DOMLevel3Addons">C.1.4 New Interfaces</a>
-              </li>
+              <li><a href="#changes-DOMEvents2to3Changes-flow">C.1.1 Changes to DOM Level 2 event flow</a></li>
+              <li><a href="#changes-DOMEvents2to3Changes-event-types">C.1.2 Changes to DOM Level 2 event types</a></li>
+              <li><a href="#changes-DOMLevel2to3Changes">C.1.3 Changes to DOM Level 2 Events interfaces</a></li>
+              <li><a href="#changes-DOMLevel3Addons">C.1.4 New Interfaces</a></li>
             </ul>
           </li>
-          <li>
-            <a href="#changes-drafts">C.2 Changes between different drafts of DOM Level 3 Events</a>
-          </li>
+          <li><a href="#changes-drafts">C.2 Changes between different drafts of DOM Level 3 Events</a></li>
         </ul>
       </li>
-      <li>
-        <a href="#acknowledgements-contributors">Appendix D: Acknowledgements</a>
+      <li><a href="#acknowledgements-contributors">Appendix D: Acknowledgements</a>
         <ul class="toc">
-          <li>
-            <a href="#acknowledgements-Productions">D.1 Production Systems</a>
-          </li>
+          <li><a href="#acknowledgements-Productions">D.1 Production Systems</a></li>
         </ul>
       </li>
-      <li>
-        <a href="#references-role-references" class="references">Appendix E: References</a>
+      <li><a href="#references-role-references" class="references">Appendix E: References</a>
         <ul class="toc">
-          <li>
-            <a href="#references-References-Normative">E.1 Normative References</a>
-          </li>
-          <li>
-            <a href="#references-References-Informative">E.2 Informative References</a>
-          </li>
+          <li><a href="#references-References-Normative">E.1 Normative References</a></li>
+          <li><a href="#references-References-Informative">E.2 Informative References</a></li>
         </ul>
       </li>
     </ul>
-    <div class="div1">
-      <h1 class="div1"><a id="dom-events" href="#dom-events">1. Document Object Model Events</a></h1>
-      <div class="div2">
-        <h2 class="div2"><a id="dom-events-overview" href="#dom-events-overview">1.1 Introduction</a></h2>
+    
+    
+    <div>
+      <h1><a id="dom-events" href="#dom-events">1. Document Object Model Events</a></h1>
+
+      
+      <div>
+        <h2><a id="dom-events-overview" href="#dom-events-overview">1.1 Introduction</a></h2>
+
         <p>DOM Events is designed with two main goals. The first goal is the design of an <a class="def" href="#glossary-event">event</a> system which allows registration of event listeners and describes event flow through a tree structure. Additionally, the specification will provide standard modules of events for user interface control and document mutation notifications, including defined contextual information for each of these event modules.</p>
         <p>The second goal of DOM Events is to provide a common subset of the current event systems used in <a class="def" href="#glossary-DOM-Level-0">DOM Level 0</a> browsers. This is intended to foster interoperability of existing scripts and content. It is not expected that this goal will be met with full backwards compatibility. However, the specification attempts to achieve this when possible.</p>
-        
-        <div class="div3">
-          <h3 class="div3"><a id="dom-events-conformance" href="#dom-events-conformance">1.2 Conformance</a></h3>
+        <div>
+          <h3><a id="dom-events-conformance" href="#dom-events-conformance">1.2 Conformance</a></h3>
+
           <p><strong>This section is normative.</strong></p>
-          
           <p>Within this specification, the key words 
             "MUST", 
             "MUST NOT",
@@ -441,86 +323,83 @@
             described in <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>
             [<a href="ref-RFC2119">RFC2119</a>].
             However, for readability, these words do not necessarily appear in uppercase in this specification.</p>
-          
-          
-          <p>This specification is to be understood in the context of the DOM Level 3 Core specification [<cite><a class="noxref normative" href="#references-DOMCore">DOM3 Core</a></cite>] and the general considerations for DOM implementations apply. For example, behavior in exceptional circumstances (such as when a <code>null</code> argument is passed when <code>null</code> was not expected) is discussed under <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-17189187"><em>DOMException</em></a>, and handling of <a class="def" href="#glossary-namespaceURI">namespace URIs</a> is discussed in <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations"><em>XML Namespaces</em></a>. For additional information about <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance"><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class="noxref normative" href="#references-DOMCore">DOM3 Core</a></cite>].</p>
-          
+          <p>This specification is to be understood in the context of the DOM Level 3 Core specification [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>] and the general considerations for DOM implementations apply. For example, behavior in exceptional circumstances (such as when a <code>null</code> argument is passed when <code>null</code> was not expected) is discussed under <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-17189187"><em>DOMException</em></a>, and handling of <a class="def" href="#glossary-namespaceURI">namespace URIs</a> is discussed in <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations"><em>XML Namespaces</em></a>. For additional information about <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance"><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>].</p>
           <p>This specification defines several classes of conformance for different <a class="def" href="#glossary-user-agent">user agents</a>, specifications, and authors:</p>
           <dl>
             <dt id="conf-interactive-ua">Web browsers and other dynamic or interactive <a class="def" href="#glossary-user-agent">user agents</a></dt>
             <dd>
-              <p>A dynamic or interactive <a class="def" href="#glossary-user-agent">user agent</a>, referred to here as a "browser" (be it a Web browser or other similar program), conforms to DOM Level 3 Events if it supports the Core module defined in [<cite><a class="noxref normative" href="#references-DOMCore">DOM3 Core</a></cite>], the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism, all the interfaces and events with their associated methods, attributes, and semantics defined in this specification which are not marked as <a class="def" href="#glossary-deprecated">deprecated</a><!--  or <a class="def" href="#glossary-obsolete">obsolete</a> -->, and the complete set of <a class="def" href="#glossary-character-value">character values</a> and <a class="def" href="#glossary-key-name">key names</a> in the <a href="#key-values">Key Values Set</a>, as well as all other normative requirements defined in this specification.  A conforming browser must <a class="def" href="#glossary-dispatch">dispatch</a> events appropriate to the given <a href="#events-Events-EventTarget">EventTarget</a> when the conditions defined for that <a class="def" href="#glossary-event-type">event type</a> have been met.</p>
-              
-              <p><span id="conform-arch">A browser conforms specifically to the DOM Level 3 Events Architecture if it implements the <a href="#dom-event-architecture">DOM Event Architecture</a> and <a href="#event-interfaces">Basic Event Interfaces</a>, regardless of its support for any other event interfaces or <a class="def" href="#glossary-event-type">event types</a> defined in this specification.</span>  <span id="conform-module">A browser conforms specifically to the DOM Level 3 Events Module if it implements the interfaces and its related <a class="def" href="#glossary-event-type">event types</a> specified in the <a href="#events-module">Events Module</a>, and to each event interface if it implements that interface and its related <a class="def" href="#glossary-event-type">event types</a>.</span></p>
-              
-              <p><span id="conform-script">A conforming browser must support scripting, declarative interactivity, or some other means of detecting and dispatching events in the manner described by this specification, and with the attributes specified for that <a class="def" href="#glossary-event-type">event type</a>.</span>  <span id="conform-declarative">A declarative browser may still conform to this specification if it does not directly support or expose the methods defined for the DOM Level 3 Events interfaces, but it should provide compatible functionality by other means.</span></p>
-              
+              <p>A dynamic or interactive <a class="def" href="#glossary-user-agent">user agent</a>, referred to here as a "browser" (be it a Web browser or other similar program), conforms to DOM Level 3 Events if it supports the Core module defined in [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>], the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism, all the interfaces and events with their associated methods, attributes, and semantics defined in this specification which are not marked as <a class="def" href="#glossary-deprecated">deprecated</a><!--  or <a class="def" href="#glossary-obsolete">obsolete</a> -->, and the complete set of <a class="def" href="#glossary-character-value">character values</a> and <a class="def" href="#glossary-key-name">key names</a> in the <a href="#key-values">Key Values Set</a>, as well as all other normative requirements defined in this specification.  A conforming browser must <a class="def" href="#glossary-dispatch">dispatch</a> events appropriate to the given <a href="#events-Events-EventTarget">EventTarget</a> when the conditions defined for that <a class="def" href="#glossary-event-type">event type</a> have been met.</p>
+              <p>
+                <span id="conform-arch">A browser conforms specifically to the DOM Level 3 Events Architecture if it implements the <a href="#dom-event-architecture">DOM Event Architecture</a> and <a href="#event-interfaces">Basic Event Interfaces</a>, regardless of its support for any other event interfaces or <a class="def" href="#glossary-event-type">event types</a> defined in this specification.</span>
+                <span id="conform-module">A browser conforms specifically to the DOM Level 3 Events Module if it implements the interfaces and its related <a class="def" href="#glossary-event-type">event types</a> specified in the <a href="#events-module">Events Module</a>, and to each event interface if it implements that interface and its related <a class="def" href="#glossary-event-type">event types</a>.</span>
+              </p>
+              <p>
+                <span id="conform-script">A conforming browser must support scripting, declarative interactivity, or some other means of detecting and dispatching events in the manner described by this specification, and with the attributes specified for that <a class="def" href="#glossary-event-type">event type</a>.</span>
+                <span id="conform-declarative">A declarative browser may still conform to this specification if it does not directly support or expose the methods defined for the DOM Level 3 Events interfaces, but it should provide compatible functionality by other means.</span>
+              </p>
               <p>In addition to meeting all other conformance criteria, a conforming browser may implement features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!--  or <a class="def" href="#glossary-obsolete">obsolete</a> -->, for backwards compatibility with existing content, but such implementation is discouraged.</p>
-              
               <p>A conforming browser may also support features not found in this specification, but which use the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism, interfaces, events, or other features defined in DOM Level 3 Events, and may implement additional interfaces and <a class="def" href="#glossary-event-type">event types</a> appropriate to that implementation.  Such features may be later standardized in future specifications.</p>
-
               <p>A browser which does not conform to all required portions of this specification must not claim conformance to DOM Level 3 Events.  Such an implementation which does conform to portions of this specification may claim conformance to those specific portions.</p>
-
-              <!-- //if we move to Web IDL, use something like the HTML5 wording:
+<!-- //if we move to Web IDL, use something like the HTML5 wording:
               <p>A conforming browser must also be conforming implementations of the IDL fragments in this specification, as described in the Web IDL specification. <a href="references.html#refsWEBIDL">[WEBIDL]</a></p> -->
             </dd>
-            
+
             <dt id="conf-author-tools">Authoring tools</dt>
             <dd>
               <p>An authoring tool conforms to DOM Level 3 Events if it produces content which uses the <a class="def" href="#glossary-event-type">event types</a> and <a href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification.  An authoring tool must not claim conformance to DOM Level 3 Events for content it produces which uses features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!--  or <a class="def" href="#glossary-obsolete">obsolete</a> --> in this specification.  A conforming authoring tool should provide to the author a means to use all <a class="def" href="#glossary-event-type">event types</a> and interfaces appropriate to all <a class="def" href="#glossary-host-language">host languages</a> in the content document being produced.</p>
             </dd>
-            
+
             <dt id="conf-authors">Authors and content</dt>
             <dd>
               <p>An author creates conforming DOM Level 3 Events content if that content uses the <a class="def" href="#glossary-event-type">event types</a> and <a href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification.  An author should not use features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!--  or <a class="def" href="#glossary-obsolete">obsolete</a> -->, but should rely instead upon replacement mechanisms defined in this specification and elsewhere.  Conforming content must use the semantics of the interfaces and <a class="def" href="#glossary-event-type">event types</a> as described in this specification, and must follow best practices as described in accessibility and internationalization guideline specifications. <i class="issue" id="issue-guidelines"><strong>Issue:</strong> define specific guideline specifications.</i></p>
             </dd>
-            
+
             <dt id="conf-specs">Specifications and host languages</dt>
             <dd>
               <p>A specification or <a class="def" href="#glossary-host-language">host language</a> conforms to DOM Level 3 Events if it references and uses the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism, interfaces, events, or other features defined in this specification, and does not extend these features in incompatible ways.  A specification or <a class="def" href="#glossary-host-language">host language</a> conforms specifically to the DOM Level 3 Events Architecture if it references and uses the <a href="#dom-event-architecture">DOM Event Architecture</a> and <a href="#event-interfaces">Basic Event Interfaces</a>, regardless of its use of any other event interfaces or <a class="def" href="#glossary-event-type">event types</a> defined in this specification.  A specification or <a class="def" href="#glossary-host-language">host language</a> conforms specifically to the DOM Level 3 Events Module if it references and uses the interfaces and its related <a class="def" href="#glossary-event-type">event types</a> specified in the <a href="#events-module">Events Module</a>, and to each event interface if it references and uses that interface and its related <a class="def" href="#glossary-event-type">event types</a>.  <span id="conf-extend">A conforming specification may define additional interfaces and <a class="def" href="#glossary-event-type">event types</a> appropriate to that specification, or may extend the DOM Level 3 Events interfaces and <a class="def" href="#glossary-event-type">event types</a> in a manner that does not contradict or conflict with the definitions of those interfaces and <a class="def" href="#glossary-event-type">event types</a> in this specification.  Events defined in conforming specifications must not have name conflicts with known languages, and should be defined in a manner that can be generalized for use with other specifications conforming to DOM Level 3 Events, as much as is possible.</span>  Specifications or <a class="def" href="#glossary-host-language">host languages</a> which reference DOM Level 3 Events should not use or recommend features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!--  or <a class="def" href="#glossary-obsolete">obsolete</a> -->, but should point instead to the indicated replacement for that the feature.  Editors of specifications referring to DOM Level 3 Events should consult with the Working Group responsible for this specification when using or extending the features defined in this specification.</p>
             </dd>
           </dl>
-
         </div>
 
-        <div class="div3">
-          <h3 class="div3"><a id="feature-detection" href="#feature-detection">1.3 Feature Detection</a></h3>
+        <div>
+          <h3><a id="feature-detection" href="#feature-detection">1.3 Feature Detection</a></h3>
+
           <p><em>This section is normative</em></p>
-          
-          <p>A conforming DOM Level 3 Events <a class="def" href="#glossary-user-agent">user agent</a> must implement the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method to allow authors to detect for support of features defined in this specification.  Refer to <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures"><em>DOM Features</em></a> in [<cite><a class="noxref normative" href="#references-DOMCore">DOM3 Core</a></cite>] for additional information on feature strings.</p>
-          
+          <p>A conforming DOM Level 3 Events <a class="def" href="#glossary-user-agent">user agent</a> must implement the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method to allow authors to detect for support of features defined in this specification.  Refer to <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures"><em>DOM Features</em></a> in [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>] for additional information on feature strings.</p>
           <p class="note"><strong>Note:</strong> The <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method has been of limited utility to authors in some instances, because of imprecision in conformance criteria in some specifications, and insufficient granularity of feature strings, leading to implementations misrepresenting the degree of support for a class of features.  This specification seeks to remedy that in the context of <a class="def" href="#glossary-user-agent">user agents</a> conforming to DOM Level 3 Events by providing discrete feature strings and clear guidelines for the circumstances under which a <a class="def" href="#glossary-user-agent">user agent</a> must or must not report in a positive manner when queried for support of the feature which that feature string represents.</p>
-
           <p>DOM Level 3 Events introduces compositional feature strings, which are base feature strings combined with extended feature strings, a new mechanism for testing support for each specific feature, rather than relying on modules-level feature strings.  A <a class="def" href="#glossary-user-agent">user agent</a> conforming to DOM Level 3 Events must also implement the following feature string convention for describing DOM3 Events feature support:</p>
-            
           <ul>
             <li id="base-feature-string">The primary base feature string for DOM Level 3 Events shall be "<code>Events</code>", with the optional version string "<code>3.0</code>", indicating that the <a class="def" href="#glossary-user-agent">user agent</a> supports the <a href="#conform-arch">DOM Level 3 Events Architecture</a> in the manner described in the appropriate conformance section.
               <ul>
-                <li><span class="assert must">Since DOM Level 3 Events is built on top of DOM Level 2 Events [<cite><a class="noxref normative" href="#references-DOM2Events">DOM2 Events</a></cite>], an implementation that returns <code>true</code> for <code>"Events"</code> and <code>"3.0"</code> shall also return <code>true</code> for the parameters <code>"Events"</code> and <code>"2.0"</code>.</span></li>
+                <li><span class="assert must">Since DOM Level 3 Events is built on top of DOM Level 2 Events [<cite><a class="normative" href="#references-DOM2Events">DOM2 Events</a></cite>], an implementation that returns <code>true</code> for <code>"Events"</code> and <code>"3.0"</code> shall also return <code>true</code> for the parameters <code>"Events"</code> and <code>"2.0"</code>.</span></li>
                 <li><span class="assert mustnot">If the version parameter is omitted, the <a class="def" href="#glossary-user-agent">user agent</a> must not differentiate between the <a href="#conform-arch">DOM Events Architecture</a> as described in DOM Level 3 Events and DOM Level 2 Events, in terms of reporting support for the features indicated by the base feature string.</span></li>
               </ul>
             </li>
             <li id="extended-feature-string">The extended feature string for each event type defined in DOM Level 3 Events shall be the base feature string "<code>Events</code>", followed by the period character ("."), followed by the name of that event type, with the optional version string "<code>3.0</code>", indicating that the <a class="def" href="#glossary-user-agent">user agent</a> supports that specific event type in the manner described in the appropriate <a href="#conform-module">conformance section</a>.  For example, the feature string for the <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event would be "<code>Events.textInput</code>", with the optional version string "<code>3.0</code>".
               <ul>
-                <li><span class="assert must">Because this specification does not retroactively define extended feature strings for DOM Level 2 Events, using the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method with extended feature strings with a version string "<code>2.0</code>" must return false.  <span class="warning"><strong>Warning!</strong> Because this mechanism for discrete feature strings was not defined in earlier DOM Events specifications, older user agents which support those specifications but not this one may report false negatives in terms of supporting particular features.  For example, a browser which supports the the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type as defined in DOM Level 2 Events, but does not support this specification, is likely to return <code>false</code> to the method call <code>document.implementation.hasFeature("Events.click", "")</code>.  The author should not take this for definitive proof that the implementation does not support the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, but rather that other means of testing are required in that instance.  This method is best used as a means to detect positive results, not negative ones.  However, it is expected that this will prove of sufficient utility in many cases to justify its use.</span></li>
+                <li><span class="assert must">Because this specification does not retroactively define extended feature strings for DOM Level 2 Events, using the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method with extended feature strings with a version string "<code>2.0</code>" must return false.</span><span class="warning"><strong>Warning!</strong> Because this mechanism for discrete feature strings was not defined in earlier DOM Events specifications, older user agents which support those specifications but not this one may report false negatives in terms of supporting particular features.  For example, a browser which supports the the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type as defined in DOM Level 2 Events, but does not support this specification, is likely to return <code>false</code> to the method call <code>document.implementation.hasFeature("Events.click", "")</code>.  The author should not take this for definitive proof that the implementation does not support the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, but rather that other means of testing are required in that instance.  This method is best used as a means to detect positive results, not negative ones.  However, it is expected that this will prove of sufficient utility in many cases to justify its use.</span></li>
                 <li><span class="assert must">A <a class="def" href="#glossary-user-agent">user agent</a> which supports an event type in a manner conforming to DOM Level 2 Events but not conforming to DOM Level 3 Events must not report a positive result to that extended feature string, regardless of the value of the version string.</span></li>
                 <li><span class="assert must">A specification or <a class="def" href="#glossary-host-language">host language</a> which <a href="#conf-specs">conforms</a> to DOM Level 3 Events, and which extends this specification in a manner consistent with the <a href="#conf-extend">extension conformance criteria</a>, may define extended feature strings for event types defined in that specification.  These extended feature strings may be used with the feature string "<code>Events</code>"; for example, support for the SVG <code>zoom</code> event type might be tested using the method call <code>document.implementation.hasFeature("Events.zoom", "")</code>.<!-- These extended feature strings may be used with the <a href="#base-feature-string">base feature string</a> of that specification, or with the feature string "<code>Events</code>"; for example, support for the SVG <code>zoom</code> event type might be tested using the method call <code>document.implementation.hasFeature("Events.zoom", "")</code> or the hypothetical <code>document.implementation.hasFeature("SVG.events.zoom", "")</code>. --></span></li>
               </ul>
             </li>
             <li>For backwards compatibility, each interface defined in DOM Level 3 Events also has a feature string, which may act as a base feature string or as an extended feature string.  If used as a base feature string, it must follow the conventions of the <a href="#base-feature-string">primary base feature string</a> (e.g., "<code>KeyboardEvent</code>", with the optional version string "<code>3.0</code>"); if used as an extended feature string, it must follow the conventions of the <a href="#extended-feature-string">extended feature strings for event types</a> (e.g., "<code>Events.KeyboardEvent</code>", with the optional version string "<code>3.0</code>").  In either case, the <a class="def" href="#glossary-user-agent">user agent</a> must only report a positive result if it supports that specific interface and all associated event types in the manner described in the appropriate <a href="#conform-module">conformance section</a>.  <span class="warning"><strong>Warning!</strong> because this is not as specific as testing for a specific event type and may thus be less likely to be accurate, authors are encouraged to use the feature strings for event types rather than interfaces.</span></li>
-          </ul>          
-                    
+          </ul>
           <p class="warning"><strong>Warning!</strong> This specification does not provide a means to guarantee that any given element of a <a class="def" href="#glossary-host-language">host language</a> is capable of generating or dispatching an event of any given <a class="def" href="#glossary-event-type">event type</a> (e.g., an HTML <code>'img'</code> element may not dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event), or what the attributes of that event will be beyond those defined in this specification (e.g., the host language may add attributes to the event object).  A  <a class="def" href="#glossary-host-language">host language</a> may provide a different means to do so, including its own relevant feature strings.</p>
-          
         </div>
-        
+
+
         <div>
-          <h3 class="div3"><a id="style-conventions" href="#style-conventions">1.4 Stylistic Conventions</a></h3>
+          <h3><a id="style-conventions" href="#style-conventions">1.4 Stylistic Conventions</a></h3>
+
           <p>The following stylistic conventions are followed in this specification:</p>
           <div style="margin-left: 3em;">
             <p class=""><code>'This is a keyword or value'</code></p>
-            <p><a class="eventtype"><code>This is an event type</code></a></p>
-            <p><a class="def">This is a link to a definition in the glossary</a></p>
+            <p>
+              <a class="eventtype"><code>This is an event type</code></a>
+            </p>
+            <p>
+              <a class="def">This is a link to a definition in the glossary</a>
+            </p>
             <p class="note">This is a note.</p>
             <p class="warning">This is a warning.  It is used on security notes and to mark <a class="def" href="#glossary-deprecated">deprecated</a><!--  or <a class="def" href="#glossary-obsolete">obsolete</a> --> features.</p>
             <p class="example">This is an example.</p>
@@ -529,17 +408,16 @@
             <p class="issue"><strong>Issue:</strong> This is an open issue.</p>
           </div>
           <p>Feedback on features at risk, new features, and open issues is especially appreciated.</p>
-          
           <p>In addition, certain terms are used in this specification with particular meanings.  The term "implementation" applies to a browser, authoring tool, or other <a class="def" href="#glossary-user-agent">user agent</a> that implements this specification, while an author is a person who writes script or code that takes advantage of the interfaces, methods, attributes, events, and other features described in this specification in order to make Web applications, and a user is the person who uses those Web applications in an implementation.</p>
         </div>
 <!-- div3 Conformance -->
       </div>
-      
 <!-- div1 glossary -->
-      <div class="div1" id="glossary-glossary">
-        <h1 class="glossary"><a id="glossary" href="#glossary">2. Glossary</a></h1>
+      <div id="glossary-glossary">
+        <h1 class="glossary">
+          <a id="glossary" href="#glossary">2. Glossary</a>
+        </h1>
         <p class="1st">Some of the following term definitions have been borrowed or modified from similar definitions in other W3C or standards documents. See the links within the definitions for more information.</p>
-        
         <dl id="glossary-list">
           <dt id="glossary-activation-behavior"><dfn>activation behavior</dfn></dt>
           <dd>The action taken when an <a class="def" href="#glossary-event">event</a>, typically initiated by users through an input device, causes an element to fulfill a defined task.  The task may be defined for that element by the <a class="def" href="#glossary-host-language">host language</a>, or by author-defined variables, or both.  The default task for any given element may be a generic action, or may be unique to that element.  For example, the activation behavior of an HTML or SVG <code>&lt;a&gt;</code> element shall be to cause the <a class="def" href="#glossary-user-agent">user agent</a> to traverse the link specified in the <code>href</code> attribute, with the further optional parameter of specifying the browsing context for the traversal (such as the current window or tab, a named window, or a new window); the activation behavior of an HTML <code>&lt;input&gt;</code> element with the <code>type</code> attribute value <code>submit</code> shall be to send the values of the form elements to an author-defined IRI by the author-defined HTTP method.  See <a href="#event-flow-activation">Activation triggers and behavior</a> for more details.</dd>
@@ -570,13 +448,13 @@
           </dd>
 
           <dt id="glossary-deprecated"><dfn>deprecated</dfn></dt>
-          <dd>Features marked as deprecated are included in the specification as reference to older implementations or specifications, but are optional and discouraged.  Only features which have existing or in-progress replacements shall be deprecated in this specification.  Implementations which do not already include support for the feature may implement deprecated features for reasons of backwards compatibility with existing content, but authors creating content should not use deprecated features, unless there is no other way to solve a use case.  Other specifications which reference this specification should not use deprecated features, but should point instead to the replacements of which the feature is deprecated in favor.  Features marked as deprecated in this specification are expected to be dropped from future specifications. <!-- Features marked as deprecated in this specification are expected to be <a class="def" href="#glossary-obsolete">obsolete</a> in future specifications. --></dd>
+          <dd>Features marked as deprecated are included in the specification as reference to older implementations or specifications, but are optional and discouraged.  Only features which have existing or in-progress replacements shall be deprecated in this specification.  Implementations which do not already include support for the feature may implement deprecated features for reasons of backwards compatibility with existing content, but authors creating content should not use deprecated features, unless there is no other way to solve a use case.  Other specifications which reference this specification should not use deprecated features, but should point instead to the replacements of which the feature is deprecated in favor.  Features marked as deprecated in this specification are expected to be dropped from future specifications.</dd>
 
           <dt id="glossary-dispatch"><dfn>dispatch</dfn></dt>
           <dd>To create an event with attributes and methods appropriate to its type and context, and propagate it through the DOM tree in the specified manner. Interchangeable with the term "<a href="#glossary-fire">fire</a>", e.g. "fire a 'click' event" or "dispatch a 'load' event".</dd>
 
           <dt id="glossary-document"><dfn>document</dfn></dt>
-          <dd>An object instantiating the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#i-Document" title="Document Object Model Core"><code>Document</code> interface</a> [<cite><a class="noxref normative" href="#references-DOMCore">DOM3 Core</a></cite>], representing the entire HTML or XML text document.  Conceptually, it is the root of the document tree, and provides the primary access to the document's data.</dd>
+          <dd>An object instantiating the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#i-Document" title="Document Object Model Core"><code>Document</code> interface</a> [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>], representing the entire HTML or XML text document.  Conceptually, it is the root of the document tree, and provides the primary access to the document's data.</dd>
 
           <dt id="glossary-DOM-application"><dfn>DOM application</dfn></dt>
           <dd>A DOM application is script or code, written by an author or automatically generated, which takes advantage of the interfaces, methods, attributes, events, and other features described in this specification in order to make dynamic or interactive content, such as Web applications, exposed to users in a <a class="def" href="#glossary-user-agent">user agent</a>.</dd>
@@ -595,19 +473,19 @@
 
           <dt id="glossary-event-type"><dfn>event type</dfn></dt>
           <dd>The name of an <a class="def" href="#glossary-event">event</a> object which defines particular trigger conditions, attributes, interfaces, and other characteristics which distinguish it from other event types.  For example, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type has different characteristics than the <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a> or <a class="eventtype" href="#event-type-load"><code>load</code></a> event types. The event type is exposed as the  the <a href="#events-event-type-type"><code class="interface-attribute">Event.type</code></a> attribute on the event object.  See <a href="#event-types">event types</a> for more details.  Also loosely referred to as 'event', such as the <em><a class="eventtype" href="#event-type-click"><code>click</code></a> event</em>.</dd>
-          
+
           <dt id="glossary-event-focus"><dfn>focus</dfn></dt>
           <dd>Focus is a special state of receptivity and concentration on an particular element or other <a class="def" href="#glossary-event-target">event target</a> within a document.  Each element has different behavior when focused, depending on its functionality, such as priming the element for activation (as for a button or hyperlink) or toggling state (as for a checkbox), receiving text input (as for a text form field), or copying selected text.  For more details, see <a href="#events-focusevent-doc-focus">Document Focus and Focus Context</a>.</dd>
-          
+
           <dt id="glossary-event-focus-ring"><dfn>focus ring</dfn></dt>
           <dd>A focus ring is a an ordered set of <a class="def" href="#glossary-event-focus">focus</a> targets within a document.  A <a class="def" href="#glossary-host-language">host language</a> may define one or more ways to determine the order of targets, such as document order, a numerical index defined per focus target, explicit pointers between focus targets, or a hybrid of different models.  Each document may contain multiple focus rings, or conditional focus rings.  Typically, for document-order or indexed focus rings, focus "wraps around" from the last focus target to the first.</dd>
-          
+
           <dt id="glossary-fire"><dfn>fire</dfn></dt>
           <dd>A synonym for <a href="#glossary-dispatch">dispatch</a>.</dd>
 
           <dt id="glossary-host-language"><dfn>host language</dfn></dt>
           <dd>Any language which integrates the features of another language or API specification, while normatively referencing the origin specification rather than redefining those features, and extending those features only in ways defined by the origin specification.  An origin specification typically is only intended to be implemented in the context of one or more host languages, not as a standalone language.  For example, XHTML, HTML, and SVG are host languages for DOM 3 Events, and they integrate and extend the objects and models defined in this specification.</dd>
-          
+
           <dt id="glossary-ime"><dfn>IME</dfn></dt>
           <dt id="glossary-input-method-editor"><dfn>input method editor</dfn></dt>
           <dd>An <em>input method editor</em> (IME), also known as a <em>front end processor</em>, is an application that performs the conversion between keystrokes and ideographs or other characters, usually by user-guided dictionary lookup, often used in East Asian languages (e.g. Chinese, Japanese, Korean).  An <a class="def" href="#glossary-ime">IME</a> may also be used for dictionary-based word completion, such as on mobile devices.  See <a href="#keyset-IME">Input Method Editors</a> for treatment of IMEs in this specification.  See also <a class="def" href="#glossary-text-composition-system">text composition system</a>.</dd>
@@ -616,21 +494,16 @@
           <dd>In the context of key values, a key name is a multi-character string (such as <code class="value">'Enter'</code>, <code class="value">'Tab'</code>, or <code class="value">'MediaNextTrack'</code>) which indicates a key.  Control keys, function keys, modifier keys, <a class="def" href="#glossary-dead-key">dead keys</a>, and others may only have a key name, without an equivalent <a class="def" href="#glossary-character-value">character value</a>.
             
             such as <code class="value">'Enter'</code> or <code>tab</code>, for control or <a class="def" href="#glossary-character-value">character value</a>, or certain symbols).</dd>
-          
+
           <dt id="glossary-localname"><dfn>local name</dfn></dt>
-          <dd>See local name in [<cite><a class="noxref informative" href="#references-Namespaces10">XML Namespaces 1.0</a></cite>].</dd>
-          
+          <dd>See local name in [<cite><a class="informative" href="#references-Namespaces10">XML Namespaces 1.0</a></cite>].</dd>
+
           <dt id="glossary-namespaceURI"><dfn>namespace URI</dfn></dt>
-          <dd>A <em>namespace URI</em> is a URI that identifies an XML namespace. This is called the namespace name in [<cite><a class="noxref informative" href="#references-Namespaces10">XML Namespaces 1.0</a></cite>]. See also sections 1.3.2 "<a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#baseURIs-Considerations"><em>DOM URIs</em></a>" and 1.3.3 "<a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations"><em>XML Namespaces</em></a>" regarding URIs and namespace URIs handling and comparison in the DOM APIs.</dd>
-          
-<!-- 
-          <dt id="glossary-obsolete"><dfn>obsolete</dfn></dt>
-          <dd>An obsolete feature is one which has previously been defined in a specification or implemented, but which is deemed to be no longer useful, problematic to implement interoperably or performantly, or even actively harmful, and are thus not formally defined in this specification.  Obsolete features may be implemented by <a class="def" href="#glossary-user-agent">user agents</a> (if they are not harmful), but should not be used by authors.  Obsolete features are not defined in this specification, but may be listed for historical purposes in the context of related features, and are marked as obsolete.</dd>
--->
+          <dd>A <em>namespace URI</em> is a URI that identifies an XML namespace. This is called the namespace name in [<cite><a class="informative" href="#references-Namespaces10">XML Namespaces 1.0</a></cite>]. See also sections 1.3.2 "<a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#baseURIs-Considerations"><em>DOM URIs</em></a>" and 1.3.3 "<a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations"><em>XML Namespaces</em></a>" regarding URIs and namespace URIs handling and comparison in the DOM APIs.</dd>
 
           <dt id="glossary-phase"><dfn>phase</dfn></dt>
           <dd>In the context of <a class="def" href="#glossary-event">events</a>, a phase is set of logical traversals from node to node along the DOM tree, from the <a class="def" href="#glossary-defaultView">defaultView</a> (window), to the <code>Document</code> object, <a class="def" href="#glossary-root-element">root element</a> down to the <a class="def" href="#glossary-event-target">event target</a> (<a class="def" href="#glossary-capture-phase">capture phase</a>), at the <a class="def" href="#glossary-event-target">event target</a> itself (<a class="def" href="#glossary-target-phase">target phase</a>), and back up to the same chain (<a class="def" href="#glossary-bubbling-phase">bubbling phase</a>).</dd>
-          
+
           <dt id="glossary-propagation-path"><dfn>propagation path</dfn></dt>
           <dd>The ordered set of <a class="def" href="#glossary-event-target">event targets</a> though which an <a class="def" href="#glossary-event">event</a> object will pass sequentially on the way to and back from the <a class="def" href="#glossary-proximal-event-target">proximal event target</a>.  As the event propagates, each <a class="def" href="#glossary-event-target">event target</a> in the propagation path shall in turn be set as the <a href="#events-event-type-currentTarget"><code>Event.currentTarget</code></a>.  The propagation path is initially comprised of one or more <a class="def" href="#glossary-event-phase">event phases</a> as defined by the <a class="def" href="#glossary-event-type">event type</a>, but may be interrupted.  Also known as an <em>event target chain</em>.</dd>
 
@@ -638,46 +511,47 @@
           <dd>The proximal event target is the object representing the <a class="def" href="#glossary-event-target">event target</a> to which an <a class="def" href="#glossary-event">event</a> is targeted using the DOM event flow.  The proximal event target is the value of the <a href="#events-event-type-target">Event.target</a> attribute.</dd>
 
           <dt id="glossary-qwerty"><dfn>QWERTY</dfn></dt>
-          <dd>QWERTY (pronounced "ˈkwɜrti") is a common keyboard layout, so named because the first five character keys on the top row of letter keys are Q, W, E, R, T, and Y.  There are many other popular keyboard layouts (including the Dvorak layout), most designed for localization or ergonomics.</dd>
+          <dd>QWERTY (pronounced "&#x2C8;kw&#x25C;rti") is a common keyboard layout, so named because the first five character keys on the top row of letter keys are Q, W, E, R, T, and Y.  There are many other popular keyboard layouts (including the Dvorak layout), most designed for localization or ergonomics.</dd>
 
           <dt id="glossary-roll"><dfn>roll</dfn></dt>
           <dd>A unit of <a class="def" href="#events-Events-WheelEvent-rotation">rotation</a> for an input device using the <a href="#events-wheelevents">WheelEvent</a> interface. On some devices this may be a finite physical step. On devices with smooth <a class="def" href="#events-Events-WheelEvent-rotation">rotation</a>, a <a class="def" href="#glossary-roll">roll</a> becomes the smallest reported amount of <a class="def" href="#events-Events-WheelEvent-rotation">rotation</a>.</dd>
-          
+
           <dt id="glossary-root-element"><dfn>root element</dfn></dt>
           <dd>The first element node of a document, of which all other elements are children; the document element.</dd>
 
           <dt id="events-Events-WheelEvent-rotation"><dfn>rotation</dfn></dt>
           <dd>An indication of incremental change on an input device using the <a href="#events-wheelevents">WheelEvent</a> interface. On some devices this may be a literal rotation of a wheel, while on others, it may be movement along a flat surface, or pressure on a particular button.</dd>
-          
+
           <dt id="glossary-text-composition-system"><dfn>text composition system</dfn></dt>
           <dd>A software component which interprets some form of alternate input, such as a <a class="def" href="#glossary-ime">input method editor</a>, a speech processor, or a handwriting recognition system, and converts it to text.</dd>
-          
+
           <dt id="glossary-target-phase"><dfn>target phase</dfn></dt>
           <dd>The process by which an <a class="def" href="#glossary-event">event</a> can be handled by the <a class="def" href="#glossary-proximal-event-target">proximal event target</a>.</dd>
-          
+
           <dt id="glossary-topmost-event-target"><dfn>topmost event target</dfn></dt>
           <dd>The <a class="def" href="#glossary-topmost-event-target">topmost event target</a> shall be the element highest in the rendering order which is capable of being an <a class="def" href="#glossary-event-target">event target</a>.  In this case, 'top' shall refer not to the position on the screen, but the logical order of the element in relation to other elements in drawing or stacking order on the z-axis (where the x-axis is the screen width and the y-axis is the screen height).  In HTML and CSS, or in SVG, this is controlled by the document order, as modified in HTML and CSS by the <code>'z-index'</code> property.  In some cases, such as when using some values of the SVG <code>'pointer-events'</code> property, the topmost element may not receive pointer events, in which case, the next element in z-index order which can receive pointer-events is the <a class="def" href="#glossary-topmost-event-target">topmost event target</a>.  Note that visibility of the element does not necessarily affect its ability to be the <a class="def" href="#glossary-topmost-event-target">topmost event target</a>, since an element which is hidden by use of the CSS <code>'visibility'</code> property can still receive pointer events (though not one with a <code>'display'</code> property of <code>none</code>), and the <a class="def" href="#glossary-topmost-event-target">topmost event target</a> may be completely obscured by another element which cannot receive pointer events.  Unless otherwise noted, there is only one <a class="def" href="#glossary-topmost-event-target">topmost event target</a> in any event.  For specific details regarding hit testing and stacking order, refer to the <a class="def" href="#glossary-host-language">host language</a>.</dd>
-          
+
           <dt id="glossary-tree"><dfn>tree</dfn></dt>
           <dd>A data structure that represents a document as a hierarchical set of nodes with child-parent-sibling relationships, i.e. each node having one or more possible ancestors (nodes higher in the hierarchy in a direct lineage), one or more possible descendants (nodes lower in the hierarchy in a direct lineage), and one or more possible peers (nodes of the same level in the hierarchy, with the same immediate ancestor).</dd>
-          
+
           <dt id="glossary-Unicode-character-categories"><dfn>Unicode character categories</dfn></dt>
           <dd>The Unicode character categories, a subset of the complete Unicode general categories, comprise the categories <abbr title="Letter, Lowercase">Ll</abbr>, <abbr title="Letter, Modifier">Lm</abbr>, <abbr title="Letter, Other">Lo</abbr>, <abbr title="Letter, Titlecase">Lt</abbr>, <abbr title="Letter, Uppercase">Lu</abbr>, <abbr title="Number, Decimal Digit">Nd</abbr>, <abbr title="Number, Letter">Nl</abbr>, <abbr title="Number, Other">No</abbr>, <abbr title="Punctuation, Connector">Pc</abbr>, <abbr title="Punctuation, Dash">Pd</abbr>, <abbr title="Punctuation, Close">Pe</abbr>, <abbr title="Punctuation, Final quote">Pf</abbr>, <abbr title="Punctuation, Initial quote">Pi</abbr>, <abbr title="Punctuation, Other">Po</abbr>, <abbr title="Punctuation, Open">Ps</abbr>, <abbr title="Symbol, Currency">Sc</abbr>, <abbr title="Symbol, Modifier">Sk</abbr>, <abbr title="Symbol, Math">Sm</abbr>, and <abbr title="Symbol, Other">So</abbr>.</dd>
-          
+
           <dt id="glossary-unicode-code-point"><dfn>Unicode code point</dfn></dt>
           <dd>A Unicode code point is a unique hexadecimal number signifying a character by its index in the Unicode codespace (or library of characters).  In the context of key values, a Unicode code point is expressed as a string in the format "\u" followed by a hexadecimal character index in the range <code>0000</code> to <code>10FFFF</code>, using at least four digits.  See also <a class="def charval" href="#glossary-character-value">character value</a>.</dd>
 
           <dt id="glossary-user-agent"><dfn>user agent</dfn></dt>
           <dd>A program, such as a browser or authoring tool, normally running on a client machine, which acts on a user's behalf in retrieving, interpreting, executing, presenting, or creating content conforming to a specification.  Users may act on the content using different user agents at different times, for different purposes.</dd>
-          
+
         </dl>
       </div>
 <!-- div1 glossary -->
-<!-- <span class='assert must'></span> -->
 <!-- div2 Events-overview -->
-      <h2 class="div2"><a id="dom-event-architecture" href="#dom-event-architecture">3. DOM Event Architecture</a></h2>
-      <div class="div2">
-        <h3 class="div2"><a id="event-flow" href="#event-flow">3.1 Event dispatch and DOM event flow</a></h3>
+      <h2><a id="dom-event-architecture" href="#dom-event-architecture">3. DOM Event Architecture</a></h2>
+
+      <div>
+        <h3><a id="event-flow" href="#event-flow">3.1 Event dispatch and DOM event flow</a></h3>
+
         <p>This section defines the event <a class="def" href="#glossary-dispatch">dispatch</a> mechanism of the event model defined in this specification. <span class="assert may">Applications may dispatch event objects using the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method</span>, and <span class="assert must">implementations must dispatch event objects as if through this method.</span> The behavior of this method depends on the <em>event flow</em> associated with the underlying object. An event flow describes how event objects <em>propagate</em> through a data structure. As an example, when an event object is dispatched to an element in an XML document, the object propagates through parts of the document, as determined by the DOM event flow which is defined at the end of this section.</p>
         <div class="figure" style="text-align: center">
           <object type="image/svg+xml" data="images/eventflow.svg" width="520" height="560">
@@ -723,13 +597,14 @@
         <p><span class="assert must">As the final step of the event dispatch, for reasons of backwards compatibility, the implementation must reset the event object's internal-propagation and default-action-prevention states.</span> This ensures that an event object may be properly dispatched multiple times while also allowing to prevent the event objects propagation or <a class="def" href="#glossary-default-action">default actions</a> prior to the event dispatch.</p>
         <p>In the production of the <a class="def" href="#glossary-propagation-path">propagation path</a>, if the <a class="def" href="#glossary-defaultView">defaultView</a> implements the <a href="#events-Events-EventTarget">EventTarget</a> interface, the event propagates from <a class="def" href="#glossary-defaultView">defaultView</a> to the <code>document</code> object during the <a class="def" href="#glossary-capture-phase">capture phase</a>, and from the <code>document</code> object to the <a class="def" href="#glossary-defaultView">defaultView</a> during the <a class="def" href="#glossary-bubbling-phase">bubble phase</a>.  
           <span class="note"><strong>Note:</strong> for legacy reasons, the <a class="eventtype" href="#event-type-load"><code>load</code></a> event does not propagate to the <a class="def" href="#glossary-defaultView">defaultView</a> in HTML implementations.</span></p>
-        <p>The model defined above must be applied regardless of the specific event flow associated with an event target. Each event flow must define how the propagation path shall be determined and which event phases are supported. The <em>DOM event flow</em> is an application of this model: the propagation path for a <code>Node</code> object shall be determined by its <code>Node.parentNode</code> chain, and if applicable, the document's containing <a class="def" href="#glossary-defaultView">defaultView</a>; all events accomplish the capture and target phases; whether an event accomplishes the bubble phase shall be defined individually for each <a class="def" href="#glossary-event-type">event type</a>. An alternate application of this model can be found in [<cite><a class="noxref informative" href="#references-DOMLS">DOM3 Load and Save</a></cite>].</p>
+        <p>The model defined above must be applied regardless of the specific event flow associated with an event target. Each event flow must define how the propagation path shall be determined and which event phases are supported. The <em>DOM event flow</em> is an application of this model: the propagation path for a <code>Node</code> object shall be determined by its <code>Node.parentNode</code> chain, and if applicable, the document's containing <a class="def" href="#glossary-defaultView">defaultView</a>; all events accomplish the capture and target phases; whether an event accomplishes the bubble phase shall be defined individually for each <a class="def" href="#glossary-event-type">event type</a>. An alternate application of this model can be found in [<cite><a class="informative" href="#references-DOMLS">DOM3 Load and Save</a></cite>].</p>
         <p>Implementations of the DOM event model must be reentrant. Event listeners may perform actions that cause additional events to be dispatched. Such events are handled in a synchronous manner, the event propagation that causes the event listener to be triggered must resume only after the event dispatch of the new event is completed.</p>
       </div>
 <!-- div2 Events-flow -->
-      <div class="div2">
-        <h3 class="div2"><a id="event-flow-default-cancel" href="#event-flow-default-cancel">3.2 Default actions and cancelable events</a></h3>
-        <p>Event objects may have one or more <a class="def" href="#glossary-default-action">default actions</a> associated with them.  These are actions the implementation must perform in combination with the dispatch of the event object.  An example is the [<cite><a class="noxref informative" href="#references-HTML5">HTML5</a></cite>] form element. When the user submits the form (e.g. by pressing on a submit button), the event <a class="eventtype" href="#event-type-submit"><code>submit</code></a> shall be dispatched to the element and the <a class="def" href="#glossary-default-action">default action</a> for this <a class="def" href="#glossary-event-type">event type</a> shall be generally to send a request to a Web server with the parameters from the form.</p>
+      <div>
+        <h3><a id="event-flow-default-cancel" href="#event-flow-default-cancel">3.2 Default actions and cancelable events</a></h3>
+
+        <p>Event objects may have one or more <a class="def" href="#glossary-default-action">default actions</a> associated with them.  These are actions the implementation must perform in combination with the dispatch of the event object.  An example is the [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] form element. When the user submits the form (e.g. by pressing on a submit button), the event <a class="eventtype" href="#event-type-submit"><code>submit</code></a> shall be dispatched to the element and the <a class="def" href="#glossary-default-action">default action</a> for this <a class="def" href="#glossary-event-type">event type</a> shall be generally to send a request to a Web server with the parameters from the form.</p>
         <p><a class="def" href="#glossary-default-action">Default actions</a> should be performed after the event dispatch has been completed, but in exceptional cases also immediately before the event is dispatched.</p>
         <span class="issue"><strong>Issue:</strong> insert example here: &lt;input type="checkbox"&gt;'s .checked handling comes to mind.
         .checked is changed just before 'click' event is dispatched, and if
@@ -737,95 +612,75 @@
         <p id="events-dt-cancelable-event">Some event objects are <em>cancelable</em>, meaning the <a class="def" href="#glossary-default-action">default action</a> can be prevented from occuring, or, if the <a class="def" href="#glossary-default-action">default action</a> is carried out before the dispatch, its effect may be reversed. Whether an event object is cancelable shall be indicated by the <a href="#events-event-type-canCancel"><code>Event.cancelable</code></a> attribute. Event listeners can cancel <a class="def" href="#glossary-default-action">default actions</a> of cancelable event objects by invoking the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method, and determine whether an event has been canceled through the <a href="#events-event-type-defaultPrevented"><code>Event.defaultPrevented</code></a> attribute while the object is being dispatched, or from the return value of the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method for event objects dispatched by the <a class="def" href="#glossary-DOM-application">DOM application</a> itself.</p>
         <p>This specification does not offer features to programatically query if an event object has any <a class="def" href="#glossary-default-action">default action</a> associated with it, or to associate new <a class="def" href="#glossary-default-action">default actions</a> to an event object. Other specifications may define what default actions, if any, are associated with certain event objects. Further, implementations may associate <a class="def" href="#glossary-default-action">default actions</a> with events as necessary and appropriate for that implementation. As an example, one implementation may scroll a document view by a certain amount as <a class="def" href="#glossary-default-action">default action</a> of a mouse wheel event, while another implementation may instead zoom the document as its <a class="def" href="#glossary-default-action">default action</a> for a mouse wheel event.</p>
       </div>
-      
-      
-
-<!-- div2 sync-async -->
-      <div class="div2">
-        <h3 class="div2"><a id="sync-async" href="#sync-async">3.3 Synchronous and asynchronous events</a></h3>
-        <p>Events may occur either synchronously (<em>"sync"</em>) or asynchronously (<em>"async"</em>).</p> 
-        <p>Events which are synchronous must be treated as if they are in a virtual queue in a first-in-first-out model, ordered by sequence of temporal occurrence, with respect to other events, to changes in the DOM, and to user interaction.  Each event in this virtual queue must be delayed until the previous event has completed its propagation behavior, or been canceled.  Some sync events are driven by a specific device or process, such as mouse button events; these events are governed by the event order algorithms defined for that set of events, and a user agent must dispatch these events in the defined order.</p>
-        
-        <p class="example" id="example-sync"><strong>Example:</strong> A user double-clicks a passage of text to select a word, then presses the <code class="value">'delete'</code> key to erase the word, triggering the following synchronous sequence of events: <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, <a class="eventtype" href="#event-type-click"><code>click</code></a>, <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, <a class="eventtype" href="#event-type-click"><code>click</code></a>, <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>, <a class="eventtype" href="#event-type-select"><code>select</code></a>, <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>, <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a>.  Each of these events are fired in the sequence initiated by the user's actions.</p>
-        
-        <p>Events which are asynchronous may be dispatched as the results of the action are completed, with no relation to other events, to other changes in the DOM, nor to user interaction.</p>
-
-        <p class="example" id="example-async"><strong>Example:</strong> <i class="note"><strong>To Do:</strong> Create good example of async events.</i></p>
-      </div>
-
-
 <!-- div2 sync-async -->
-      <div class="div2">
-        <h3 class="div2"><a id="trusted-events" href="#trusted-events">3.4 Trusted events</a></h3>
+      <div>
+        <h3><a id="sync-async" href="#sync-async">3.3 Synchronous and asynchronous events</a></h3>
+
+        <p>Events may occur either synchronously (<em>"sync"</em>) or asynchronously (<em>"async"</em>).</p>
+        <p>Events which are synchronous must be treated as if they are in a virtual queue in a first-in-first-out model, ordered by sequence of temporal occurrence, with respect to other events, to changes in the DOM, and to user interaction.  Each event in this virtual queue must be delayed until the previous event has completed its propagation behavior, or been canceled.  Some sync events are driven by a specific device or process, such as mouse button events; these events are governed by the event order algorithms defined for that set of events, and a user agent must dispatch these events in the defined order.</p>
+        <p class="example" id="example-sync"><strong>Example:</strong> A user double-clicks a passage of text to select a word, then presses the <code class="value">'delete'</code> key to erase the word, triggering the following synchronous sequence of events: <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, <a class="eventtype" href="#event-type-click"><code>click</code></a>, <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, <a class="eventtype" href="#event-type-click"><code>click</code></a>, <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>, <a class="eventtype" href="#event-type-select"><code>select</code></a>, <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>, <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a>.  Each of these events are fired in the sequence initiated by the user's actions.</p>
+        <p>Events which are asynchronous may be dispatched as the results of the action are completed, with no relation to other events, to other changes in the DOM, nor to user interaction.</p>
+        <p class="example" id="example-async">
+          <strong>Example:</strong>
+          <i class="note"><strong>To Do:</strong> Create good example of async events.</i>
+        </p>
+      </div>
+<!-- div2 sync-async -->
+      <div>
+        <h3><a id="trusted-events" href="#trusted-events">3.4 Trusted events</a></h3>
+
         <p>Events which are generated by the user agent, either as a result of user interaction, or as a direct result of changes to the DOM, are trusted by the user agent with privileges that are not afforded to events generated by script through the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> method or the <a href="#events-Events-CustomEvent">CustomEvent</a> interface, modified using the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method, or dispatched via the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method.  The <a href="#events-event-type-trusted"><code>trusted</code></a> attribute of trusted events has a value of <code>true</code>, while untrusted events have a <a href="#events-event-type-trusted"><code>trusted</code></a> attribute value of <code>false</code>.</p>
-        
         <p>Most untrusted events should not trigger <a class="def" href="#glossary-default-action">default actions</a>, with the exception of <a class="eventtype" href="#event-type-click"><code>click</code></a> or <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> events which have been synthesized and are managed by the <a class="def" href="#glossary-user-agent">user agents</a> event as the <a class="def" href="#glossary-default-action">default action</a> of an <a class="def" href="#glossary-activation-trigger">activation trigger</a> (see <a href="#event-flow-activation">Activation triggers and behavior</a> for more details); these <a class="def" href="#glossary-user-agent">user-agent</a>-managed synthesized events have a have a <a href="#events-event-type-trusted"><code>trusted</code></a> attribute value of <code>false</code>, but still initiate any <a class="def" href="#glossary-default-action">default actions</a>.  All other untrusted events must behave as if the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method had been called on that event.</p>
-        
         <p>For security reasons, a <a class="def" href="#glossary-host-language">host language</a> should not define events which are not cancelable (see <a href="#event-flow-default-cancel">Default actions and cancelable events</a>), but also have <a class="def" href="#glossary-default-action">default actions</a>, since these <a class="def" href="#glossary-default-action">default actions</a> may be initiated by untrusted events.</p>
-        
         <p class="issue" id="issue-trusted-nonui"><strong>Issue:</strong> Are all non-script-generated events trusted events, or are only user-interaction-based events trusted events?</p>
-        
-
       </div>
-
-
-
-
-
-
 <!-- div2 Events-flow-cancelation -->
-      <div class="div2">
-        <h3 class="div2"><a id="event-flow-activation" href="#event-flow-activation">3.5 Activation triggers and behavior</a></h3>
-        <p class="warning" id="activation-deprecated"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> is deprecated in this specification.</p>
+      <div>
+        <h3><a id="event-flow-activation" href="#event-flow-activation">3.5 Activation triggers and behavior</a></h3>
+
+        <p class="warning" id="activation-deprecated"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a><a class="def" href="#glossary-event-type">event type</a> is deprecated in this specification.</p>
         <p>Certain <a class="def" href="#glossary-proximal-event-target">proximal event targets</a> (such as a link or button element) may have associated <a class="def" href="#glossary-activation-behavior">activation behavior</a> (such a following a link) that implementations perform in response to an <em><a class="def" href="#glossary-activation-trigger">activation trigger</a></em> (such as clicking a link).</p>
-        
-        <p>A <a class="def" href="#glossary-host-language">host language</a> should indicate which, if any, elements have activation behavior, describe appropriate <a class="def" href="#glossary-activation-trigger">activation triggers</a>, and define the result of that activation behavior.  An implementation which supports a <a class="def" href="#glossary-host-language">host language</a> should initiate these <a class="def" href="#glossary-activation-behavior">activation behavior</a> when the associated <a class="def" href="#glossary-activation-trigger">activation trigger</a> occurs.</p>  
-        
+        <p>A <a class="def" href="#glossary-host-language">host language</a> should indicate which, if any, elements have activation behavior, describe appropriate <a class="def" href="#glossary-activation-trigger">activation triggers</a>, and define the result of that activation behavior.  An implementation which supports a <a class="def" href="#glossary-host-language">host language</a> should initiate these <a class="def" href="#glossary-activation-behavior">activation behavior</a> when the associated <a class="def" href="#glossary-activation-trigger">activation trigger</a> occurs.</p>
         <p class="example" id="example-activation"><strong>Example:</strong> Both HTML and SVG have an <code class="element">a</code> element which indicates a link.  Relevant <a class="def" href="#glossary-activation-trigger">activation triggers</a> for an <code class="element">a</code> element are a <a class="eventtype" href="#event-type-click"><code>click</code></a> event on the text or image  content of the <code class="element">a</code> element, or a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event with a <a href="#events-Events-KeyboardEvent-key">key</a> attribute value of <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> key when the <code class="element">a</code> element has focus.  The activation behavior for an <code class="element">a</code> element is normally to change the content of the window to the content of the new document, in the case of external links, or to reposition the current document relative to the new anchor, in the case of internal links.</p>
-        
-        <p>An <a class="def" href="#glossary-activation-trigger">activation trigger</a> is a user action or an event which indicates to the implementation that an activation behavior should be initiated.  User-initiated <a class="def" href="#glossary-activation-trigger">activation triggers</a> include clicking a mouse button on an activatable element, pressing the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> key when an activatable element has focus, or pressing a key that is somehow linked to an activatable element (a "hotkey" or "access key") even when that element does not have focus.  Event-based <a class="def" href="#glossary-activation-trigger">activation triggers</a> may include timer-based events that activate an element at a certain clock time or after a certain time period has elapsed, progress events after a certain action has been completed, or many other condition-based or state-based events.</p>        
-
-        <p>In some cases, a <a class="def" href="#glossary-host-language">host language</a> may define attributes or even attribute values which add to or change the native <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a> of an element.  For example, ARIA [<cite><a class="noxref informative" href="#ref-ARIA">ARIA</a></cite>] defines values for the <code class="attr">role</code> attribute that add semantics to the element to which it is applied, for purposes of enhanced accessibility.  In such cases, if the <a class="def" href="#glossary-host-language">host language</a> does not explicitly define the <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a>, the author must provide the mechanics of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> (via an event listener) or <a class="def" href="#glossary-activation-behavior">activation behavior</a> (such as calling an ECMAScript function) for that element when applying that attributes or attribute value.</p>
-
+        <p>An <a class="def" href="#glossary-activation-trigger">activation trigger</a> is a user action or an event which indicates to the implementation that an activation behavior should be initiated.  User-initiated <a class="def" href="#glossary-activation-trigger">activation triggers</a> include clicking a mouse button on an activatable element, pressing the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> key when an activatable element has focus, or pressing a key that is somehow linked to an activatable element (a "hotkey" or "access key") even when that element does not have focus.  Event-based <a class="def" href="#glossary-activation-trigger">activation triggers</a> may include timer-based events that activate an element at a certain clock time or after a certain time period has elapsed, progress events after a certain action has been completed, or many other condition-based or state-based events.</p>
+        <p>In some cases, a <a class="def" href="#glossary-host-language">host language</a> may define attributes or even attribute values which add to or change the native <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a> of an element.  For example, ARIA [<cite><a class="informative" href="#ref-ARIA">ARIA</a></cite>] defines values for the <code class="attr">role</code> attribute that add semantics to the element to which it is applied, for purposes of enhanced accessibility.  In such cases, if the <a class="def" href="#glossary-host-language">host language</a> does not explicitly define the <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a>, the author must provide the mechanics of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> (via an event listener) or <a class="def" href="#glossary-activation-behavior">activation behavior</a> (such as calling an ECMAScript function) for that element when applying that attributes or attribute value.</p>
         <p>If the instance of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> is not an event of <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> (that is, when it does not result from a user activating a button or link using a mouse or equivalent pointing device), the implementation must synthesize and dispatch an event of <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> as one of the <a class="def" href="#glossary-default-action">default actions</a> of that <a class="def" href="#glossary-activation-trigger">activation trigger</a>.  Context information of such a <a class="eventtype" href="#event-type-click"><code>click</code></a> event is implementation dependent, but for historical purposes, the interface for the <a class="eventtype" href="#event-type-click"><code>click</code></a> event must be the <a href="#events-Events-MouseEvent"><code>MouseEvent interface</code></a>, regardless of the actual device used to activate the element.  Preventing the <a class="def" href="#glossary-default-action">default action</a> of the <a class="def" href="#glossary-activation-trigger">activation trigger</a>, such as with the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a>, must stop the initiation of the <a class="def" href="#glossary-activation-behavior">activation behavior</a>.</p>
-        
         <p class="example" id="example-activation-click"><strong>Example:</strong>  When a user activates a hyperlink using a keyboard, such as by focusing the hyperlink element and pressing the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> or <a href="#key-Space"><code class="value keyname">'Space'</code></a> key, a <a class="eventtype" href="#event-type-click"><code>click</code></a> event would be dispatched as the <a class="def" href="#glossary-default-action">default action</a> of the respective <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event.</p>
-
-      <p>Implementations must dispatch the synthesized <a class="eventtype" href="#event-type-click"><code>click</code></a> event as described above even if they do not normally dispatch such an event (e.g. when activation is requested by a voice command, since this specification does not address <a class="def" href="#glossary-event-type">event types</a> for voice input).</p>
-
-      <p class="note" id="application-dependent-activation"><strong>Note:</strong> The activation of an event target is device dependent but is also application dependent, e.g. a link in a document can be activated using a mouse click or a mouse double click.</p>
-
-      <p>Implementations which support the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> should also dispatch a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event as a <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-click"><code>click</code></a> event which is associated with an <a class="def" href="#glossary-activation-trigger">activation trigger</a>.  However, such implementations should only initiate the associated <a class="def" href="#glossary-activation-behavior">activation behavior</a> once for any given occurrence of an <a class="def" href="#glossary-activation-trigger">activation trigger</a>.</p>   
-        
-        <p class="example" id="example-activation-DOMActivate"><strong>Example:</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> is required to be supported for XForms [<cite><a class="noxref informative" href="#ref-xforms">XFORMS</a></cite>], which is intended for implementation within a <a class="def" href="#glossary-host-language">host language</a>.  In a scenario where a plugin or script-based implementation of XForms is intended for installation in a native implementation of this specification which does not support the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a>, the XForms <a class="def" href="#glossary-user-agent">user agent</a> must synthesize and dispatch its own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> events based on the appropriate <a class="def" href="#glossary-activation-trigger">activation triggers</a>.  Thus, when a <a class="eventtype" href="#event-type-click"><code>click</code></a> event is dispatched by the DOM Level 3 Events <a class="def" href="#glossary-user-agent">user agent</a>, the XForms <a class="def" href="#glossary-user-agent">user agent</a> must determine whether to synthesize a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event with the same relevant properties as a <a class="def" href="#glossary-default-action">default action</a> of that <a class="eventtype" href="#event-type-click"><code>click</code></a> event; appropriate cues may be whether the <a class="eventtype" href="#event-type-click"><code>click</code></a> event is <a href="#trusted-events">trusted</a>, or whether its <a class="def" href="#glossary-proximal-event-target">proximal event target</a> has a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event listener registered.</p>
-      
-      <p class="note" id="authors-activation"><strong>Note:</strong>  Authors should not rely upon the interoperable support of <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> in many <a class="def" href="#glossary-user-agent">user agents</a>.  Thus, authors may use the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> whenever they wish to make or react to an <a class="def" href="#glossary-activation-trigger">activation trigger</a>, but should use the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> for more accessible behavior instead, due to wider implementation.</p>
-
-
-      <h4 class="div3 needswork"><a id="events-activation-event-order" href="#events-activation-event-order">3.5.1 Activation Event Order</a></h4>
-      <p>Activation triggers and behavior can be defined in part by the events which are dispatched in a set order relative to one another.  The following is the typical sequence of events for an element activated by a pointing device (with only pertinent events listed):</p>
-      <ol>
-        <li><a class="eventtype" href="#event-type-click"><code>click</code></a></li>
-        <li><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> (<a class="def" href="#glossary-default-action">default action</a>, if supported by the <a class="def" href="#glossary-user-agent">user agent</a>; synthesized; <code>trusted="false"</code>)</li>
-        <li><em>All other <a class="def" href="#glossary-default-action">default actions</a>, including the <a class="def" href="#glossary-activation-behavior">activation behavior</a></em></li>
-      </ol>
-
-      <p>The following is the typical sequence of events when a focused element is activated by a key event (with only pertinent events listed):</p>
-      <ol>
-        <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (must be a key which can activate the element, such as the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> or <a href="#key-Space"><code class="value keyname">'Space'</code></a> key, or the element is not activated)</li>
-        <li><a class="eventtype" href="#event-type-click"><code>click</code></a> (<a class="def" href="#glossary-default-action">default action</a>; synthesized; <code>trusted="false"</code>)</li>
-        <li><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> (<a class="def" href="#glossary-default-action">default action</a>, if supported by the <a class="def" href="#glossary-user-agent">user agent</a>; synthesized; <code>trusted="false"</code>)</li>
-        <li><em>All other <a class="def" href="#glossary-default-action">default actions</a>, including the <a class="def" href="#glossary-activation-behavior">activation behavior</a></em></li>
-      </ol>
-        
-       <!--
+        <p>Implementations must dispatch the synthesized <a class="eventtype" href="#event-type-click"><code>click</code></a> event as described above even if they do not normally dispatch such an event (e.g. when activation is requested by a voice command, since this specification does not address <a class="def" href="#glossary-event-type">event types</a> for voice input).</p>
+        <p class="note" id="application-dependent-activation"><strong>Note:</strong> The activation of an event target is device dependent but is also application dependent, e.g. a link in a document can be activated using a mouse click or a mouse double click.</p>
+        <p>Implementations which support the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> should also dispatch a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event as a <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-click"><code>click</code></a> event which is associated with an <a class="def" href="#glossary-activation-trigger">activation trigger</a>.  However, such implementations should only initiate the associated <a class="def" href="#glossary-activation-behavior">activation behavior</a> once for any given occurrence of an <a class="def" href="#glossary-activation-trigger">activation trigger</a>.</p>
+        <p class="example" id="example-activation-DOMActivate"><strong>Example:</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a><a class="def" href="#glossary-event-type">event type</a> is required to be supported for XForms [<cite><a class="informative" href="#ref-xforms">XFORMS</a></cite>], which is intended for implementation within a <a class="def" href="#glossary-host-language">host language</a>.  In a scenario where a plugin or script-based implementation of XForms is intended for installation in a native implementation of this specification which does not support the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a><a class="def" href="#glossary-event-type">event type</a>, the XForms <a class="def" href="#glossary-user-agent">user agent</a> must synthesize and dispatch its own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> events based on the appropriate <a class="def" href="#glossary-activation-trigger">activation triggers</a>.  Thus, when a <a class="eventtype" href="#event-type-click"><code>click</code></a> event is dispatched by the DOM Level 3 Events <a class="def" href="#glossary-user-agent">user agent</a>, the XForms <a class="def" href="#glossary-user-agent">user agent</a> must determine whether to synthesize a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event with the same relevant properties as a <a class="def" href="#glossary-default-action">default action</a> of that <a class="eventtype" href="#event-type-click"><code>click</code></a> event; appropriate cues may be whether the <a class="eventtype" href="#event-type-click"><code>click</code></a> event is <a href="#trusted-events">trusted</a>, or whether its <a class="def" href="#glossary-proximal-event-target">proximal event target</a> has a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event listener registered.</p>
+        <p class="note" id="authors-activation"><strong>Note:</strong>  Authors should not rely upon the interoperable support of <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> in many <a class="def" href="#glossary-user-agent">user agents</a>.  Thus, authors may use the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a><a class="def" href="#glossary-event-type">event type</a> whenever they wish to make or react to an <a class="def" href="#glossary-activation-trigger">activation trigger</a>, but should use the <a class="eventtype" href="#event-type-click"><code>click</code></a><a class="def" href="#glossary-event-type">event type</a> for more accessible behavior instead, due to wider implementation.</p>
+        <h4 class="needswork">
+          <a id="events-activation-event-order" href="#events-activation-event-order">3.5.1 Activation Event Order</a>
+        </h4>
+        <p>Activation triggers and behavior can be defined in part by the events which are dispatched in a set order relative to one another.  The following is the typical sequence of events for an element activated by a pointing device (with only pertinent events listed):</p>
+        <ol>
+          <li>
+            <a class="eventtype" href="#event-type-click"><code>click</code></a>
+          </li>
+          <li><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> (<a class="def" href="#glossary-default-action">default action</a>, if supported by the <a class="def" href="#glossary-user-agent">user agent</a>; synthesized; <code>trusted="false"</code>)</li>
+          <li>
+            <em>All other <a class="def" href="#glossary-default-action">default actions</a>, including the <a class="def" href="#glossary-activation-behavior">activation behavior</a></em>
+          </li>
+        </ol>
+        <p>The following is the typical sequence of events when a focused element is activated by a key event (with only pertinent events listed):</p>
+        <ol>
+          <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (must be a key which can activate the element, such as the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> or <a href="#key-Space"><code class="value keyname">'Space'</code></a> key, or the element is not activated)</li>
+          <li><a class="eventtype" href="#event-type-click"><code>click</code></a> (<a class="def" href="#glossary-default-action">default action</a>; synthesized; <code>trusted="false"</code>)</li>
+          <li><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> (<a class="def" href="#glossary-default-action">default action</a>, if supported by the <a class="def" href="#glossary-user-agent">user agent</a>; synthesized; <code>trusted="false"</code>)</li>
+          <li>
+            <em>All other <a class="def" href="#glossary-default-action">default actions</a>, including the <a class="def" href="#glossary-activation-behavior">activation behavior</a></em>
+          </li>
+        </ol>
+<!--
        <p>Implementations could react to an event before dispatching it
        	  and do changes on the display and the DOM tree. In such case,
        	  if a DOM attribute is changed before the event is fired,
        	  cancelling the device event type will also reverse the
        	  change. A good example is the attribute
        	  <code>HTMLInputElement.checked</code>: As described in 
-       	  [<a class="noxref normative" href="references.html#DOM2HTML">DOM Level 2 HTML</a>], 
+       	  [<a class="normative" href="references.html#DOM2HTML">DOM Level 2 HTML</a>], 
        	  the value of this property may be changed before the dispatch of the event;
        	  the user clicks on the radio button, the radio button is being
        	  checked (or unchecked) on the display, the attribute
@@ -838,13 +693,13 @@
        	  back to its original value.
        	</p>
        -->
-       
       </div>
 <!-- div2 Events-flow-activation -->
-
 <!-- div2 Event-interfaces -->
-      <div class="div2">
-        <h2 class="div2"><a id="event-interfaces" href="#event-interfaces">4. Basic Event Interfaces</a></h2>
+      <div>
+        <h2><a id="event-interfaces" href="#event-interfaces">4. Basic Event Interfaces</a></h2>
+
+
         <p>The interfaces described in this section are fundamental to DOM Level 3 Events and must always be supported by the implementation. Together they define the feature Events 3.0.</p>
         <p>The event types defined in this specification derive from these basic interfaces, and shall inherit all of the attributes, methods, and constants of the interfaces they derive from.  Event types defined in other specifications may similarly inherit from these basic interfaces or other interfaces defined in this specification, or may define their own interfaces.  The following chart describes the inheritance structure of interfaces defined in this specification.</p>
         <div class="figure" style="text-align: center">
@@ -855,7 +710,9 @@
             <em>Figure 2: graphical representation of the DOM3 Events interface inheritance</em>
           </p>
         </div>
-        <h3 class="div2"><a id="interface-Event" href="#interface-Event">4.1 Interface Event</a></h3>
+        <h3><a id="interface-Event" href="#interface-Event">4.1 Interface Event</a></h3>
+
+
         <dl>
           <dt><strong>Interface <em><a id="events-Events-Event">Event</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
           <dd>
@@ -896,52 +753,43 @@
   // Introduced in DOM Level 3:
   readonly attribute boolean         <a href="#events-event-type-trusted">trusted</a>;
 };
-</pre>
+                  </pre>
                 </div>
                 <br />
               </dd>
+
               <dt>
                 <strong>Definition group <em><a id="events-event-type-eventPhaseType">PhaseType</a></em></strong>
               </dt>
               <dd>
                 <p>An integer indicating which phase of the event flow is being processed as defined in <a href="#event-flow">Event dispatch and DOM event flow</a>.</p>
                 <dl>
-                  <dt>
-                    <strong>Defined Constants</strong>
-                  </dt>
+                  <dt><strong>Defined Constants</strong></dt>
                   <dd>
                     <dl>
-                      <dt>
-                        <a id="events-AT_TARGET">
-                          <code class="constant-name">AT_TARGET</code>
-                        </a>
-                      </dt>
+                      <dt><a id="events-AT_TARGET"><code class="constant-name">AT_TARGET</code></a></dt>
                       <dd>The current event is in the <a class="def" href="#glossary-target-phase">target phase</a>, i.e. it is being evaluated at the <a class="def" href="#glossary-proximal-event-target">proximal event target</a>.</dd>
-                      <dt>
-                        <a id="events-BUBBLING_PHASE">
-                          <code class="constant-name">BUBBLING_PHASE</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-BUBBLING_PHASE"><code class="constant-name">BUBBLING_PHASE</code></a></dt>
                       <dd>The current event phase is the <a class="def" href="#glossary-bubbling-phase">bubbling phase</a>.</dd>
-                      <dt>
-                        <a id="events-CAPTURING_PHASE">
-                          <code class="constant-name">CAPTURING_PHASE</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-CAPTURING_PHASE"><code class="constant-name">CAPTURING_PHASE</code></a></dt>
                       <dd>The current event phase is the <a class="def" href="#glossary-capture-phase">capture phase</a>.</dd>
+
                     </dl>
                   </dd>
                 </dl>
               </dd>
-              <dt>
-                <strong>Attributes</strong>
-              </dt>
+
+              <dt><strong>Attributes</strong></dt>
               <dd>
                 <dl>
                   <dt><code class="attribute-name"><a id="events-event-type-canBubble">bubbles</a></code> of type <code>boolean</code>, readonly</dt>
                   <dd>Used to indicate whether or not an event is a bubbling event. If the event can bubble the value shall be <code>true</code>, otherwise the value shall be <code>false</code>.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-event-type-canCancel">cancelable</a></code> of type <code>boolean</code>, readonly</dt>
                   <dd>Used to indicate whether or not an event can have its <a class="def" href="#glossary-default-action">default action</a> prevented (see also <a href="#event-flow-default-cancel">Default actions and cancelable events</a>). If the <a class="def" href="#glossary-default-action">default action</a> can be prevented the value shall be <code>true</code>, otherwise the value shall be <code>false</code>.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-event-type-currentTarget">currentTarget</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
                   <dd>Used to indicate the <a href="#events-Events-EventTarget"><code>EventTarget</code></a> whose <a href="#events-Events-EventListener"><code>EventListeners</code></a> are currently being processed. This is particularly useful during the capture and bubbling phases. When used with the <a href="#event-flow">Event dispatch and DOM event flow</a>, this attribute contains the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> or a target ancestor.<br /></dd>
 
@@ -953,17 +801,20 @@
 
                   <dt><code class="attribute-name"><a id="events-event-type-eventPhase">eventPhase</a></code> of type <code>unsigned short</code>, readonly</dt>
                   <dd>Used to indicate which phase of event flow is currently being accomplished.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-event-type-target">target</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
                   <dd>Used to indicate the <a class="def" href="#glossary-event-target">event target</a>. This attribute contains the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> when used with the <a href="#event-flow">Event dispatch and DOM event flow</a>.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-event-type-timeStamp">timeStamp</a></code> of type <code>DOMTimeStamp</code>, readonly</dt>
                   <dd>Used to specify the time at which the event was created in milliseconds relative to 1970-01-01T00:00:00Z. Due to the fact that some systems may not provide this information the value of <code>timeStamp</code> may be not available for all events. When not available, the value shall be <code>0</code>.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-event-type-type">type</a></code> of type <code>DOMString</code>, readonly</dt>
                   <dd>The name of the event type. The name must be a <code>DOMString</code>.  <a href="#conf-specs">Specifications that define events</a>, <a href="#conf-authors">authors</a>, and <a href="#conf-author-tools">authoring tools</a> must use case-sensitive event type names that do not contain whitespace characters.<br /></dd>
+
                 </dl>
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -977,13 +828,18 @@
 This method sets the <a href="#events-event-type-type"><code>Event.type</code></a> attribute to <code>eventTypeArg</code>.
                       <p class="warning" id="warning-initEvent-untrusted"><strong>Warning!</strong>  For security reasons, events modified using <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>.  See <a href="#trusted-events">trusted events</a> for more details.</p>
 
-                      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">eventTypeArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-event-type-type"><code>Event.type</code></a>, the name of the event type.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-event-type-canBubble"><code>Event.bubbles</code></a>. This parameter overrides the intrinsic bubbling behavior of the event.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-event-type-canCancel"><code>Event.cancelable</code></a>. This parameter overrides the intrinsic cancelable behavior of the event.<br /></dd></dl></div></div>
+                      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">eventTypeArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-event-type-type"><code>Event.type</code></a>, the name of the event type.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-event-type-canBubble"><code>Event.bubbles</code></a>. This parameter overrides the intrinsic bubbling behavior of the event.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-event-type-canCancel"><code>Event.cancelable</code></a>. This parameter overrides the intrinsic cancelable behavior of the event.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
                   </dd>
+
                   <dt>
                     <code class="method-name">
                       <a id="events-event-type-preventDefault">preventDefault</a>
@@ -993,31 +849,41 @@
                     <div class="method">When this method is evoked, the event must be canceled, meaning any <a class="def" href="#glossary-default-action">default actions</a> normally taken by the implementation as a result of the event must not occur (see also <a href="#event-flow-default-cancel">Default actions and cancelable events</a>). Calling this method for a non-cancelable event shall have no effect.  If an event has more than one <a class="def" href="#glossary-default-action">default action</a>, each cancelable <a class="def" href="#glossary-default-action">default action</a> must be canceled.
 <p class="note"><strong>Note:</strong> This method does not stop the event propagation; use <a href="#events-event-type-stopPropagation"><code>Event.stopPropagation()</code></a> or <a href="#events-event-type-stopImmediatePropagation"><code>Event.stopImmediatePropagation()</code></a> for that effect.</p>
                       <div><strong>No Parameters</strong></div>
+
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
                   </dd>
+
                   <dt><code class="method-name"><a id="events-event-type-stopImmediatePropagation">stopImmediatePropagation</a></code> introduced in <strong class="since">DOM Level 3</strong></dt>
                   <dd>
-                    <div class="method">Prevents other event listeners from being triggered and, unlike <a href="#events-event-type-stopPropagation"><code>Event.stopPropagation()</code></a> its effect shall be immediate . Once it has been called, further calls to this method have no additional effect.
-<p class="note"><strong>Note:</strong> This method does not prevent the <a class="def" href="#glossary-default-action">default action</a> from being invoked; use <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> for that effect.</p>
+                    <div class="method">
+                      Prevents other event listeners from being triggered and, unlike <a href="#events-event-type-stopPropagation"><code>Event.stopPropagation()</code></a> its effect shall be immediate . Once it has been called, further calls to this method have no additional effect.
+                      <p class="note"><strong>Note:</strong> This method does not prevent the <a class="def" href="#glossary-default-action">default action</a> from being invoked; use <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> for that effect.</p>
                       <div><strong>No Parameters</strong></div>
+
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
                   </dd>
+
                   <dt>
                     <code class="method-name">
                       <a id="events-event-type-stopPropagation">stopPropagation</a>
                     </code>
                   </dt>
                   <dd>
-                    <div class="method">Prevents other event listeners from being triggered but its effect shall be deferred until all event listeners attached on the <a href="#events-event-type-currentTarget"><code>Event.currentTarget</code></a> have been triggered . Once it has been called, further calls to this method have no additional effect.
-<p class="note"><strong>Note:</strong> This method does not prevent the <a class="def" href="#glossary-default-action">default action</a> from being invoked; use <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> for that effect.</p>
+                    <div class="method">
+                      Prevents other event listeners from being triggered but its effect shall be deferred until all event listeners attached on the <a href="#events-event-type-currentTarget"><code>Event.currentTarget</code></a> have been triggered . Once it has been called, further calls to this method have no additional effect.
+                      <p class="note"><strong>Note:</strong> This method does not prevent the <a class="def" href="#glossary-default-action">default action</a> from being invoked; use <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> for that effect.</p>
                       <div><strong>No Parameters</strong></div>
+
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
@@ -1027,7 +893,8 @@
             </dl>
           </dd>
         </dl>
-        <h3 class="div2"><a id="interface-CustomEvent" href="#interface-CustomEvent">4.2 Interface CustomEvent</a></h3>
+        <h3><a id="interface-CustomEvent" href="#interface-CustomEvent">4.2 Interface CustomEvent</a></h3>
+
         <dl>
           <dt><strong>Interface <em><a id="events-Events-CustomEvent">CustomEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
           <dd>
@@ -1050,22 +917,21 @@
                                      in boolean cancelableArg, 
                                      in DOMObject detailArg);
 };
-</pre>
+                  </pre>
                 </div>
                 <br />
               </dd>
-              <dt>
-                <strong>Attributes</strong>
-              </dt>
+
+              <dt><strong>Attributes</strong></dt>
               <dd>
                 <dl>
                   <dt><code class="attribute-name"><a id="events-Events-CustomEvent-detail">detail</a></code> of type <code>DOMObject</code>, readonly</dt>
                   <dd>Specifies some detail information about the <a href="#events-Events-Event"><code>Event</code></a>.<br /></dd>
+
                 </dl>
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -1075,9 +941,14 @@
                   </dt>
                   <dd>
                     <div class="method">Initializes attributes of a <code>CustomEvent</code> object. This method has the same behavior as <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a>.
-        <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">detailArg</code> of type <code>DOMObject</code></dt><dd>Specifies <a href="#events-Events-CustomEvent-detail"><code>CustomEvent.detail</code></a>. This value may be <code>null</code>.<br /></dd></dl></div></div>
+                      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">detailArg</code> of type <code>DOMObject</code></dt><dd>Specifies <a href="#events-Events-CustomEvent-detail"><code>CustomEvent.detail</code></a>. This value may be <code>null</code>.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
@@ -1087,14 +958,16 @@
             </dl>
           </dd>
         </dl>
-        <h3 class="div2"><a id="interface-EventTarget" href="#interface-EventTarget">4.3 Interface EventTarget</a></h3>
+        
+        
+        <h3><a id="interface-EventTarget" href="#interface-EventTarget">4.3 Interface EventTarget</a></h3>
+
         <dl>
           <dt><strong>Interface <em><a id="events-Events-EventTarget">EventTarget</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
           <dd>
             <p>The <code>EventTarget</code> interface shall be implemented by all the objects which could be <a class="def" href="#glossary-event-target">event targets</a> in an implementation which supports an event flow. The interface allows registration and removal of event listeners, and dispatch of events to an event target.</p>
             <p>When used with the DOM event flow, this interface must be implemented by all <a class="def" href="#glossary-proximal-event-target">proximal event targets</a> and target ancestors, i.e. all DOM <code>Nodes</code> of the tree support this interface when the implementation conforms to DOM Level 3 Events and, therefore, this interface can be obtained by using binding-specific casting methods on an instance of the <code>Node</code> interface.</p>
-            <p>Invoking <code>addEventListener</code> or <code>addEventListenerNS</code> repeatedly on the same <code>EventTarget</code> with the same values for the parameters <code>type</code>, <code>listener</code>, and <code>useCapture</code> has no effect. Doing so does not cause the <a href="#events-Events-EventListener"><code>EventListener</code></a> to be called more than once and does not cause a change in the triggering order.</p>
-            
+            <p>Invoking <code>addEventListener</code> repeatedly on the same <code>EventTarget</code> with the same values for the parameters <code>type</code>, <code>listener</code>, and <code>useCapture</code> has no effect. Doing so does not cause the <a href="#events-Events-EventListener"><code>EventListener</code></a> to be called more than once and does not cause a change in the triggering order.</p>
             <dl>
               <dt>
                 <br />
@@ -1117,13 +990,12 @@
                                    DOMException);
                                    
 };
-</pre>
+                  </pre>
                 </div>
                 <br />
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -1133,32 +1005,25 @@
                   </dt>
                   <dd>
                     <div class="method">Registers an event listener, depending on the <code>useCapture</code> parameter, on the capture phase of the DOM event flow or its target and bubbling phases.
-                      <div class="parameters"><strong>Parameters</strong>
-                        <div class="paramtable">
-                          <dl>
-                            <dt><code class="parameter-name">type</code> of type <code>DOMString</code></dt>
-                            <dd>Specifies the <a href="#events-event-type-type"><code>Event.type</code></a> associated with the event for which the user is registering.<br /></dd>
-                            <dt><code class="parameter-name">listener</code> of type <a href="#events-Events-EventListener"><code>EventListener</code></a></dt>
-                            <dd>The <code>listener</code> parameter takes an object implemented by the user which implements the <a href="#events-Events-EventListener"><code>EventListener</code></a> interface and contains the method to be called when the event occurs.<br /></dd>
-                            <dt><code class="parameter-name">useCapture</code> of type <code>boolean</code></dt>
-                            <dd>If true, <code>useCapture</code> indicates that the user wishes to add the event listener for the <a class="def" href="#glossary-capture-phase">capture phase</a> only, i.e. this event listener will not be triggered during the <a class="def" href="#glossary-target-phase">target</a> and <a class="def" href="#glossary-bubbling-phase">bubbling</a> phases. If <code>false</code>, the event listener must only be triggered during the target and bubbling phases.<br /></dd>
-                          </dl>
-                        </div>
-                      </div>
+                      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">type</code> of type <code>DOMString</code></dt><dd>Specifies the <a href="#events-event-type-type"><code>Event.type</code></a> associated with the event for which the user is registering.<br /></dd>
+<dt><code class="parameter-name">listener</code> of type <a href="#events-Events-EventListener"><code>EventListener</code></a></dt><dd>The <code>listener</code> parameter takes an object implemented by the user which implements the <a href="#events-Events-EventListener"><code>EventListener</code></a> interface and contains the method to be called when the event occurs.<br /></dd>
+<dt><code class="parameter-name">useCapture</code> of type <code>boolean</code></dt><dd>If true, <code>useCapture</code> indicates that the user wishes to add the event listener for the <a class="def" href="#glossary-capture-phase">capture phase</a> only, i.e. this event listener will not be triggered during the <a class="def" href="#glossary-target-phase">target</a> and <a class="def" href="#glossary-bubbling-phase">bubbling</a> phases. If <code>false</code>, the event listener must only be triggered during the target and bubbling phases.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
                   </dd>
-                  
-                  
-                <dt><code class="method-name"><a id="events-Events-EventTarget-dispatchEvent">dispatchEvent</a></code> modified in <strong class="version">DOM Level 3</strong></dt>
+
+                  <dt><code class="method-name"><a id="events-Events-EventTarget-dispatchEvent">dispatchEvent</a></code> modified in <strong class="version">DOM Level 3</strong></dt>
                   <dd>
                     <div class="method">Dispatches an event into the implementation's event model. The <a class="def" href="#glossary-event-target">event target</a> of the event shall be the <code>EventTarget</code> object on which <code>dispatchEvent</code> is called.
-                      <p class="warning" id="warning-initEvent-untrusted"><strong>Warning!</strong>  For security reasons, events dispatched using <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>.  See <a href="#trusted-events">trusted events</a> for more details.</p>
+                      <p class="warning" id="warning-dispatchEvent-untrusted"><strong>Warning!</strong>  For security reasons, events dispatched using <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>.  See <a href="#trusted-events">trusted events</a> for more details.</p>
                       
-<div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">evt</code> of type <a href="#events-Events-Event"><code>Event</code></a></dt><dd>The event to be dispatched.<br /></dd></dl></div></div>
+<div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">evt</code> of type <a href="#events-Events-Event"><code>Event</code></a></dt><dd>The event to be dispatched.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div class="return"><strong>Return Value</strong><div class="returntable"><table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr><td><p><code>boolean</code></p></td><td><p>Indicates whether any of the listeners which handled the event called <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a>. If <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> was called the returned value shall be <code>false</code>, else it shall be <code>true</code>.</p></td></tr></table></div></div>
                       <!-- return -->
@@ -1166,6 +1031,7 @@
                       <!-- exceptions --></div>
 <!-- method -->
                   </dd>
+
                   <dt>
                     <code class="method-name">
                       <a id="events-Events-EventTarget-removeEventListener">removeEventListener</a>
@@ -1173,20 +1039,13 @@
                   </dt>
                   <dd>
                     <div class="method">Removes an event listener. Calling <code>removeEventListener</code> with arguments which do not identify any currently registered <a href="#events-Events-EventListener"><code>EventListener</code></a> on the <code>EventTarget</code> has no effect. 
-                      <div class="parameters"><strong>Parameters</strong>
-                        <div class="paramtable">
-                          <dl>
-                            <dt><code class="parameter-name">type</code> of type <code>DOMString</code></dt>
-                            <dd>Specifies the <a href="#events-event-type-type"><code>Event.type</code></a> for which the user registered the event listener.<br /></dd>
-                            <dt><code class="parameter-name">listener</code> of type <a href="#events-Events-EventListener"><code>EventListener</code></a></dt>
-                            <dd>The <a href="#events-Events-EventListener"><code>EventListener</code></a> to be removed.<br /></dd>
-                            <dt><code class="parameter-name">useCapture</code> of type <code>boolean</code></dt>
-                            <dd>Specifies whether the <a href="#events-Events-EventListener"><code>EventListener</code></a> being removed was registered for the capture phase or not. If a listener was registered twice, once for the capture phase and once for the target and bubbling phases, each must be removed separately. Removal of an event listener registered for the capture phase does not affect the same event listener registered for the target and bubbling phases, and vice versa.<br /></dd>
-                          </dl>
-                        </div>
-                      </div>
+                      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">type</code> of type <code>DOMString</code></dt><dd>Specifies the <a href="#events-event-type-type"><code>Event.type</code></a> for which the user registered the event listener.<br /></dd>
+<dt><code class="parameter-name">listener</code> of type <a href="#events-Events-EventListener"><code>EventListener</code></a></dt><dd>The <a href="#events-Events-EventListener"><code>EventListener</code></a> to be removed.<br /></dd>
+<dt><code class="parameter-name">useCapture</code> of type <code>boolean</code></dt><dd>Specifies whether the <a href="#events-Events-EventListener"><code>EventListener</code></a> being removed was registered for the capture phase or not. If a listener was registered twice, once for the capture phase and once for the target and bubbling phases, each must be removed separately. Removal of an event listener registered for the capture phase does not affect the same event listener registered for the target and bubbling phases, and vice versa.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
@@ -1196,7 +1055,10 @@
             </dl>
           </dd>
         </dl>
-        <h3 class="div2"><a id="interface-EventListener" href="#interface-EventListener">4.4 Interface EventListener</a></h3>
+        
+        
+        <h3><a id="interface-EventListener" href="#interface-EventListener">4.4 Interface EventListener</a></h3>
+
         <dl>
           <dt><strong>Interface <em><a id="events-Events-EventListener">EventListener</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
           <dd>
@@ -1220,13 +1082,12 @@
 interface <a href="#events-Events-EventListener">EventListener</a> {
   void               <a href="#events-Events-EventListener-handleEvent">handleEvent</a>(in <a href="#events-Events-Event">Event</a> evt);
 };
-</pre>
+                  </pre>
                 </div>
                 <br />
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -1236,9 +1097,11 @@
                   </dt>
                   <dd>
                     <div class="method">This method shall be called whenever an event occurs of the event type for which the <code>EventListener</code> interface was registered.
-<div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">evt</code> of type <a href="#events-Events-Event"><code>Event</code></a></dt><dd>The <a href="#events-Events-Event"><code>Event</code></a> contains contextual information about the <a class="def" href="#glossary-event">event</a>.<br /></dd></dl></div></div>
+<div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">evt</code> of type <a href="#events-Events-Event"><code>Event</code></a></dt><dd>The <a href="#events-Events-Event"><code>Event</code></a> contains contextual information about the <a class="def" href="#glossary-event">event</a>.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
@@ -1247,6 +1110,7 @@
               </dd>
             </dl>
           </dd>
+
           <dt><strong>Exception <em><a id="events-Events-EventException">EventException</a></em></strong> introduced in <strong class="version">DOM Level 2</strong></dt>
           <dd>
             <p>Event operations may throw an <a href="#events-Events-EventException"><code>EventException</code></a> as specified in their method descriptions.</p>
@@ -1266,29 +1130,26 @@
 const unsigned short      <a href="#events-UNSPECIFIED_EVENT_TYPE_ERR">UNSPECIFIED_EVENT_TYPE_ERR</a>     = 0;
 // Introduced in DOM Level 3:
 const unsigned short      <a href="#events-DISPATCH_REQUEST_ERR">DISPATCH_REQUEST_ERR</a>           = 1;
-</pre>
+                  </pre>
                 </div>
                 <br />
               </dd>
+
               <dt>
                 <strong>Definition group <em><a id="events-Events-EventException-EventExceptionCode">EventExceptionCode</a></em></strong>
               </dt>
               <dd>
                 <p>An integer indicating the type of error generated.</p>
                 <dl>
-                  <dt>
-                    <strong>Defined Constants</strong>
-                  </dt>
+                  <dt><strong>Defined Constants</strong></dt>
                   <dd>
                     <dl>
                       <dt><a id="events-DISPATCH_REQUEST_ERR"><code class="constant-name">DISPATCH_REQUEST_ERR</code></a>, introduced in <strong class="version">DOM Level 3</strong>.</dt>
                       <dd>If the <a href="#events-Events-Event"><code>Event</code></a> object is already dispatched in the tree.</dd>
-                      <dt>
-                        <a id="events-UNSPECIFIED_EVENT_TYPE_ERR">
-                          <code class="constant-name">UNSPECIFIED_EVENT_TYPE_ERR</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-UNSPECIFIED_EVENT_TYPE_ERR"><code class="constant-name">UNSPECIFIED_EVENT_TYPE_ERR</code></a></dt>
                       <dd>If the <a href="#events-event-type-type"><code>Event.type</code></a> was not specified by initializing the event before the method was called. Specification of the <a href="#events-event-type-type"><code>Event.type</code></a> as <code>null</code> or an empty string must also trigger this exception.</dd>
+
                     </dl>
                   </dd>
                 </dl>
@@ -1296,8 +1157,11 @@
             </dl>
           </dd>
         </dl>
-        <div class="div3">
-          <h3 class="div2"><a id="interface-DocumentEvent" href="#interface-DocumentEvent">4.5 Interface DocumentEvent</a></h3>
+        
+        
+        <div>
+          <h3><a id="interface-DocumentEvent" href="#interface-DocumentEvent">4.5 Interface DocumentEvent</a></h3>
+
           <dl>
             <dt><strong>Interface <em><a id="events-Events-DocumentEvent">DocumentEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
             <dd>
@@ -1323,60 +1187,44 @@
   // Modified in DOM Level 3:
   <a href="#events-Events-Event">Event</a>              <a href="#events-Events-DocumentEvent-createEvent">createEvent</a>(in DOMString eventInterface)
                                         raises(DOMException);
-<div class="proposal">
+<!-- <div class="proposal"> -->
   // Introduced in DOM Level 3:
   DOMString            <a href="#events-Events-DocumentEvent-convertKeyValue">convertKeyValue</a>(in DOMString keyArg,
                                  in unsigned long KeyValueFormatArg);
-</div>
+<!-- </div> -->
 };
-</pre>
+                    </pre>
                   </div>
                   <br />
                 </dd>
-                
+
                 <dt>
                   <strong>Definition group <em><a id="events-Events-DocumentEvent-KeyValueFormatCode">KeyValueFormatCode</a></em></strong>
                 </dt>
                 <dd>
                   <p>This set of constants shall be used to indicate the format to which the key value must be converted.</p>
                   <dl>
-                    <dt>
-                      <strong>Defined Constants</strong>
-                    </dt>
+                    <dt><strong>Defined Constants</strong></dt>
                     <dd>
                       <dl>
-                        <dt>
-                          <a id="events-DOM_KEY_FORMAT_CHARACTER">
-                            <code class="constant-name">DOM_KEY_FORMAT_CHARACTER</code>
-                          </a>
-                        </dt>
+                        <dt><a id="events-DOM_KEY_FORMAT_CHARACTER"><code class="constant-name">DOM_KEY_FORMAT_CHARACTER</code></a></dt>
                         <dd>The format to which the key value must be converted is a <a class="def" href="#glossary-character-value">character value</a>.</dd>
-                        <dt>
-                          <a id="events-DOM_KEY_FORMAT_NAME">
-                            <code class="constant-name">DOM_KEY_FORMAT_NAME</code>
-                          </a>
-                        </dt>
+
+                        <dt><a id="events-DOM_KEY_FORMAT_NAME"><code class="constant-name">DOM_KEY_FORMAT_NAME</code></a></dt>
                         <dd>The format to which the key value must be converted is a key name (as from the <a href="#key-values">Key Values Set</a>).</dd>
-                        <dt>
-                          <a id="events-DOM_KEY_FORMAT_UNICODE">
-                            <code class="constant-name">DOM_KEY_FORMAT_UNICODE</code>
-                          </a>
-                        </dt>
+
+                        <dt><a id="events-DOM_KEY_FORMAT_UNICODE"><code class="constant-name">DOM_KEY_FORMAT_UNICODE</code></a></dt>
                         <dd>The format to which the key value must be converted is a bare <a class="def" href="#glossary-unicode-code-point">Unicode code point</a>.</dd>
-                        <dt>
-                          <a id="events-DOM_KEY_FORMAT_ENTITY">
-                            <code class="constant-name">DOM_KEY_FORMAT_ENTITY</code>
-                          </a>
-                        </dt>
-                        <dd>The format to which the key value must be converted is a numberic entity reference representing the <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> for that character.  For example, the <a class="def" href="#glossary-character-value">character value</a> <code class="value">'é'</code> must be converted to the entity string <code class="value">'&amp;#xE9;'</code>.</dd>                        
+
+                        <dt><a id="events-DOM_KEY_FORMAT_ENTITY"><code class="constant-name">DOM_KEY_FORMAT_ENTITY</code></a></dt>
+                        <dd>The format to which the key value must be converted is a numberic entity reference representing the <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> for that character.  For example, the <a class="def" href="#glossary-character-value">character value</a> <code class="value">'&#xE9;'</code> must be converted to the entity string <code class="value">'&amp;#xE9;'</code>.</dd>
+
                       </dl>
                     </dd>
                   </dl>
                 </dd>
 
-                <dt>
-                  <strong>Methods</strong>
-                </dt>
+                <dt><strong>Methods</strong></dt>
                 <dd>
                   <dl>
                     <dt>
@@ -1386,29 +1234,8 @@
                     </dt>
                     <dd>
                       <div class="method">Creates an event object of the type specified.
-                        <div class="parameters">
-                          <strong>Parameters</strong>
-                          <div class="paramtable">
-                            <dl>
-                              <dt><code class="parameter-name">eventInterface</code> of type <code>DOMString</code></dt>
-                              <dd>
-                                
-                                <p>The <code>eventInterface</code> parameter specifies the name of the DOM Events interface to be supported by the created event object, e.g. <code>"Event"</code>, <code>"MouseEvent"</code>, <code>"MutationEvent"</code>, and so on. If the <a href="#events-Events-Event"><code>Event</code></a> is to be dispatched via the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method, the appropriate event initialization method must be called after creation in order to initialize the <a class="noxref" href="#events-Events-Event"><code>Event</code></a>'s values.</p>
-                                
-                                <p class="example" id="example-createEvent"><strong>Example:</strong>  An author wishing to synthesize some kind of <a href="#events-Events-UIEvent"><code>UIEvent</code></a> would invoke <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("UIEvent")</code></a>. The <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method could then be called on the newly created <a class="noxref" href="#events-Events-UIEvent"><code>UIEvent</code></a> object to set the specific type of user interface event to be dispatched, <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> for example, and set its context information, e.g. <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a>.</p>
-
-                                
-                                <p>For backward compatibility reason, <code>"UIEvents"</code>, <code>"MouseEvents"</code>, <code>"MutationEvents"</code>, and <code>"HTMLEvents"</code> feature names are valid values for the parameter <code>eventInterface</code> and represent respectively the interfaces <a href="#events-Events-UIEvent"><code>UIEvent</code></a>, <a href="#events-Events-MouseEvent"><code>MouseEvent</code></a>, <a href="#events-Events-MutationEvent"><code>MutationEvent</code></a>, and <a href="#interface-Event"><code>Event</code></a>, and the characters <code>'a'..'z'</code> are considered equivalent to the characters <code>'A'..'Z'</code>.</p>
-                                
-                                <p>If the parameter does not match an event interface name supported by the implementation, the implementation must raise a <code>NOT_SUPPORTED_ERR</code>  <code>DOMException</code></p>
-                                
-                                <p class="warning" id="warning-createEvent-untrusted"><strong>Warning!</strong>  For security reasons, events generated using <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>.  See <a href="#trusted-events">trusted events</a> for more details.</p>
-
-                                <br />
-                              </dd>
-                            </dl>
-                          </div>
-                        </div>
+                        <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">eventInterface</code> of type <code>DOMString</code></dt><dd><p>The <code>eventInterface</code> parameter specifies the name of the DOM Events interface to be supported by the created event object, e.g. <code>"Event"</code>, <code>"MouseEvent"</code>, <code>"MutationEvent"</code>, and so on. If the <a href="#events-Events-Event"><code>Event</code></a> is to be dispatched via the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method, the appropriate event initialization method must be called after creation in order to initialize the <a class="noxref" href="#events-Events-Event"><code>Event</code></a>'s values.</p><p class="example" id="example-createEvent"><strong>Example:</strong>  An author wishing to synthesize some kind of <a href="#events-Events-UIEvent"><code>UIEvent</code></a> would invoke <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("UIEvent")</code></a>. The <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method could then be called on the newly created <a class="noxref" href="#events-Events-UIEvent"><code>UIEvent</code></a> object to set the specific type of user interface event to be dispatched, <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> for example, and set its context information, e.g. <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a>.</p><p>For backward compatibility reason, <code>"UIEvents"</code>, <code>"MouseEvents"</code>, <code>"MutationEvents"</code>, and <code>"HTMLEvents"</code> feature names are valid values for the parameter <code>eventInterface</code> and represent respectively the interfaces <a href="#events-Events-UIEvent"><code>UIEvent</code></a>, <a href="#events-Events-MouseEvent"><code>MouseEvent</code></a>, <a href="#events-Events-MutationEvent"><code>MutationEvent</code></a>, and <a href="#interface-Event"><code>Event</code></a>, and the characters <code>'a'..'z'</code> are considered equivalent to the characters <code>'A'..'Z'</code>.</p><p>If the parameter does not match an event interface name supported by the implementation, the implementation must raise a <code>NOT_SUPPORTED_ERR</code>  <code>DOMException</code></p><p class="warning" id="warning-createEvent-untrusted"><strong>Warning!</strong>  For security reasons, events generated using <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>.  See <a href="#trusted-events">trusted events</a> for more details.</p><br /></dd>
+</dl></div></div>
                         <!-- parameters -->
                         <div class="return"><strong>Return Value</strong><div class="returntable"><table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr><td><p><a href="#events-Events-Event"><code>Event</code></a></p></td><td><p>The newly created event object.</p></td></tr></table></div></div>
                         <!-- return -->
@@ -1416,7 +1243,6 @@
                         <!-- exceptions --></div>
 <!-- method -->
                     </dd>
-                    
 
                     <dt class="proposal">
                       <code class="method-name">
@@ -1428,79 +1254,61 @@
                         Given a key value and the desired format, this method returns the equivalent key value in the specified format, if the key value exists in that format.
                         
                         <p class="issue"><strong>Issue:</strong> some disagreement on including this (see <a href="http://lists.w3.org/Archives/Public/www-dom/2009JulSep/0412.html">Re: convertKeyValue from Anne van Kesteren on 2009-09-22</a>)</p>
-                        <div class="parameters"><strong>Parameters</strong>
-                          <div class="paramtable">
-                            <dl>
-                              <dt><code class="parameter-name">key</code> of type <code>DOMString</code></dt>
-                              <dd>
-                                <p>The <code>key</code> parameter specifies the string to be converted, as a key value.   This parameter must be one of the following formats: a single character, or a key name (as from the <a href="#key-values">Key Values Set</a>).</p>
-                                <p>The key value need not be represent a value capable of being produced by the system keyboard  in order to be converted.  For example, this method may be used to find the raw <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> of a Chinese ideographic glyph on a computer with only a <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard and no <a class="def" href="#glossary-ime">IME</a> software.
+                        <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">key</code> of type <code>DOMString</code></dt><dd><p>The <code>key</code> parameter specifies the string to be converted, as a key value.   This parameter must be one of the following formats: a single character, or a key name (as from the <a href="#key-values">Key Values Set</a>).</p><p>The key value need not be represent a value capable of being produced by the system keyboard  in order to be converted.  For example, this method may be used to find the raw <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> of a Chinese ideographic glyph on a computer with only a <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard and no <a class="def" href="#glossary-ime">IME</a> software.
                                   <br />
-                                </p>
-                              </dd>
-                              <dt><code class="parameter-name">KeyValueFormat</code> of type <code>unsigned long</code></dt>
-                              <dd>
-                                <p>The <code>KeyValueFormat</code> parameter specifies the format to which the key value must be converted.
+                                </p></dd>
+<dt><code class="parameter-name">KeyValueFormat</code> of type <code>unsigned long</code></dt><dd><p>The <code>KeyValueFormat</code> parameter specifies the format to which the key value must be converted.
                                   <br />
-                                </p>
-                              </dd>
-                            </dl>
-                          </div>
-                        </div>
+                                </p></dd>
+</dl></div></div>
 
                         <!-- parameters -->
-                        <div class="return"><strong>Return Value</strong>
-                          <div class="returntable">
-                            <table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0">
-                              <tr>
-                                <td><p><a href="#events-Events-Event"><code>DOMString</code></a></p></td>
-                                <td><p>The key value in the converted format, or the empty string if no equivalent of the key value exists in the format indicated.</p></td>
-                              </tr>
-                            </table>
-                          </div>
-                        </div>
+                        <div class="return"><strong>Return Value</strong><div class="returntable"><table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr><td><p><a href="#events-Events-Event"><code>DOMString</code></a></p></td><td><p>The key value in the converted format, or the empty string if no equivalent of the key value exists in the format indicated.</p></td></tr></table></div></div>
                         <!-- return -->
-                        <div class="exceptions"><strong>Exceptions</strong>
-                          <div class="exceptiontable">None
+                        <div class="exceptions"><strong>Exceptions</strong><div class="exceptiontable">None
                             <!-- <table summary="Layout table: the first cell contains the type of the exception, the second contains the specific error code and a short description" border="0">
                               <tr>
                                 <td><p><code>DOMException</code></p></td>
                                 <td><p>NOT_SUPPORTED_ERR: Raised if the implementation does not support the <a href="#events-Events-Event"><code>Event</code></a> interface requested.</p></td>
                               </tr>
-                            </table> -->
-                          </div>
-                        </div>
+                           </table> -->
+                          </div></div>
                         <!-- exceptions -->
                       </div>
-      <!-- method -->
+<!-- method -->
                     </dd>
-                    
                   </dl>
                 </dd>
               </dl>
             </dd>
           </dl>
-          <h4 class="div3"><a id="event-creation" href="#event-creation">4.5.1 Event creation</a></h4>
+          <h4><a id="event-creation" href="#event-creation">4.5.1 Event creation</a></h4>
+
           <p>In most cases, the events dispatched by the DOM Events implementation are also created by the implementation.  However, it is possible to simulate events, such as mouse events, by creating the <a href="#events-Events-Event"><code>Event</code></a> objects and dispatch them using the DOM Events implementation.</p>
           <p>Creating <a href="#events-Events-Event"><code>Event</code></a> objects that are known to the DOM Events implementation is done using <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent()</code></a>. The author must then initialize the <a href="#events-Events-Event"><code>Event</code></a> object by directly setting the <a href="#events-Events-Event"><code>Event</code></a>'s property values, by using the generic <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method, or by using any existing event initialization method for that interface, before invoking <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a>. The <a href="#events-Events-Event"><code>Event</code></a> objects created must be known by the DOM Events implementation; otherwise an event exception shall be thrown.</p>
-
-          <p class="example" id="example-create-event"><strong>Example:</strong> <i class="note"><strong>To Do:</strong> Create examples of creating and dispatching an event.</i></p>
+          <p class="example" id="example-create-event">
+            <strong>Example:</strong>
+            <i class="note"><strong>To Do:</strong> Create examples of creating and dispatching an event.</i>
+          </p>
         </div>
 <!-- div3 Events-document -->
       </div>
 <!-- div2 Events-interface -->
     </div>
 <!-- div2 Events-types -->
-    <div class="div2">
-      <h2 class="div2"><a id="events-module" href="#events-module">5. Events Module</a></h2>
-      <h3 class="div2"><a id="event-types" href="#event-types">5.1 Event Types</a></h3>
+    <div>
+      <h2><a id="events-module" href="#events-module">5. Events Module</a></h2>
+
+      <h3><a id="event-types" href="#event-types">5.1 Event Types</a></h3>
+
       <p>Each event shall be associated with a type, called <em>event type</em> and available as the <a href="#events-event-type-type"><code class="interface-attribute">type</code></a> attribute on the event object. The event type must be of type <code>DOMString</code>.</p>
-      <div class="div3">
-        <h4 class="div3"><a id="event-types-list" href="#event-types-list">5.1.1 List of DOM3 Event Types</a></h4>
-        <p>Depending on the level of DOM support, or the devices used for display (e.g. screen) or interaction (e.g., mouse, keyboard, touch screen, or voice), these event types can be generated by the implementation. When used with an [<cite><a class="noxref informative" href="#references-XML">XML 1.0</a></cite>] or [<cite><a class="noxref informative" href="#references-HTML5">HTML5</a></cite>] application, the specifications of those languages may restrict the semantics and scope (in particular the possible <a class="def" href="#glossary-proximal-event-target">proximal event targets</a>) associated with an event type. Refer to the specification defining the language used in order to find those restrictions or to find event types that are not defined in this document.</p>
+      <div>
+        <h4><a id="event-types-list" href="#event-types-list">5.1.1 List of DOM3 Event Types</a></h4>
+
+        <p>Depending on the level of DOM support, or the devices used for display (e.g. screen) or interaction (e.g., mouse, keyboard, touch screen, or voice), these event types can be generated by the implementation. When used with an [<cite><a class="informative" href="#references-XML">XML 1.0</a></cite>] or [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] application, the specifications of those languages may restrict the semantics and scope (in particular the possible <a class="def" href="#glossary-proximal-event-target">proximal event targets</a>) associated with an event type. Refer to the specification defining the language used in order to find those restrictions or to find event types that are not defined in this document.</p>
         <p>The following table provides a non-normative summary of the event types defined in this specification.  All events must accomplish the capture and target phases, but not all of them must accomplish the bubbling phase (see also <a href="#event-flow">Event dispatch and DOM event flow</a>). Some events are not <a href="#events-dt-cancelable-event">cancelable</a> (see <a href="#event-flow-default-cancel">Default actions and cancelable events</a>). Some events must only be dispatched to a specific set of possible targets in the DOM event flow, specified using node types. Contextual information related to the event type must be accessible using DOM interfaces.</p>
         <table id="table-event-summary" summary="This table contains the complete list of event types defined by DOM Level 3 Events. The first column contains the local name of the event type. The second column indicates if the event accomplish the bubbling phase or not (all events accomplish the capture and target phases). The third column indicates if the default action associated with the event can be canceled. The fourth column indicates the nodes that can be target of the event. the fifth (and last) column indicates the DOM interface implemented by the event object.">
-           <!-- border="1" cellpadding="2" cellspacing="0"  -->
+<!-- border="1" cellpadding="2" cellspacing="0"  -->
           <tr>
             <th>Event Type</th>
             <th>Sync / Async</th>
@@ -1511,690 +1319,464 @@
             <th>Default Action</th>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-abort"><code>abort</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-abort">
+              <code>abort</code>
+            </a></td>
             <td>Sync</td>
             <td>No</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-Event">
-                <code>Event</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-blur"><code>blur</code></a>
-            </td>
-            <td>Async</td>
-            <td>No</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-FocusEvent">
-                <code>FocusEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-click"><code>click</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-CompositionEvent">
-                <code>CompositionEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td>Launch <a class="def" href="#glossary-text-composition-system">text composition system</a></td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-CompositionEvent">
-                <code>CompositionEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-CompositionEvent">
-                <code>CompositionEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-UIEvent">
-                <code>UIEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMAttributeNameChanged"><code>DOMAttributeNameChanged</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MutationNameEvent">
-                <code>MutationNameEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MutationEvent">
-                <code>MutationEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td><code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>ProcessingInstruction</code></td>
-            <td>
-              <a href="#events-Events-MutationEvent">
-                <code>MutationEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMElementNameChanged"><code>DOMElementNameChanged</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MutationNameEvent">
-                <code>MutationNameEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-FocusEvent">
-                <code>FocusEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-FocusEvent">
-                <code>FocusEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
-            <td>
-              <a href="#events-Events-MutationEvent">
-                <code>MutationEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code></a>
-            </td>
-            <td>Sync</td>
-            <td>No</td>
-            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
-            <td>
-              <a href="#events-Events-MutationEvent">
-                <code>MutationEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
-            <td>
-              <a href="#events-Events-MutationEvent">
-                <code>MutationEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code></a>
-            </td>
-            <td>Sync</td>
-            <td>No</td>
-            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
-            <td>
-              <a href="#events-Events-MutationEvent">
-                <code>MutationEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>DocumentFragment</code>, <code>Element</code>, <code>Attr</code></td>
-            <td>
-              <a href="#events-Events-MutationEvent">
-                <code>MutationEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-error"><code>error</code></a>
-            </td>
-            <td>Async</td>
-            <td>No</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-Event">
-                <code>Event</code>
-              </a>
-            </td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-Event"><code>Event</code></a></td>
             <td>No</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-focus"><code>focus</code></a>
-            </td>
-            <td>Async</td>
-            <td>No</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-FocusEvent">
-                <code>FocusEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-focusin"><code>focusin</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-FocusEvent">
-                <code>FocusEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-FocusEvent">
-                <code>FocusEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-KeyboardEvent">
-                <code>KeyboardEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-KeyboardEvent">
-                <code>KeyboardEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-KeyboardEvent">
-                <code>KeyboardEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-load"><code>load</code></a>
-            </td>
-            <td>Async</td>
-            <td>No</td>
-            <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
-            <td>
-              <a href="#events-Events-Event">
-                <code>Event</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
-            <td>Yes</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-blur">
+              <code>blur</code>
+            </a></td>
             <td>Sync</td>
             <td>No</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>
-            </td>
-            <td>Sync</td>
-            <td>No</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
             <td>No</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-click">
+              <code>click</code>
+            </a></td>
             <td>Sync</td>
             <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
             <td>Yes</td>
+            <td><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-compositionstart">
+              <code>compositionstart</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td>
+            <td>Yes</td>
+            <td>Launch <a class="def" href="#glossary-text-composition-system">text composition system</a></td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-compositionupdate">
+              <code>compositionupdate</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td>
+            <td>No</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-compositionend">
+              <code>compositionend</code>
+            </a></td>
             <td>Sync</td>
             <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td>
+            <td>Yes</td>
+            <td><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-dblclick">
+              <code>dblclick</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
             <td>Yes</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-DOMActivate">
+              <code>DOMActivate</code>
+            </a></td>
             <td>Sync</td>
             <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
             <td>Yes</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-DOMAttributeNameChanged">
+              <code>DOMAttributeNameChanged</code>
+            </a></td>
             <td>Sync</td>
             <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-MouseEvent">
-                <code>MouseEvent</code>
-              </a>
-            </td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMAttrModified">
+              <code>DOMAttrModified</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMCharacterDataModified">
+              <code>DOMCharacterDataModified</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>ProcessingInstruction</code></td>
+            <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMElementNameChanged">
+              <code>DOMElementNameChanged</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMFocusIn">
+              <code>DOMFocusIn</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMFocusOut">
+              <code>DOMFocusOut</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMNodeInserted">
+              <code>DOMNodeInserted</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
+            <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument">
+              <code>DOMNodeInsertedIntoDocument</code>
+            </a></td>
+            <td>Sync</td>
+            <td>No</td>
+            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
+            <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMNodeRemoved">
+              <code>DOMNodeRemoved</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
+            <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument">
+              <code>DOMNodeRemovedFromDocument</code>
+            </a></td>
+            <td>Sync</td>
+            <td>No</td>
+            <td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
+            <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-DOMSubtreeModified">
+              <code>DOMSubtreeModified</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>DocumentFragment</code>, <code>Element</code>, <code>Attr</code></td>
+            <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-error">
+              <code>error</code>
+            </a></td>
+            <td>Async</td>
+            <td>No</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-Event"><code>Event</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-focus">
+              <code>focus</code>
+            </a></td>
+            <td>Sync</td>
+            <td>No</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-focusin">
+              <code>focusin</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-focusout">
+              <code>focusout</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-keydown">
+              <code>keydown</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
+            <td>Yes</td>
+            <td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-keypress">
+              <code>keypress</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
+            <td>Yes</td>
+            <td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-keyup">
+              <code>keyup</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
             <td>Yes</td>
             <td>none</td>
           </tr>
-          <!-- <tr>
-            <td>
-              <a class="eventtype" href="#event-type-mousewheel"><code>mousewheel</code></a>
-            </td>
+          <tr>
+            <td><a class="eventtype" href="#event-type-load">
+              <code>load</code>
+            </a></td>
+            <td>Async</td>
+            <td>No</td>
+            <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
+            <td><a href="#events-Events-Event"><code>Event</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-mousedown">
+              <code>mousedown</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+            <td>Yes</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-mouseenter">
+              <code>mouseenter</code>
+            </a></td>
+            <td>Sync</td>
+            <td>No</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-mouseleave">
+              <code>mouseleave</code>
+            </a></td>
+            <td>Sync</td>
+            <td>No</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-mousemove">
+              <code>mousemove</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+            <td>Yes</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-mouseout">
+              <code>mouseout</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+            <td>Yes</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-mouseover">
+              <code>mouseover</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+            <td>Yes</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-mouseup">
+              <code>mouseup</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+            <td>Yes</td>
+            <td>none</td>
+          </tr>
+<!-- <tr>
+            <td><a class="eventtype" href="#event-type-mousewheel">
+              <code>mousewheel</code>
+            </a></td>
             <td>Sync</td>
             <td>Yes</td>
             <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
-            <td>
-              <a href="#events-Events-MouseWheelEvent">
-                <code>MouseWheelEvent</code>
-              </a>
-            </td>
+            <td><a href="#events-Events-MouseWheelEvent"><code>MouseWheelEvent</code></a></td>
             <td>Yes</td>
             <td>Scroll (or zoom) the document</td>
           </tr> -->
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-resize"><code>resize</code></a>
-            </td>
-            <td>Async</td>
-            <td>No</td>
-            <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
-            <td>
-              <a href="#events-Events-UIEvent">
-                <code>UIEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a>
-            </td>
-            <td>Async</td>
+            <td><a class="eventtype" href="#event-type-resize">
+              <code>resize</code>
+            </a></td>
+            <td>Sync</td>
             <td>No</td>
             <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
-            <td>
-              <a href="#events-Events-UIEvent">
-                <code>UIEvent</code>
-              </a>
-            </td>
-            <td>No</td>
-            <td>none</td>
-          </tr>
-          <tr>
-            <td>
-              <a class="eventtype" href="#event-type-select"><code>select</code></a>
-            </td>
-            <td>Sync</td>
-            <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-Event">
-                <code>Event</code>
-              </a>
-            </td>
+            <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
             <td>No</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-scroll">
+              <code>scroll</code>
+            </a></td>
+            <td>Async</td>
+            <td>No</td>
+            <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
+            <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-select">
+              <code>select</code>
+            </a></td>
             <td>Sync</td>
             <td>Yes</td>
-            <td>
-              <code>Element</code>
-            </td>
-            <td>
-              <a href="#events-Events-TextEvent">
-                <code>TextEvent</code>
-              </a>
-            </td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-Event"><code>Event</code></a></td>
+            <td>No</td>
+            <td>none</td>
+          </tr>
+          <tr>
+            <td><a class="eventtype" href="#event-type-textInput">
+              <code>textInput</code>
+            </a></td>
+            <td>Sync</td>
+            <td>Yes</td>
+            <td><code>Element</code></td>
+            <td><a href="#events-Events-TextEvent"><code>TextEvent</code></a></td>
             <td>Yes</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-unload"><code>unload</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-unload">
+              <code>unload</code>
+            </a></td>
             <td>Sync</td>
             <td>No</td>
             <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
-            <td>
-              <a href="#events-Events-Event">
-                <code>Event</code>
-              </a>
-            </td>
+            <td><a href="#events-Events-Event"><code>Event</code></a></td>
             <td>No</td>
             <td>none</td>
           </tr>
           <tr>
-            <td>
-              <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a>
-            </td>
+            <td><a class="eventtype" href="#event-type-wheel">
+              <code>wheel</code>
+            </a></td>
             <td>Sync</td>
             <td>Yes</td>
             <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
-            <td>
-              <a href="#events-Events-WheelEvent">
-                <code>WheelEvent</code>
-              </a>
-            </td>
+            <td><a href="#events-Events-WheelEvent"><code>WheelEvent</code></a></td>
             <td>Yes</td>
             <td>Scroll (or zoom) the document</td>
           </tr>
-          <!-- <tr>
-            <td>
-              <a class="eventtype" href="#event-type-zoom"><code>zoom</code></a>
-            </td>
+<!-- <tr>
+            <td><a class="eventtype" href="#event-type-zoom">
+              <code>zoom</code>
+            </a></td>
             <td>Async</td>
             <td>No</td>
             <td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
-            <td>
-              <a href="#events-Events-UIEvent">
-                <code>UIEvent</code>
-              </a>
-            </td>
+            <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
             <td>No</td>
             <td>none</td>
           </tr> -->
@@ -2204,18 +1786,16 @@
       </div>
 <!-- div3 Events-EventTypes-complete -->
     </div>
-    
-    
 <!-- div2 Events-definitions -->
-    <div class="div2">
-      <h2 class="div2"><a id="event-definitions" href="#event-definitions">5.2 Event Module Definitions</a></h2>
+    <div>
+      <h2><a id="event-definitions" href="#event-definitions">5.2 Event Module Definitions</a></h2>
+
       <p>The DOM Event Model allows a DOM implementation to support multiple modules of events. The model has been designed to allow addition of new event modules if required. This document does not attempt to define all possible events. For purposes of interoperability, the DOM defines a module of user interface events including lower level device dependent events and a module of document mutation events.</p>
-      
-      <div class="div3">
-        <h3 class="div3"><a id="events-uievents" href="#events-uievents">5.2.1 User Interface Event Types</a></h3>
+      <div>
+        <h3><a id="events-uievents" href="#events-uievents">5.2.1 User Interface Event Types</a></h3>
+
         <p>This module defines the feature UIEvents 3.0 and depends on the features Events 3.0 and Views 2.0.</p>
         <p>The User Interface event module contains basic event types associated with user interfaces and document manipulation.</p>
-
         <dl>
           <dt><strong>Interface <em><a id="events-Events-UIEvent">UIEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
           <dd>
@@ -2229,34 +1809,34 @@
               <dd>
                 <div class="idl-code">
                   <pre>
-    // Introduced in DOM Level 2:
-    interface <a href="#events-Events-UIEvent">UIEvent</a> : <a href="#events-Events-Event">Event</a> {
-      readonly attribute views::AbstractView <a href="#events-Events-UIEvent-view">view</a>;
-      readonly attribute long            <a href="#events-Events-UIEvent-detail">detail</a>;
-      void               <a href="#events-event-type-initUIEvent">initUIEvent</a>(in DOMString typeArg, 
-                                     in boolean canBubbleArg, 
-                                     in boolean cancelableArg, 
-                                     in views::AbstractView viewArg, 
-                                     in long detailArg);
-    };
-    </pre>
+// Introduced in DOM Level 2:
+interface <a href="#events-Events-UIEvent">UIEvent</a> : <a href="#events-Events-Event">Event</a> {
+  readonly attribute views::AbstractView <a href="#events-Events-UIEvent-view">view</a>;
+  readonly attribute long            <a href="#events-Events-UIEvent-detail">detail</a>;
+  void               <a href="#events-event-type-initUIEvent">initUIEvent</a>(in DOMString typeArg, 
+                                 in boolean canBubbleArg, 
+                                 in boolean cancelableArg, 
+                                 in views::AbstractView viewArg, 
+                                 in long detailArg);
+};
+                  </pre>
                 </div>
                 <br />
               </dd>
-              <dt>
-                <strong>Attributes</strong>
-              </dt>
+
+              <dt><strong>Attributes</strong></dt>
               <dd>
                 <dl>
                   <dt><code class="attribute-name"><a id="events-Events-UIEvent-detail">detail</a></code> of type <code>long</code>, readonly</dt>
                   <dd>Specifies some detail information about the <a href="#events-Events-Event"><code>Event</code></a>, depending on the type of event.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-UIEvent-view">view</a></code> of type <code>views::AbstractView</code>, readonly</dt>
                   <dd>The <code>view</code> attribute identifies the <code>AbstractView</code> from which the event was generated.<br /></dd>
+
                 </dl>
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -2266,9 +1846,15 @@
                   </dt>
                   <dd>
                     <div class="method">Initializes attributes of an <code>UIEvent</code> object. This method has the same behavior as <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a>.
-    <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Specifies <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>. This value may be <code>null</code>.<br /></dd><dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a>.<br /></dd></dl></div></div>
+    <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Specifies <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>. This value may be <code>null</code>.<br /></dd>
+<dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a>.<br /></dd>
+</dl></div></div>
                             <!-- parameters -->
                             <div><strong>No Return Value</strong></div>
+
                             <div><strong>No Exceptions</strong></div>
                           </div>
 <!-- method -->
@@ -2283,86 +1869,157 @@
 <!-- DOMActivate -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-DOMActivate">
-              <a class="eventtype noxref" href="#event-type-DOMActivate"><code>DOMActivate</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMActivate</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a button, link, or other state-changing element is activated.  Refer to <a href="#event-flow-activation">Activation triggers and behavior</a> for more details.</dd>
-
-              <p class="warning" id="DOMActivate-deprecated"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the related <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a>.  Other specifications may define and maintain their own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> for backwards compatibility.</p>
-              
-              <p class="note" id="DOMActivate-click"><strong>Note:</strong>   While <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> and <a class="eventtype" href="#event-type-click"><code>click</code></a> are not completely equivalent, implemented behavior for the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> has developed to encompass the most critical accessibility aspects for which the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> was designed, and is more widely implemented.  Authors are encouraged to use the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> rather than the related <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> or <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> <a class="def" href="#glossary-event-type">event type</a> to ensure maximum accessibility.</p>
+            <dt id="event-type-DOMActivate"><dfn>
+                <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMActivate</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a button, link, or other state-changing element is activated.  Refer to <a href="#event-flow-activation">Activation triggers and behavior</a> for more details.</p>
+              <p class="warning" id="DOMActivate-deprecated"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a><a class="def" href="#glossary-event-type">event type</a> is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the related <a class="def" href="#glossary-event-type">event type</a><a class="eventtype" href="#event-type-click"><code>click</code></a>.  Other specifications may define and maintain their own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a><a class="def" href="#glossary-event-type">event type</a> for backwards compatibility.</p>
+              <p class="note" id="DOMActivate-click"><strong>Note:</strong>   While <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> and <a class="eventtype" href="#event-type-click"><code>click</code></a> are not completely equivalent, implemented behavior for the <a class="eventtype" href="#event-type-click"><code>click</code></a><a class="def" href="#glossary-event-type">event type</a> has developed to encompass the most critical accessibility aspects for which the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a><a class="def" href="#glossary-event-type">event type</a> was designed, and is more widely implemented.  Authors are encouraged to use the <a class="eventtype" href="#event-type-click"><code>click</code></a><a class="def" href="#glossary-event-type">event type</a> rather than the related <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> or <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a><a class="def" href="#glossary-event-type">event type</a> to ensure maximum accessibility.</p>
+            </dd>
           </dl>
         </div>
 
 <!-- load -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-load">
-              <a class="eventtype noxref" href="#event-type-load"><code>load</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>load</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr><tr class="assert must"><th>Sync / Async</th><td>Async</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the DOM implementation finishes loading the resource (such as the document) and any dependent resources (such as images, style sheets, or scripts). Dependent resources that fail to load must not prevent this event from firing if the resource that loaded them is still accessible via the DOM. If this event type is dispatched, implementations are required to dispatch this event at least on the <code>Document</code> node.
-              <!-- This event differs from the <a class="eventtype" href="#event-type-DOMContentLoaded"><code>DOMContentLoaded</code></a> event in that it is not dispatched until all external resources are loaded.  -->
+            <dt id="event-type-load"><dfn>
+                <a class="eventtype" href="#event-type-load"><code>load</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>load</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the DOM implementation finishes loading the resource (such as the document) and any dependent resources (such as images, style sheets, or scripts). Dependent resources that fail to load must not prevent this event from firing if the resource that loaded them is still accessible via the DOM. If this event type is dispatched, implementations are required to dispatch this event at least on the <code>Document</code> node.</p>
+<!-- This event differs from the <a class="eventtype" href="#event-type-DOMContentLoaded"><code>DOMContentLoaded</code></a> event in that it is not dispatched until all external resources are loaded.  -->
             </dd>
           </dl>
         </div>
-
+        
 <!-- DOMContentLoaded -->
-        <!-- <div class="event-definition assert must">
+<!-- <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-DOMContentLoaded">
-              <a class="eventtype noxref" href="#event-type-DOMContentLoaded"><code>DOMContentLoaded</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMContentLoaded</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the DOM implementation finishes loading the resource (such as the document), but before any dependent resources (such as images, style sheets, or scripts) are necessary loaded.  If this event type is dispatched, implementations are required to dispatch this event at least on the <code>Document</code> node.  This event differs from the <a class="eventtype" href="#event-type-load"><code>load</code></a> event in that it is dispatched immediately when the document markup is loaded, rather than waiting on external resources. 
+            <dt id="event-type-DOMContentLoaded"><dfn><a class="eventtype" href="#event-type-DOMContentLoaded"><code>DOMContentLoaded</code></a></dfn></dt>
+            <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMContentLoaded</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr>
+              </table>
+              
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the DOM implementation finishes loading the resource (such as the document), but before any dependent resources (such as images, style sheets, or scripts) are necessary loaded.  If this event type is dispatched, implementations are required to dispatch this event at least on the <code>Document</code> node.  This event differs from the <a class="eventtype" href="#event-type-load"><code>load</code></a> event in that it is dispatched immediately when the document markup is loaded, rather than waiting on external resources.</p>
             </dd>
           </dl>
         </div>
  -->
-        
+
 <!-- unload -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-unload">
-              <a class="eventtype noxref" href="#event-type-unload"><code>unload</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>unload</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the DOM Implementation removes from the environment the resource (such as the document) or any dependent resources (such as images, style sheets, scripts). The document shall be unloaded after the dispatch of this event type. If this event type is dispatched, implementations are required to dispatch this event at least on the <code>Document</code> node.</dd>
+            <dt id="event-type-unload"><dfn>
+                <a class="eventtype" href="#event-type-unload"><code>unload</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>unload</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the DOM Implementation removes from the environment the resource (such as the document) or any dependent resources (such as images, style sheets, scripts). The document shall be unloaded after the dispatch of this event type. If this event type is dispatched, implementations are required to dispatch this event at least on the <code>Document</code> node.</p>
+            </dd>
           </dl>
         </div>
-        
+
 <!-- abort -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-abort">
-              <a class="eventtype noxref" href="#event-type-abort"><code>abort</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>abort</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the loading of a resource has been aborted.</dd>
+            <dt id="event-type-abort"><dfn>
+                <a class="eventtype" href="#event-type-abort"><code>abort</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>abort</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when the loading of a resource has been aborted.</p>
+            </dd>
           </dl>
         </div>
-        
+
 <!-- error -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-error">
-              <a class="eventtype noxref" href="#event-type-error"><code>error</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>error</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr><tr class="assert must"><th>Sync / Async</th><td>Async</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a resource failed to load, or has been loaded but cannot be interpreted according to its semantics, such as an invalid image, a script execution error, or non-well-formed XML.</dd>
+            <dt id="event-type-error"><dfn>
+                <a class="eventtype" href="#event-type-error"><code>error</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>error</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a resource failed to load, or has been loaded but cannot be interpreted according to its semantics, such as an invalid image, a script execution error, or non-well-formed XML.</p>
+            </dd>
           </dl>
         </div>
-        
+
 <!-- select -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-select">
-              <a class="eventtype noxref" href="#event-type-select"><code>select</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>select</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a user selects some text.  This specification does not provide contextual information to access the selected text. <i class="issue"  id="issue-selected_text"><strong>Issue:</strong> need to detail how the author can get at this information, perhaps through HTML5 <a href="http://dev.w3.org/html5/spec/editing.html#selection" title="7 User Interaction &#8212; HTML 5">text selection APIs</a></i> <!-- The <a class="def" href="#glossary-user-agent">user agent</a> must make the selected text passage available through the <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute.  <span class="issue"><strong>Issue:</strong> should the selection include the markup structure, or just the text-content?</span> --> This event is dispatched after the selection has occurred.
-              <p class="note"><strong>Note:</strong> The <a class="eventtype" href="#event-type-select"><code>select</code></a> event may not be available for all elements in all languages.  For example, in [<cite><a class="noxref informative" href="#references-HTML5">HTML5</a></cite>], <a class="eventtype" href="#event-type-select"><code>select</code></a> events will only be dispatched on only form <code>input</code> and <code>textarea</code> elements.  Implementations may dispatch <a class="eventtype" href="#event-type-select"><code>select</code></a> events in any context deemed appropriate, including text selections outside of form controls, or image or markup selections such as in SVG.</p>
+            <dt id="event-type-select"><dfn>
+                <a class="eventtype" href="#event-type-select"><code>select</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>select</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a user selects some text.  This specification does not provide contextual information to access the selected text. <i class="issue" id="issue-selected_text"><strong>Issue:</strong> need to detail how the author can get at this information, perhaps through HTML5 <a href="http://dev.w3.org/html5/spec/editing.html#selection" title="7 User Interaction &#x2014; HTML 5">text selection APIs</a></i> <!-- The <a class="def" href="#glossary-user-agent">user agent</a> must make the selected text passage available through the <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute.  <span class="issue"><strong>Issue:</strong> should the selection include the markup structure, or just the text-content?</span> --> This event is dispatched after the selection has occurred.</p>
+              <p class="note"><strong>Note:</strong> The <a class="eventtype" href="#event-type-select"><code>select</code></a> event may not be available for all elements in all languages.  For example, in [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>], <a class="eventtype" href="#event-type-select"><code>select</code></a> events will only be dispatched on only form <code>input</code> and <code>textarea</code> elements.  Implementations may dispatch <a class="eventtype" href="#event-type-select"><code>select</code></a> events in any context deemed appropriate, including text selections outside of form controls, or image or markup selections such as in SVG.</p>
             </dd>
           </dl>
         </div>
@@ -2370,12 +2027,31 @@
 <!-- resize -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-resize">
-              <a class="eventtype noxref" href="#event-type-resize"><code>resize</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>resize</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Async</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a document view or an element has been resized. This event type is dispatched after the resize has occurred.
-              <p class="note"><strong>Note:</strong> In previous DOM Events specifications, the <a class="eventtype noxref" href="#event-type-resize"><code>resize</code></a> event type was defined to have a <a class="def" href="#glossary-bubbling-phase">bubbling phase</a>, but for performance reasons, this was not implemented in most user agents, and this specification removes the <a class="def" href="#glossary-bubbling-phase">bubbling phase</a> for this event.</p>
+            <dt id="event-type-resize"><dfn>
+                <a class="eventtype" href="#event-type-resize"><code>resize</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>resize</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a document view or an element has been resized. This event type is dispatched after all effects for that occurrence of resizing of that particular <a class="def" href="#glossary-event-target">event target</a> have been executed by the <a class="def" href="#glossary-user-agent">user agent</a>.</p>
+              <p>In the case of a user-initiated resizing, i.e when a user expands or shrinks a browser window or a resizable element such as <code class="element">object</code> or <code class="element">iframe</code> by dragging the edge of the frame, the frame undergoes several consecutive size changes, but these intermediate stages must not be dispatched as <a class="eventtype" href="#event-type-resize"><code>resize</code></a> events.</p>
+              <p class="note" id="note-resize-multiple"><strong>Note:</strong>  Some <a class="def" href="#glossary-user-agent">user agents</a> may have an optional mode in which the document is reflowed dynamically while the window is resized; in this mode, <a class="eventtype" href="#event-type-resize"><code>resize</code></a> events may be dispatched continuously while the resizing operation is in progress.</p>
+              <p>Once the user has finished resizing, in a system- and  implementation-determined manner such as the release of the pointer button or after a sufficiently long pause, or once any instant resizing (e.g. from a window maximize button or a script effect) has been executed, the <a class="def" href="#glossary-user-agent">user agent</a> must perform any relevant layout recalculations or other actions caused by the resizing, and must subsequently dispatch a single <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event that reflects the final state of the <a class="def" href="#glossary-event-target">event target</a>.  In the case where multiple <a class="eventtype" href="#event-type-resize"><code>resize</code></a> events have been triggered as the result of the same action, even for different <a class="def" href="#glossary-event-target">event target</a>, the <a class="def" href="#glossary-user-agent">user agent</a> must dispatch each <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event only after the previous <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event has completed its <a class="def" href="#glossary-propagation-path">propagation path</a> or been canceled.</p>
+              <p class="issue" id="issue-resize-queue"><strong>Issue:</strong>  There is no current interoperability here.  See <a href="http://www.w3.org/2008/webapps/track/issues/113" title="ISSUE-113 - Web Applications Working Group Tracker">ISSUE-113</a>.</p>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> should dispatch the <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event before the document is re-rendered, to provide the author an opportunity to adjust the content to suit the new size.</p>
+              <p class="issue" id="issue-resize-repaint"><strong>Issue:</strong> Firing the event between reflow and repaint may be difficult in some UAs (see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=227495#c30">Mozilla Bug #227495</a>), but it seems the behavior most authors would want.  Should we keep this, or change it to fire after repaint?</p>
+<!-- <p class="example" id="example-resize"><strong>Example:</strong> </p> -->
+              <p>The <a class="def" href="#glossary-defaultView"><code>defaultView</code></a> object should always be resizable.  A <a class="def" href="#glossary-host-language">host language</a> should define which elements, if any, are resizable, and under what conditions (e.g. specific elements like <code class="element">iframe</code>, or elements with particular characteristics like width and height).</p>
+              <p class="note" id="note-resize-zoom"><strong>Note:</strong>  The <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event is distinct from the <a class="eventtype" href="#event-type-zoom"><code>zoom</code></a> event, though both may occur at the same time, or as the consequence of the same user action.  In particular, browser "font zooming" or "page zooming" should not necessarily trigger a <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event.</p>
+              <p class="note" id="note-resize-bubbling"><strong>Note:</strong> In previous DOM Events specifications, the <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event type was defined to have a <a class="def" href="#glossary-bubbling-phase">bubbling phase</a>, but for performance reasons, this was not implemented in most user agents, and this specification removes the <a class="def" href="#glossary-bubbling-phase">bubbling phase</a> for this event.</p>
             </dd>
           </dl>
         </div>
@@ -2383,36 +2059,53 @@
 <!-- scroll -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-scroll">
-              <a class="eventtype noxref" href="#event-type-scroll"><code>scroll</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>scroll</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Async</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a document view or an element has been scrolled.  This event type is dispatched after the scroll has occurred.</dd>
+            <dt id="event-type-scroll"><dfn>
+                <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>scroll</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a document view or an element has been scrolled.  This event type is dispatched after the scroll has occurred.</p>
+            </dd>
           </dl>
         </div>
-
 <!-- zoom -->
-        <!-- <div class="event-definition assert must">
+<!-- <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-zoom">
-              <a class="eventtype noxref" href="#event-type-zoom"><code>zoom</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>zoom</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Async</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-current-scale-coefficient">current scale coefficient</a> of the <a class="def" href="#glossary-event-target">event target</a>.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a document view or an element has been zoomed.  This event type is dispatched after the scroll has occurred.
+            <dt id="event-type-zoom"><dfn><a class="eventtype" href="#event-type-zoom"><code>zoom</code></a></dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>zoom</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+                <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-current-scale-coefficient">current scale coefficient</a> of the <a class="def" href="#glossary-event-target">event target</a>.</td></tr>
+              </table>
+              
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a document view or an element has been zoomed.  This event type is dispatched after the scroll has occurred.</p>
               <p>The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> must reflect the <dfn id="events-current-scale-coefficient">current scale coefficient</dfn> (or "zoom level") of the document or element.  The initial value for the current scale coefficient must be 1.  Each doubling in size of the <a class="def" href="#glossary-event-target">event target</a> must multiply the current scale coefficient, and each halving</p>
             </dd>
           </dl>
         </div>
+ -->
       </div>
-    </div> -->
-
-
-
-    <!-- interface events-focusevents -->
-    <div class="div3">
-      <h3 class="div3"><a id="events-focusevent" href="#events-focusevent">5.2.2 Focus Event Types</a></h3>
+    </div>
+<!-- interface events-focusevents -->
+    <div>
+      <h3><a id="events-focusevent" href="#events-focusevent">5.2.2 Focus Event Types</a></h3>
+
       <p>This module defines the feature FocusEvents 3.0 and depends on the feature UIEvents 3.0.</p>
-
       <dl>
         <dt><strong>Interface <em><a id="events-Events-FocusEvent">FocusEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
         <dd>
@@ -2426,32 +2119,31 @@
             <dd>
               <div class="idl-code">
                 <pre>
-  // Introduced in DOM Level 3:
-  interface <a href="#events-Events-FocusEvent">FocusEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
-    readonly attribute <a href="#events-Events-EventTarget">EventTarget</a>     <a href="#events-Events-FocusEvent-relatedTarget">relatedTarget</a>;
-    void               <a href="#events-event-type-initFocusEvent">initFocusEvent</a>(in DOMString typeArg, 
-                                  in boolean canBubbleArg, 
-                                  in boolean cancelableArg, 
-                                  in views::AbstractView viewArg, 
-                                  in long detailArg, 
-                                  in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
-  };
-  </pre>
+// Introduced in DOM Level 3:
+interface <a href="#events-Events-FocusEvent">FocusEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
+  readonly attribute <a href="#events-Events-EventTarget">EventTarget</a>     <a href="#events-Events-FocusEvent-relatedTarget">relatedTarget</a>;
+  void               <a href="#events-event-type-initFocusEvent">initFocusEvent</a>(in DOMString typeArg, 
+                                in boolean canBubbleArg, 
+                                in boolean cancelableArg, 
+                                in views::AbstractView viewArg, 
+                                in long detailArg, 
+                                in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
+};
+                </pre>
               </div>
               <br />
             </dd>
-            <dt>
-              <strong>Attributes</strong>
-            </dt>
+
+            <dt><strong>Attributes</strong></dt>
             <dd>
               <dl>
                 <dt><code class="attribute-name"><a id="events-Events-FocusEvent-relatedTarget">relatedTarget</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
                 <dd>Used to identify a secondary <a href="#events-Events-EventTarget"><code>EventTarget</code></a> related to a Focus event, depending on the type of event.<br /></dd>
+
               </dl>
             </dd>
-            <dt>
-              <strong>Methods</strong>
-            </dt>
+
+            <dt><strong>Methods</strong></dt>
             <dd>
               <dl>
                 <dt>
@@ -2461,26 +2153,16 @@
                 </dt>
                 <dd>
                   <div class="method">Initializes attributes of a <code>FocusEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>.
-                    <div class="parameters"><strong>Parameters</strong>
-                      <div class="paramtable">
-                        <dl>
-                          <dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt>
-                          <dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
-                          <dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt>
-                          <dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
-                          <dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt>
-                          <dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
-                          <dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt>
-                          <dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
-                          <dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt>
-                          <dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
-                          <dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt>
-                          <dd>Specifies <a href="#events-Events-FocusEvent-relatedTarget"><code>FocusEvent.relatedTarget</code></a>. This value may be <code>null</code>.<br /></dd>
-                        </dl>
-                      </div>
-                    </div>
+                    <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt><dd>Specifies <a href="#events-Events-FocusEvent-relatedTarget"><code>FocusEvent.relatedTarget</code></a>. This value may be <code>null</code>.<br /></dd>
+</dl></div></div>
                     <!-- parameters -->
                     <div><strong>No Return Value</strong></div>
+
                     <div><strong>No Exceptions</strong></div>
                   </div>
 <!-- method -->
@@ -2491,36 +2173,46 @@
         </dd>
       </dl>
       <p>The Focus event types are listed below.</p>
-
-      <h4 class="div3 needswork"><a id="events-focusevent-event-order" href="#events-focusevent-event-order">5.2.2.1 Focus Event Order</a></h4>
+      <h4 class="needswork">
+        <a id="events-focusevent-event-order" href="#events-focusevent-event-order">5.2.2.1 Focus Event Order</a>
+      </h4>
       <p>The focus events defined in this specification occur in a set order relative to one another.  The following is the typical sequence of events when a focus is shifted between elements (this order assumes that no element is initially focused):</p>
       <ol>
-        <li><em>[user shifts focus]</em> <a class="eventtype" href="#event-type-focusin"><code>focusin</code></a> (before first target element receives focus)</li>
+        <li><em>[user shifts focus]</em><a class="eventtype" href="#event-type-focusin"><code>focusin</code></a> (before first target element receives focus)</li>
         <li><a class="eventtype" href="#event-type-focus"><code>focus</code></a> (after first target element receives focus)</li>
         <li><a class="eventtype" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a> (if supported)</li>
-        <li><em>[user shifts focus]</em> <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a> (before first target element loses focus)</li>
+        <li><em>[user shifts focus]</em><a class="eventtype" href="#event-type-focusout"><code>focusout</code></a> (before first target element loses focus)</li>
         <li><a class="eventtype" href="#event-type-focusin"><code>focusin</code></a> (before second target element receives focus)</li>
         <li><a class="eventtype" href="#event-type-blur"><code>blur</code></a> (after first target element loses focus)</li>
         <li><a class="eventtype" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a> (if supported)</li>
         <li><a class="eventtype" href="#event-type-focus"><code>focus</code></a> (after second target element receives focus)</li>
         <li><a class="eventtype" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a> (if supported)</li>
       </ol>
-      
-      
       <p class="issue"><strong>Issue:</strong> Behavior of focus events when interacting with focus()/blur() methods needs to be defined.  See [<a href="http://www.w3.org/2008/webapps/track/issues/102">ISSUE-102</a>]</p>
-
-      <h4 class="div3 needswork"><a id="events-focusevent-doc-focus" href="#events-focusevent-doc-focus">5.2.2.2 Document Focus and Focus Context</a></h4>
+      <h4 class="needswork">
+        <a id="events-focusevent-doc-focus" href="#events-focusevent-doc-focus">5.2.2.2 Document Focus and Focus Context</a>
+      </h4>
       <p>This event module includes event types for notification of changes in document <a class="def" href="#glossary-event-focus">focus</a>.  Depending on the environment, document focus may be distinct from <a class="def" href="#glossary-user-agent">user agent</a> focus and operating system focus; this is referred to as focus context.  For example, in a typical desktop browser environment, the operating system context focus may be on one of many different applications, one of which is the browser; when the browser has focus, the user may shift  the application context focus (such as with the tab key) among different browser user interface fields (e.g. the Web site location bar, a search field, etc.) before or after achieving document focus; once the document itself has focus, sequential shifting of focus will step through the focusable elements in the document.  The event types defined in this specification deal exclusively with document focus, and the <a class="def" href="#glossary-event-target">event target</a> identified in the event details must only be part of the document or documents in the window, never a part of the browser or operating system, even when switching from one focus context to another.</p>
       <p>Normally, a document always has a focused element, even if it is the document element itself, and a persistent <a class="def" href="#glossary-event-focus-ring">focus ring</a>; when switching between focus contexts, the document's currently focused element and focus ring normally remain the their current state; for example, if a document has three focusable elements, with the second element focused, when a user changes operating system focus to another application and then back to the browser, the second element will still be focused within the document, and tabbing will change the focus to the third element.  A <a class="def" href="#glossary-host-language">host language</a> may define specific elements which may or may not receive focus, the conditions user which an element may receive focus, the means by which focus may be changed, and the order in which the focus changes.  For example, in some cases an element may be given focus by moving a pointer over it, while other circumstances may require a mouse click; some elements may not be focusable at all, and some may be focusable only by special means (clicking on the element), but not by tabbing to it.  Documents may contain multiple focus rings.  Other specifications may define a more complex focus model than is described in this specification, including allowing multiple elements to have the current focus.</p>
 
 <!-- blur -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-blur">
-            <a class="eventtype noxref" href="#event-type-blur"><code>blur</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>blur</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Async</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> losing focus.</td></tr></table>
-  A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses focus. The focus shall be taken from the element before the dispatch of this event type.  This event type is similar to <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a>, but is dispatched after focus is shifted, and does not bubble.
+          <dt id="event-type-blur"><dfn>
+              <a class="eventtype" href="#event-type-blur"><code>blur</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>blur</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> losing focus.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses focus. The focus shall be taken from the element before the dispatch of this event type.  This event type is similar to <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a>, but is dispatched after focus is shifted, and does not bubble.</p>
           </dd>
         </dl>
       </div>
@@ -2528,11 +2220,21 @@
 <!-- DOMFocusIn -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-DOMFocusIn">
-            <a class="eventtype noxref" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusIn</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> receiving focus.</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives focus. The focus shall be given to the element before the dispatch of this event type. This event type shall be dispatched after the event type <a class="eventtype" href="#event-type-focus"><code>focus</code></a>.
+          <dt id="event-type-DOMFocusIn"><dfn>
+              <a class="eventtype" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusIn</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> receiving focus.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives focus. The focus shall be given to the element before the dispatch of this event type. This event type shall be dispatched after the event type <a class="eventtype" href="#event-type-focus"><code>focus</code></a>.</p>
             <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the related event types <a class="eventtype" href="#event-type-focus"><code>focus</code></a> and <a class="eventtype" href="#event-type-focusin"><code>focusin</code></a>.</p>
           </dd>
         </dl>
@@ -2541,12 +2243,22 @@
 <!-- DOMFocusOut -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-DOMFocusOut">
-            <a class="eventtype noxref" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusOut</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> losing focus.</td></tr></table>
-  A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses focus. The focus shall be taken from the element before the dispatch of this event type. This event type shall be dispatched after the event type <a class="eventtype" href="#event-type-blur"><code>blur</code></a>.
-  <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the related event types <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a>.</p>
+          <dt id="event-type-DOMFocusOut"><dfn>
+              <a class="eventtype" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusOut</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> losing focus.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses focus. The focus shall be taken from the element before the dispatch of this event type. This event type shall be dispatched after the event type <a class="eventtype" href="#event-type-blur"><code>blur</code></a>.</p>
+            <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the related event types <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a>.</p>
           </dd>
         </dl>
       </div>
@@ -2554,11 +2266,21 @@
 <!-- focus -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-focus">
-            <a class="eventtype noxref" href="#event-type-focus"><code>focus</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>focus</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Async</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> receiving focus.</td></tr></table>
-  A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives focus. The focus shall be given to the element before the dispatch of this event type.  This event type is similar to <a class="eventtype" href="#event-type-focusin"><code>focusin</code></a>, but is dispatched after focus is shifted, and does not bubble..
+          <dt id="event-type-focus"><dfn>
+              <a class="eventtype" href="#event-type-focus"><code>focus</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>focus</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> and <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attributes is the <a class="def" href="#glossary-event-target">event target</a> receiving focus.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives focus. The focus shall be given to the element before the dispatch of this event type.  This event type is similar to <a class="eventtype" href="#event-type-focusin"><code>focusin</code></a>, but is dispatched after focus is shifted, and does not bubble.</p>
           </dd>
         </dl>
       </div>
@@ -2566,11 +2288,21 @@
 <!-- focusin -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-focusin">
-            <a class="eventtype noxref" href="#event-type-focusIn"><code>focusin</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusIn</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> attribute is is the <a class="def" href="#glossary-event-target">event target</a> receiving focus, and the value of the <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attribute is the <a class="def" href="#glossary-event-target">event target</a> losing focus (if any).</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about to receive focus. This event type must be dispatched before the element is given focus.  The <a class="def" href="#glossary-event-target">event target</a> must be the element which is about to receive focus.  This event type is similar to <a class="eventtype" href="#event-type-focus"><code>focus</code></a>, but is dispatched before focus is shifted, and does bubble..
+          <dt id="event-type-focusin"><dfn>
+              <a class="eventtype" href="#event-type-focusIn"><code>focusin</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusIn</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> attribute is is the <a class="def" href="#glossary-event-target">event target</a> receiving focus, and the value of the <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attribute is the <a class="def" href="#glossary-event-target">event target</a> losing focus (if any).</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about to receive focus. This event type must be dispatched before the element is given focus.  The <a class="def" href="#glossary-event-target">event target</a> must be the element which is about to receive focus.  This event type is similar to <a class="eventtype" href="#event-type-focus"><code>focus</code></a>, but is dispatched before focus is shifted, and does bubble.</p>
             <p class="note"><strong>Note:</strong> When using this event type, the author may use the event's <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attribute (or a host-language-specific method or means) to get the currently focused element before the focus shifts to the next focus <a class="def" href="#glossary-event-target">event target</a>, thus having optional access to both the element losing focus and the element gaining focus without the use of the <a class="eventtype" href="#event-type-blur"><code>blur</code></a> or <a class="eventtype" href="#event-type-focusout">focusout</a> event types.</p>
           </dd>
         </dl>
@@ -2579,25 +2311,32 @@
 <!-- focusout -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-focusout">
-            <a class="eventtype noxref" href="#event-type-focusOut"><code>focusout</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusOut</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> attribute is is the <a class="def" href="#glossary-event-target">event target</a> losing focus, and the value of the <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attribute is the <a class="def" href="#glossary-event-target">event target</a> receiving focus.</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about to lose focus. This event type must be dispatched before the element loses focus.  The <a class="def" href="#glossary-event-target">event target</a> must be the element which is about to lose focus.  This event type is similar to <a class="eventtype" href="#event-type-blur"><code>blur</code></a>, but is dispatched before focus is shifted, and does bubble..
+          <dt id="event-type-focusout"><dfn>
+              <a class="eventtype" href="#event-type-focusOut"><code>focusout</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusOut</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> is in use.  The value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> attribute is is the <a class="def" href="#glossary-event-target">event target</a> losing focus, and the value of the <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attribute is the <a class="def" href="#glossary-event-target">event target</a> receiving focus.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about to lose focus. This event type must be dispatched before the element loses focus.  The <a class="def" href="#glossary-event-target">event target</a> must be the element which is about to lose focus.  This event type is similar to <a class="eventtype" href="#event-type-blur"><code>blur</code></a>, but is dispatched before focus is shifted, and does bubble.</p>
           </dd>
         </dl>
       </div>
     </div>
-    <!-- interface events-focusevents -->
-  
-  
-    
+<!-- interface events-focusevents -->
 <!-- interface events-mouseevents -->
-    <div class="div3">
-      <h3 class="div3"><a id="events-mouseevents" href="#events-mouseevents">5.2.3 Mouse Event Types</a></h3>
+    <div>
+      <h3><a id="events-mouseevents" href="#events-mouseevents">5.2.3 Mouse Event Types</a></h3>
+
       <p>This module defines the feature MouseEvents 3.0 and depends on the feature UIEvents 3.0.</p>
-      <p>The Mouse event module originates from the [<cite><a class="noxref informative" href="#references-HTML40">HTML 4.01</a></cite>] <code>onclick</code>, <code>ondblclick</code>, <code>onmousedown</code>, <code>onmouseup</code>, <code>onmouseover</code>, <code>onmousemove</code>, and <code>onmouseout</code> attributes. This event module is specifically designed for use with pointing input devices, such as a mouse or a trackball.</p>
-
+      <p>The Mouse event module originates from the [<cite><a class="informative" href="#references-HTML40">HTML 4.01</a></cite>] <code>onclick</code>, <code>ondblclick</code>, <code>onmousedown</code>, <code>onmouseup</code>, <code>onmouseover</code>, <code>onmousemove</code>, and <code>onmouseout</code> attributes. This event module is specifically designed for use with pointing input devices, such as a mouse or a trackball.</p>
       <dl>
         <dt><strong>Interface <em><a id="events-Events-MouseEvent">MouseEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
         <dd>
@@ -2613,53 +2352,52 @@
             <dd>
               <div class="idl-code">
                 <pre>
-  // Modified in DOM Level 3:
-  interface <a href="#events-Events-MouseEvent">MouseEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
-    readonly attribute long            <a href="#events-Events-MouseEvent-screenX">screenX</a>;
-    readonly attribute long            <a href="#events-Events-MouseEvent-screenY">screenY</a>;
-    readonly attribute long            <a href="#events-Events-MouseEvent-clientX">clientX</a>;
-    readonly attribute long            <a href="#events-Events-MouseEvent-clientY">clientY</a>;
-    readonly attribute boolean         <a href="#events-Events-MouseEvent-ctrlKey">ctrlKey</a>;
-    readonly attribute boolean         <a href="#events-Events-MouseEvent-shiftKey">shiftKey</a>;
-    readonly attribute boolean         <a href="#events-Events-MouseEvent-altKey">altKey</a>;
-    readonly attribute boolean         <a href="#events-Events-MouseEvent-metaKey">metaKey</a>;
-    readonly attribute unsigned short  <a href="#events-Events-MouseEvent-button">button</a>;  
-    readonly attribute unsigned short  <a href="#events-Events-MouseEvent-buttons">buttons</a>;
-    readonly attribute <a href="#events-Events-EventTarget">EventTarget</a>     <a href="#events-Events-MouseEvent-relatedTarget">relatedTarget</a>;
-    void               <a href="#events-event-type-initMouseEvent">initMouseEvent</a>(in DOMString typeArg, 
-                                  in boolean canBubbleArg, 
-                                  in boolean cancelableArg, 
-                                  in views::AbstractView viewArg, 
-                                  in long detailArg, 
-                                  in long screenXArg, 
-                                  in long screenYArg, 
-                                  in long clientXArg, 
-                                  in long clientYArg, 
-                                  in boolean ctrlKeyArg, 
-                                  in boolean altKeyArg, 
-                                  in boolean shiftKeyArg, 
-                                  in boolean metaKeyArg, 
-                                  in unsigned short buttonArg, 
-                                  in unsigned short buttonsArg, 
-                                  in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
-    // Introduced in DOM Level 3:
-    boolean            <a href="#events-Events-MouseEvent-getModifierState">getModifierState</a>(in DOMString keyArg);
-  };
-  </pre>
+// Modified in DOM Level 3:
+interface <a href="#events-Events-MouseEvent">MouseEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
+  readonly attribute long            <a href="#events-Events-MouseEvent-screenX">screenX</a>;
+  readonly attribute long            <a href="#events-Events-MouseEvent-screenY">screenY</a>;
+  readonly attribute long            <a href="#events-Events-MouseEvent-clientX">clientX</a>;
+  readonly attribute long            <a href="#events-Events-MouseEvent-clientY">clientY</a>;
+  readonly attribute boolean         <a href="#events-Events-MouseEvent-ctrlKey">ctrlKey</a>;
+  readonly attribute boolean         <a href="#events-Events-MouseEvent-shiftKey">shiftKey</a>;
+  readonly attribute boolean         <a href="#events-Events-MouseEvent-altKey">altKey</a>;
+  readonly attribute boolean         <a href="#events-Events-MouseEvent-metaKey">metaKey</a>;
+  readonly attribute unsigned short  <a href="#events-Events-MouseEvent-button">button</a>;  
+  readonly attribute unsigned short  <a href="#events-Events-MouseEvent-buttons">buttons</a>;
+  readonly attribute <a href="#events-Events-EventTarget">EventTarget</a>     <a href="#events-Events-MouseEvent-relatedTarget">relatedTarget</a>;
+  void               <a href="#events-event-type-initMouseEvent">initMouseEvent</a>(in DOMString typeArg, 
+                                in boolean canBubbleArg, 
+                                in boolean cancelableArg, 
+                                in views::AbstractView viewArg, 
+                                in long detailArg, 
+                                in long screenXArg, 
+                                in long screenYArg, 
+                                in long clientXArg, 
+                                in long clientYArg, 
+                                in boolean ctrlKeyArg, 
+                                in boolean altKeyArg, 
+                                in boolean shiftKeyArg, 
+                                in boolean metaKeyArg, 
+                                in unsigned short buttonArg, 
+                                in unsigned short buttonsArg, 
+                                in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
+  // Introduced in DOM Level 3:
+  boolean            <a href="#events-Events-MouseEvent-getModifierState">getModifierState</a>(in DOMString keyArg);
+};
+                </pre>
               </div>
               <br />
             </dd>
-            <dt>
-              <strong>Attributes</strong>
-            </dt>
+
+            <dt><strong>Attributes</strong></dt>
             <dd>
               <dl>
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-altKey">altKey</a></code> of type <code>boolean</code>, readonly</dt>
                 <dd>Refer to the <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a> attribute.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-button">button</a></code> of type <code>unsigned short</code>, readonly</dt>
                 <dd>During mouse events caused by the depression or release of a mouse button, <code>button</code> shall be used to indicate which pointer device button changed state. <code>0</code> must indicate the primary button of the device (in general, the left button  or the only button on single-button devices, used to activate a user interface control or select text). <code>2</code> must indicate the secondary button (in general, the right button, often used to display a context menu). <code>1</code> must indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).  Some mice may provide or simulate more buttons, and values higher than <code>2</code> may be used to represent such buttons.<br /></dd>
-                
-                
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-buttons">buttons</a></code> of type <code>unsigned short</code>, readonly</dt>
                 <dd>During mouse events caused by the depression or release of a mouse button, <code>buttons</code> shall be used to indicate which combination of mouse buttons are currently being pressed, expressed as a bitmask.  <span class="note"><strong>Note:</strong> This should not be confused with the <a href="#events-Events-MouseEvent-button">button</a> attribute.</span>
                 <code>0</code> must indicates no button is currently active.
@@ -2668,37 +2406,42 @@
                 <code>4</code> must indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).
                 Some pointer devices may provide or simulate more buttons.  To represent such buttons, the value must be doubled for each successive button (in the binary series <code>8</code>, <code>16</code>, <code>32</code>, ... ), and the buttons should alternate sides of the device, from left to right.  For example, with a 5-button mouse, the primary button (on the left) would have the value <code>1</code>, the secondary button (on the right) would have the value <code>2</code>, the auxiliary button (in the middle) would have the value <code>4</code>, the fourth button (on the left) would have the value <code>8</code>, and the fifth button (on the right) would have the value <code>16</code>.  Because the sum of any set of button values is a unique number, an author can use a bitwise operation to determine how many buttons are currently being pressed and which buttons they are, for an arbitrary number of mouse buttons on a device, e.g. the value <code>3</code> indicates that the left and right button are currently both pressed, while the value <code>5</code> indicates that the left and middle button are currently both pressed.                  
                 </dd>
-                
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-clientX">clientX</a></code> of type <code>long</code>, readonly</dt>
                 <dd>The horizontal coordinate at which the event occurred relative to the viewport associated with the event.<br /></dd>
-                
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-clientY">clientY</a></code> of type <code>long</code>, readonly</dt>
                 <dd>The vertical coordinate at which the event occurred relative to the viewport associated with the event.<br /></dd>
-                
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-ctrlKey">ctrlKey</a></code> of type <code>boolean</code>, readonly</dt>
                 <dd>Refer to the <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a> attribute.<br /></dd>
-                
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-metaKey">metaKey</a></code> of type <code>boolean</code>, readonly</dt>
                 <dd>Refer to the <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a> attribute.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-relatedTarget">relatedTarget</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
                 <dd>Used to identify a secondary <a href="#events-Events-EventTarget"><code>EventTarget</code></a> related to a UI event, depending on the type of event.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-screenX">screenX</a></code> of type <code>long</code>, readonly</dt>
                 <dd>The horizontal coordinate at which the event occurred relative to the origin of the screen coordinate system.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-screenY">screenY</a></code> of type <code>long</code>, readonly</dt>
                 <dd>The vertical coordinate at which the event occurred relative to the origin of the screen coordinate system.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-MouseEvent-shiftKey">shiftKey</a></code> of type <code>boolean</code>, readonly</dt>
                 <dd>Refer to the <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a> attribute.<br /></dd>
+
               </dl>
             </dd>
-            <dt>
-              <strong>Methods</strong>
-            </dt>
+
+            <dt><strong>Methods</strong></dt>
             <dd>
               <dl>
                 <dt><code class="method-name"><a id="events-Events-MouseEvent-getModifierState">getModifierState</a></code> introduced in <strong class="since">DOM Level 3</strong></dt>
                 <dd>
                   <div class="method">Queries the state of a modifier using a key value. See also <a href="#keyset-Modifiers">Modifier keys</a>.
-  <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-Events-KeyboardEvent-getModifierState"><code>KeyboardEvent.getModifierState()</code></a> method for a description of this parameter.<br /></dd></dl></div></div>
+  <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-Events-KeyboardEvent-getModifierState"><code>KeyboardEvent.getModifierState()</code></a> method for a description of this parameter.<br /></dd>
+</dl></div></div>
                     <!-- parameters -->
                     <div class="return"><strong>Return Value</strong><div class="returntable"><table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr class="assert must"><td><p><code>boolean</code></p></td><td><p><code>true</code> if it is a modifier key and the modifier is activated, <code>false</code> otherwise.</p></td></tr></table></div></div>
                     <!-- return -->
@@ -2706,6 +2449,7 @@
                   </div>
 <!-- method -->
                 </dd>
+
                 <dt>
                   <code class="method-name">
                     <a id="events-event-type-initMouseEvent">initMouseEvent</a>
@@ -2713,9 +2457,25 @@
                 </dt>
                 <dd>
                   <div class="method">Initializes attributes of a <code>MouseEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>.
-  <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">screenXArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>.<br /></dd><dt><code class="parameter-name">screenYArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>.<br /></dd><dt><code class="parameter-name">clientXArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>.<br /></dd><dt><code class="parameter-name">clientYArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>.<br /></dd><dt><code class="parameter-name">ctrlKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>.<br /></dd><dt><code class="parameter-name">altKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>.<br /></dd><dt><code class="parameter-name">shiftKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>.<br /></dd><dt><code class="parameter-name">metaKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>.<br /></dd><dt><code class="parameter-name">buttonArg</code> of type <code>unsigned short</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>.<br /></dd><dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt><dd>Specifies <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a>. This value may be <code>null</code>.<br /></dd></dl></div></div>
+  <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">screenXArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>.<br /></dd>
+<dt><code class="parameter-name">screenYArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>.<br /></dd>
+<dt><code class="parameter-name">clientXArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>.<br /></dd>
+<dt><code class="parameter-name">clientYArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>.<br /></dd>
+<dt><code class="parameter-name">ctrlKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>.<br /></dd>
+<dt><code class="parameter-name">altKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>.<br /></dd>
+<dt><code class="parameter-name">shiftKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>.<br /></dd>
+<dt><code class="parameter-name">metaKeyArg</code> of type <code>boolean</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>.<br /></dd>
+<dt><code class="parameter-name">buttonArg</code> of type <code>unsigned short</code></dt><dd>Specifies <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>.<br /></dd>
+<dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt><dd>Specifies <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a>. This value may be <code>null</code>.<br /></dd>
+</dl></div></div>
                     <!-- parameters -->
                     <div><strong>No Return Value</strong></div>
+
                     <div><strong>No Exceptions</strong></div>
                   </div>
 <!-- method -->
@@ -2729,93 +2489,157 @@
       <p id="events-dt-current-click-count">Implementations must maintain the <em>current click count</em> when generating mouse events. This shall be a non-negative integer indicating the number of consecutive clicks of a pointing device button during a user action. The notion of consecutive clicks depends on the environment configuration. For example, a <code><a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a></code> event type might not happen if there is a long delay between the two clicks.
       <span class="note"><strong>Note:</strong> The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> for a number of clicks greater than 2 is platform-dependent.  For example, on the Windows OS, the click-count series seems to be <code>1, 2, 3, 2, 3</code>, while on MacOS, the click-count series seems to be <code>1, 2, 3, 4, 5, ...</code>.</span></p>
 <!-- click -->
-
-
-    <h4 class="div3 needswork"><a id="events-mouseevent-event-order" href="#events-mouseevent-event-order">5.2.3.2 Mouse Event Order</a></h4>
-    <p>Certain mouse events defined in this specification occur in a set order relative to one another.  The following is the typical sequence of events when a pointing device's cursor is moved over an element:</p>
-    <ol>
-      <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a></li>
-      <li><a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a></li>
-      <li><a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a></li>
-      <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (multiple events)</li>
-      <li><a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a></li>
-      <li><a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a></li>
-    </ol>
-
-    <p>The following is the typical sequence of events when a button associated with a pointing device (e.g., a mouse button or trackpad) is pressed and released over an element:</p>
-    <ol>
-      <li><a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a></li>
-      <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (optional, multiple events, some limits)</li>
-      <li><a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a></li>
-      <li><a class="eventtype" href="#event-type-click"><code>click</code></a></li>
-      <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (optional, multiple events, some limits)</li>
-      <li><a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a></li>
-      <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (optional, multiple events, some limits)</li>
-      <li><a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a></li>
-      <li><a class="eventtype" href="#event-type-click"><code>click</code></a></li>
-      <li><a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a></li>
-    </ol>
-
-    <p>Note that the lag time, degree, distance, and number of <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> events allowed between the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events while still firing a <a class="eventtype" href="#event-type-click"><code>click</code></a> or <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event shall be implementation-, device-, and platform-specific.  Each implementation should determine the appropriate hysteresis tolerance, but in general should fire <a class="eventtype" href="#event-type-click"><code>click</code></a> and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> events when the event target of the associated <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events is the same element with no <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> or <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a> events intervening, and should not fire <a class="eventtype" href="#event-type-click"><code>click</code></a> and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> events when the event target of the associated <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events is different.</p>
+      <h4 class="needswork">
+        <a id="events-mouseevent-event-order" href="#events-mouseevent-event-order">5.2.3.2 Mouse Event Order</a>
+      </h4>
+      <p>Certain mouse events defined in this specification occur in a set order relative to one another.  The following is the typical sequence of events when a pointing device's cursor is moved over an element:</p>
+      <ol>
+        <li>
+          <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>
+        </li>
+        <li>
+          <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>
+        </li>
+        <li>
+          <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a>
+        </li>
+        <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (multiple events)</li>
+        <li>
+          <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a>
+        </li>
+        <li>
+          <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>
+        </li>
+      </ol>
+      <p>The following is the typical sequence of events when a button associated with a pointing device (e.g., a mouse button or trackpad) is pressed and released over an element:</p>
+      <ol>
+        <li>
+          <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>
+        </li>
+        <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (optional, multiple events, some limits)</li>
+        <li>
+          <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>
+        </li>
+        <li>
+          <a class="eventtype" href="#event-type-click"><code>click</code></a>
+        </li>
+        <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (optional, multiple events, some limits)</li>
+        <li>
+          <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>
+        </li>
+        <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (optional, multiple events, some limits)</li>
+        <li>
+          <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>
+        </li>
+        <li>
+          <a class="eventtype" href="#event-type-click"><code>click</code></a>
+        </li>
+        <li>
+          <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>
+        </li>
+      </ol>
+      <p>Note that the lag time, degree, distance, and number of <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> events allowed between the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events while still firing a <a class="eventtype" href="#event-type-click"><code>click</code></a> or <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event shall be implementation-, device-, and platform-specific.  Each implementation should determine the appropriate hysteresis tolerance, but in general should fire <a class="eventtype" href="#event-type-click"><code>click</code></a> and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> events when the event target of the associated <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events is the same element with no <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> or <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a> events intervening, and should not fire <a class="eventtype" href="#event-type-click"><code>click</code></a> and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> events when the event target of the associated <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events is different.</p>
 
 <!-- click -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-click">
-            <a class="eventtype noxref" href="#event-type-click"><code>click</code></a>
-          </dt>
-          <dd><p><!-- <a class="def" href="#glossary-topmost-event-target">topmost event target</a> --><!-- || Are you asking for the spec to say something along the lines of, "The 
-                || 'click' event is fired when the user presses a button on the pointer 
-                || device, or otherwise activates the pointer in a manner that simulates 
-                || such an action." Or something more abstract (or more concrete)?
-                Something like that, maybe a little more concrete, e.g. "When the user 
-                presses a button on the pointer device, a 'mousedown' event MUST be 
-                dispatched at the element that is rendered at the highest z-order position 
-                below the current pointer position, with the event set having the 
-                following values: [...]" followed by the default action being to fire 
-                'mouseup' or 'click' or whatever, with the same detail for that, and also 
-                with rules for how to handle mouseover, mouseenter, mouseleave, etc. Same 
-                for keyboards, mousewheels, etc. Basically any user interaction event. --></p><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>click</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a>. The attribute value shall be <code>1</code> when the user begins this action and increments by <code>1</code> for each click.</td></tr></table>
-                <!-- A pointing device button is clicked over an element. The definition of a click depends on the environment configuration; i.e. it may depend on the screen location or the delay between the press and release of the pointing device button. In any case, the event target must be the same between the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-click"><code>click</code></a>. The sequence of these events is: <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-click"><code>click</code></a>. It depends on the environment configuration whether the event type <a class="eventtype" href="#event-type-click"><code>click</code></a> can occur if one or more of the event types <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>, and <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> occur between the press and release of the pointing device button. In addition, the event type is dispatched as described in <a href="#event-flow-activation">Activation triggers and behavior</a>. -->
-                The <a class="eventtype" href="#event-type-click"><code>click</code></a> event must be dispatched on the <a class="def" href="#glossary-topmost-event-target">topmost event target</a> indicated by the pointer, when the user presses down and releases the pointer button, or otherwise activates the pointer in a manner that simulates such an action.  Activation of the button may depend upon the pointer device and the environment configuration, e.g. it may depend on the screen location or the delay between the press and release of the pointing device button.  The <a class="eventtype" href="#event-type-click"><code>click</code></a> event may be preceded by the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events on the same element.  Depending upon the environment configuration, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event may be dispatched if one or more of the event types <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>, and <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> occur between the press and release of the pointing device button.  The <a class="eventtype" href="#event-type-click"><code>click</code></a> event may also be followed by the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event.  The <a class="eventtype" href="#event-type-click"><code>click</code></a> event type must be dispatched as described in <a href="#event-flow-activation">Activation triggers and behavior</a>.
-            </dd>
+          <dt id="event-type-click"><dfn>
+              <a class="eventtype" href="#event-type-click"><code>click</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>click</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Default action</th><td><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a>. The attribute value shall be <code>1</code> when the user begins this action and increments by <code>1</code> for each click.</td></tr>
+            </table>
+            <p>The <a class="eventtype" href="#event-type-click"><code>click</code></a> event must be dispatched on the <a class="def" href="#glossary-topmost-event-target">topmost event target</a> indicated by the pointer, when the user presses down and releases the pointer button, or otherwise activates the pointer in a manner that simulates such an action.  Activation of the button may depend upon the pointer device and the environment configuration, e.g. it may depend on the screen location or the delay between the press and release of the pointing device button.  The <a class="eventtype" href="#event-type-click"><code>click</code></a> event may be preceded by the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events on the same element.  Depending upon the environment configuration, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event may be dispatched if one or more of the event types <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>, and <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> occur between the press and release of the pointing device button.  The <a class="eventtype" href="#event-type-click"><code>click</code></a> event may also be followed by the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event.  The <a class="eventtype" href="#event-type-click"><code>click</code></a> event type must be dispatched as described in <a href="#event-flow-activation">Activation triggers and behavior</a>.</p>
+<!-- <a class="def" href="#glossary-topmost-event-target">topmost event target</a> -->
+<!-- || Are you asking for the spec to say something along the lines of, "The 
+                  || 'click' event is fired when the user presses a button on the pointer 
+                  || device, or otherwise activates the pointer in a manner that simulates 
+                  || such an action." Or something more abstract (or more concrete)?
+                  Something like that, maybe a little more concrete, e.g. "When the user 
+                  presses a button on the pointer device, a 'mousedown' event MUST be 
+                  dispatched at the element that is rendered at the highest z-order position 
+                  below the current pointer position, with the event set having the 
+                  following values: [...]" followed by the default action being to fire 
+                  'mouseup' or 'click' or whatever, with the same detail for that, and also 
+                  with rules for how to handle mouseover, mouseenter, mouseleave, etc. Same 
+                  for keyboards, mousewheels, etc. Basically any user interaction event. -->
+<!-- A pointing device button is clicked over an element. The definition of a click depends on the environment configuration; i.e. it may depend on the screen location or the delay between the press and release of the pointing device button. In any case, the event target must be the same between the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-click"><code>click</code></a>. The sequence of these events is: <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-click"><code>click</code></a>. It depends on the environment configuration whether the event type <a class="eventtype" href="#event-type-click"><code>click</code></a> can occur if one or more of the event types <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>, and <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> occur between the press and release of the pointing device button. In addition, the event type is dispatched as described in <a href="#event-flow-activation">Activation triggers and behavior</a>. -->
+          </dd>
         </dl>
       </div>
 
 <!-- dblclick -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-dblclick">
-            <a class="eventtype noxref" href="#event-type-dblclick"><code>dblclick</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>dblclick</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a>.</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device button is clicked twice over an element. The definition of a double click depends on the environment configuration, except that the event target must be the same between <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>. This event type must be dispatched after the event type <a class="eventtype" href="#event-type-click"><code>click</code></a> if a click and double click occur simultaneously, and after the event type <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> otherwise.
-            <p class="note"><strong>Note:</strong> Canceling the <a class="eventtype" href="#event-type-click"><code>click</code></a> event must not not affect the firing of a <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event.</p></dd>
+          <dt id="event-type-dblclick"><dfn>
+              <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>dblclick</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a>.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device button is clicked twice over an element. The definition of a double click depends on the environment configuration, except that the event target must be the same between <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>. This event type must be dispatched after the event type <a class="eventtype" href="#event-type-click"><code>click</code></a> if a click and double click occur simultaneously, and after the event type <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> otherwise.</p>
+            <p class="note"><strong>Note:</strong> Canceling the <a class="eventtype" href="#event-type-click"><code>click</code></a> event must not not affect the firing of a <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event.</p>
+          </dd>
         </dl>
       </div>
 
 <!-- mousedown -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-mousedown">
-            <a class="eventtype noxref" href="#event-type-mousedown"><code>mousedown</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mousedown</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one. For example, if no click happened before the mousedown, <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> must contain the value <code>1</code>.</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device button is pressed over an element.</dd>
+          <dt id="event-type-mousedown"><dfn>
+              <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mousedown</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one. For example, if no click happened before the mousedown, <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> must contain the value <code>1</code>.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device button is pressed over an element.</p>
+          </dd>
         </dl>
       </div>
 
 <!-- mouseenter -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-mouseenter">
-            <a class="eventtype noxref" href="#event-type-mouseenter"><code>mouseenter</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseenter</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</td></tr></table>
-            
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved onto the boundaries of an element or one of its descendent elements.  This event type is similar to <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, but differs in that it does not bubble, and must not be dispatched when the pointer device moves from an element onto the boundaries of one of its descendent elements.
-
-            <p class="note"><strong>Note:</strong> This is the event type equivalent of the CSS <a href="http://www.w3.org/TR/CSS2/selector.html#dynamic-pseudo-classes" title="Selectors"><code>:hover</code> pseudo-class</a> <a href="#references-CSS2">[CSS2]</a>.  See also the <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a> event type.</p>
+          <dt id="event-type-mouseenter"><dfn>
+              <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseenter</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved onto the boundaries of an element or one of its descendent elements.  This event type is similar to <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, but differs in that it does not bubble, and must not be dispatched when the pointer device moves from an element onto the boundaries of one of its descendent elements.</p>
+            <p class="note"><strong>Note:</strong> This is the event type equivalent of the CSS <a href="http://www.w3.org/TR/CSS2/selector.html#dynamic-pseudo-classes" title="Selectors"><code>:hover</code> pseudo-class</a><a href="#references-CSS2">[CSS2]</a>.  See also the <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a> event type.</p>
           </dd>
         </dl>
       </div>
@@ -2823,14 +2647,22 @@
 <!-- mouseleave -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-mouseleave">
-            <a class="eventtype noxref" href="#event-type-mouseleave"><code>mouseleave</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseout</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>No</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</td></tr></table>
-
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved off of the boundaries of an element and all of its descendent elements.  This event type is similar to <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a>, but differs in that does not bubble, and that it must not be dispatched until the pointing device has left the boundaries of the element and the boundaries of all of its children.            
-            
-            <p class="note"><strong>Note:</strong> This is the event type equivalent of the CSS <a href="http://www.w3.org/TR/CSS2/selector.html#dynamic-pseudo-classes" title="Selectors"><code>:hover</code> pseudo-class</a> <a href="#references-CSS2">[CSS2]</a>.  See also the <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a> event type.</p>
+          <dt id="event-type-mouseleave"><dfn>
+              <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseout</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved off of the boundaries of an element and all of its descendent elements.  This event type is similar to <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a>, but differs in that does not bubble, and that it must not be dispatched until the pointing device has left the boundaries of the element and the boundaries of all of its children.</p>
+            <p class="note"><strong>Note:</strong> This is the event type equivalent of the CSS <a href="http://www.w3.org/TR/CSS2/selector.html#dynamic-pseudo-classes" title="Selectors"><code>:hover</code> pseudo-class</a><a href="#references-CSS2">[CSS2]</a>.  See also the <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a> event type.</p>
           </dd>
         </dl>
       </div>
@@ -2838,24 +2670,43 @@
 <!-- mousemove -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-mousemove">
-            <a class="eventtype noxref" href="#event-type-mousemove"><code>mousemove</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mousemove</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use.</td></tr></table>
-
-     A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved while it is over an element.  The frequency rate of events while the pointing device is moved shall be implementation-, device-, and platform-specific, but multiple consecutive <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> events should be fired for sustained pointer-device movement, rather than a single event for each instance of mouse movement.  Implementations are encouraged to determine the optimal frequency rate to balance responsiveness with performance.</dd>
+          <dt id="event-type-mousemove"><dfn>
+              <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mousemove</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved while it is over an element.  The frequency rate of events while the pointing device is moved shall be implementation-, device-, and platform-specific, but multiple consecutive <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> events should be fired for sustained pointer-device movement, rather than a single event for each instance of mouse movement.  Implementations are encouraged to determine the optimal frequency rate to balance responsiveness with performance.</p>
+          </dd>
         </dl>
       </div>
 
 <!-- mouseout -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-mouseout">
-            <a class="eventtype noxref" href="#event-type-mouseout"><code>mouseout</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseout</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved off of the boundaries of an element.  This event type is similar to <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>, but differs in that does bubble, and that it must be dispatched when the pointer device moves from an element onto the boundaries of one of its descendent elements.
-            
+          <dt id="event-type-mouseout"><dfn>
+              <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseout</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved off of the boundaries of an element.  This event type is similar to <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>, but differs in that does bubble, and that it must be dispatched when the pointer device moves from an element onto the boundaries of one of its descendent elements.</p>
             <p class="note"><strong>Note:</strong> See also the <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a> event type.</p>
           </dd>
         </dl>
@@ -2864,13 +2715,23 @@
 <!-- mouseover -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-mouseover">
-            <a class="eventtype noxref" href="#event-type-mouseover"><code>mouseover</code></a>
-          </dt>
-          <dd><table summary="This table contains information about the semantics of the given event type" border="0" cellpadding="2" cellspacing="0"><tbody><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseover</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</td></tr></tbody></table>
-            
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved onto the boundaries of an element.  This event type is similar to <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a>, but differs in that does bubble, and that it must be dispatched when the pointer device moves onto the boundaries of an element whose ancestor element is the <a class="def" href="#glossary-event-target">event target</a> for the same event listener instance.
-            
+          <dt id="event-type-mouseover"><dfn>
+              <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>
+            </dfn></dt>
+          <dd>
+            <table summary="This table contains information about the semantics of the given event type" border="0" cellpadding="2" cellspacing="0">
+              <tbody>
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseover</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</td></tr>
+              </tbody>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device is moved onto the boundaries of an element.  This event type is similar to <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a>, but differs in that does bubble, and that it must be dispatched when the pointer device moves onto the boundaries of an element whose ancestor element is the <a class="def" href="#glossary-event-target">event target</a> for the same event listener instance.</p>
             <p class="note"><strong>Note:</strong> See also the <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> event type.</p>
           </dd>
         </dl>
@@ -2879,110 +2740,32 @@
 <!-- mouseup -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-mouseup">
-            <a class="eventtype noxref" href="#event-type-mouseup"><code>mouseup</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseup</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one.</td></tr></table>
-
-     A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device button is released over an element.</dd>
+          <dt id="event-type-mouseup"><dfn>
+              <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseup</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Default action</th><td>none</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. The <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> attribute indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device button is released over an element.</p>
+          </dd>
         </dl>
       </div>
     </div>
 <!-- div2 Events-eventgroupings -->
-
-
-
-<!-- div3 Events-eventgroupings-wheelevents -->
-    <!-- <div class="div3">
-      <h3 class="div3"><a id="events-mousewheelevents" href="#events-mousewheelevents">5.2.4 Mouse Wheel Event Types</a></h3>
-      <p>This module defines the feature MouseWheelEvents 3.0 and depends on the feature MouseEvents 3.0.</p>
-      <p class="warning"><strong>Warning!</strong> the <a href="#events-Events-MouseWheelEvent">MouseWheelEvent interface</a> is defined in this specification for reference and completeness of legacy behavior, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this interface in favor of the related <a href="#events-Events-WheelEvent">WheelEvent interface</a>.</p>
-
-      <dl>
-        <dt><strong>Interface <em><a id="events-Events-MouseWheelEvent">MouseWheelEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
-        <dd>
-          <p>The <code>MouseWheelEvent</code> interface provides specific contextual information associated with mouse wheel events.</p>
-          <p>To create an instance of the <code>MouseWheelEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("MouseWheelEvent")</code></a> method call.</p>
-          <dl>
-            <dt>
-              <br />
-              <strong>IDL Definition</strong>
-            </dt>
-            <dd>
-              <div class="idl-code">
-                <pre>
-        // Introduced in DOM Level 3:
-        interface <a href="#events-Events-MouseWheelEvent">MouseWheelEvent</a> : <a href="#events-Events-MouseEvent">MouseEvent</a> {
-          readonly attribute long            <a href="#events-Events-MouseWheelEvent-wheelDelta">wheelDelta</a>;
-          void               <a href="#events-event-type-initMouseWheelEvent">initMouseWheelEvent</a>(in DOMString typeArg, 
-                                                                 in boolean canBubbleArg, 
-                                                                 in boolean cancelableArg, 
-                                                                 in views::AbstractView viewArg, 
-                                                                 in long detailArg, 
-                                                                 in long screenXArg, 
-                                                                 in long screenYArg, 
-                                                                 in long clientXArg, 
-                                                                 in long clientYArg, 
-                                                                 in unsigned short buttonArg, 
-                                                                 in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg, 
-                                                                 in DOMString modifiersListArg, 
-                                                                 in long wheelDeltaArg);
-        };
-        </pre>
-              </div>
-              <br />
-            </dd>
-            <dt>
-              <strong>Attributes</strong>
-            </dt>
-            <dd>
-              <dl>
-                <dt><code class="attribute-name"><a id="events-Events-MouseWheelEvent-wheelDelta">wheelDelta</a></code> of type <code>long</code>, readonly</dt>
-                <dd>The distance the wheel has rotated around the y-axis.  Because this is a legacy event type, the units or number of these units in <code>wheelDelta</code> are implementation-specific.<br /></dd>
-              </dl>
-            </dd>
-            <dt>
-              <strong>Methods</strong>
-            </dt>
-            <dd>
-              <dl>
-                <dt><code class="method-name"><a id="events-event-type-initMouseWheelEvent">initMouseWheelEvent</a></code> introduced in <strong class="since">DOM Level 3</strong></dt>
-                <dd>
-                  <div class="method">Initializes attributes of a <code>MouseWheelEvent</code> object. This method has the same behavior as <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a>.
-                          <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">screenXArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">screenYArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">clientXArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">clientYArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">buttonArg</code> of type <code>unsigned short</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">modifiersListArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">wheelDeltaArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-MouseWheelEvent-wheelDelta"><code>MouseWheelEvent.wheelDelta</code></a>.<br /></dd></dl></div></div>
-                          <div><strong>No Return Value</strong></div>
-                          <div><strong>No Exceptions</strong></div>
-                        </div>
-                </dd>
-              </dl>
-            </dd>
-          </dl>
-        </dd>
-      </dl>
-
-      <div class="event-definition assert must">
-        <dl>
-          <dt id="event-type-mousewheel">
-            <a class="eventtype noxref" href="#event-type-mousewheel"><code>mousewheel</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mousewheel</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseWheelEvent"><code>MouseWheelEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>scroll (or zoom) the document</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-MouseWheelEvent-wheelDelta"><code>MouseWheelEvent.wheelDelta</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, and <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> are in use if the wheel is associated to a pointing device. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> the pointing device is pointing at, if any. <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> is not in use.</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a mouse wheel has been rotated around the y-axis, or when an equivalent input device (such as a mouse-ball, certain tablets or touchpads, etc.) has emulated such an action. 
-            <p>The typical default action of the <a class="eventtype" href="#event-type-mousewheel"><code>mousewheel</code></a> event type is to scroll (or in some cases, zoom) the document by the indicated amount.  If this event is canceled, the implementation must not scroll or zoom the document (or perform whatever other implementation-specific default action is associated with this event type).</p>
-            <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-mousewheel"><code>mousewheel</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the related <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event type.</p>
-          </dd>
-        </dl>
-      </div>
-    </div> -->
-<!-- div3 Events-eventgroupings-mousewheelevents -->
-
-
-
 <!-- div3 Events-eventgroupings-mouseevents -->
-    <div class="div3">
-      <h3 class="div3"><a id="events-wheelevents" href="#events-wheelevents">5.2.4 Wheel Event Types</a></h3>
+    <div>
+      <h3><a id="events-wheelevents" href="#events-wheelevents">5.2.4 Wheel Event Types</a></h3>
+
       <p>This module defines the feature WheelEvents 3.0 and depends on the feature MouseEvents 3.0.</p>
       <p>Wheels are devices that can be rotated in one or more spatial dimensions, and which may or may not be associated with a pointer device. The coordinate system depends on the environment configuration. As an example, the environment may be configured to associate vertical scrolling with rotation along the y-axis, horizontal scrolling with rotation along the x-axis, and zooming with rotation along the z-axis.  The deltax, deltaY, and deltaX attributes of <a href="#events-Events-WheelEvent"><code>WheelEvent</code></a> objects indicate the distance of the rotation, as specified in the <a class="def" href="#glossary-delta">delta</a> definition. <!--The delta attributes of <a href='#events-Events-WheelEvent'><code>WheelEvent</code></a> objects indicate the distance of the rotation. The measurement unit depends on the environment configuration. The sign of the delta value should indicate the direction of the rotation.--></p>
-
       <dl>
         <dt><strong>Interface <em><a id="events-Events-WheelEvent">WheelEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
         <dd>
@@ -2996,109 +2779,115 @@
             <dd>
               <div class="idl-code">
                 <pre>
-        // Introduced in DOM Level 3:
-        interface <a href="#events-Events-WheelEvent">WheelEvent</a> : <a href="#events-Events-MouseEvent">MouseEvent</a> {
-
-          // DeltaModeCode
-          const unsigned long       <a href="#events-DOM_DELTA_PIXEL">DOM_DELTA_PIXEL</a>       = 0x00;
-          const unsigned long       <a href="#events-DOM_DELTA_LINE">DOM_DELTA_LINE</a>        = 0x01;
-          const unsigned long       <a href="#events-DOM_DELTA_PAGE">DOM_DELTA_PAGE</a>        = 0x02;
-
-          readonly attribute long            <a href="#events-Events-WheelEvent-deltaX">deltaX</a>;
-          readonly attribute long            <a href="#events-Events-WheelEvent-deltaY">deltaY</a>;
-          readonly attribute long            <a href="#events-Events-WheelEvent-deltaZ">deltaZ</a>;
-          readonly attribute unsigned long   <a href="#events-Events-WheelEvent-deltaMode">deltaMode</a>;    
-          void               <a href="#events-event-type-initWheelEvent">initWheelEvent</a>(in DOMString typeArg, 
-                                                          in boolean canBubbleArg, 
-                                                          in boolean cancelableArg, 
-                                                          in views::AbstractView viewArg, 
-                                                          in long detailArg, 
-                                                          in long screenXArg, 
-                                                          in long screenYArg, 
-                                                          in long clientXArg, 
-                                                          in long clientYArg, 
-                                                          in unsigned short buttonArg, 
-                                                          in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg, 
-                                                          in DOMString modifiersListArg, 
-                                                          in long deltaXArg, 
-                                                          in long deltaYArg, 
-                                                          in long deltaZArg, 
-                                                          in unsigned long deltaMode);
-        };
-        </pre>
+// Introduced in DOM Level 3:
+interface <a href="#events-Events-WheelEvent">WheelEvent</a> : <a href="#events-Events-MouseEvent">MouseEvent</a> {
+
+  // DeltaModeCode
+  const unsigned long       <a href="#events-DOM_DELTA_PIXEL">DOM_DELTA_PIXEL</a>       = 0x00;
+  const unsigned long       <a href="#events-DOM_DELTA_LINE">DOM_DELTA_LINE</a>        = 0x01;
+  const unsigned long       <a href="#events-DOM_DELTA_PAGE">DOM_DELTA_PAGE</a>        = 0x02;
+
+  readonly attribute long            <a href="#events-Events-WheelEvent-deltaX">deltaX</a>;
+  readonly attribute long            <a href="#events-Events-WheelEvent-deltaY">deltaY</a>;
+  readonly attribute long            <a href="#events-Events-WheelEvent-deltaZ">deltaZ</a>;
+  readonly attribute unsigned long   <a href="#events-Events-WheelEvent-deltaMode">deltaMode</a>;    
+  void               <a href="#events-event-type-initWheelEvent">initWheelEvent</a>(in DOMString typeArg, 
+                                                  in boolean canBubbleArg, 
+                                                  in boolean cancelableArg, 
+                                                  in views::AbstractView viewArg, 
+                                                  in long detailArg, 
+                                                  in long screenXArg, 
+                                                  in long screenYArg, 
+                                                  in long clientXArg, 
+                                                  in long clientYArg, 
+                                                  in unsigned short buttonArg, 
+                                                  in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg, 
+                                                  in DOMString modifiersListArg, 
+                                                  in long deltaXArg, 
+                                                  in long deltaYArg, 
+                                                  in long deltaZArg, 
+                                                  in unsigned long deltaMode);
+};
+                </pre>
               </div>
               <br />
             </dd>
+
             <dt>
               <strong>Definition group <em><a id="events-ID-WheelEvent-DeltaModeCode">DeltaModeCode</a></em></strong>
             </dt>
             <dd>
               <p>This set of constants shall be used to indicate the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values.  The precise measurement is specific to device, operating system, and application configurations.</p>
               <dl>
-                <dt>
-                  <strong>Defined Constants</strong>
-                </dt>
+                <dt><strong>Defined Constants</strong></dt>
                 <dd>
                   <dl>
-                    <dt>
-                      <a id="events-DOM_DELTA_PIXEL">
-                        <code class="constant-name">DOM_DELTA_PIXEL</code>
-                      </a>
-                    </dt>
+                    <dt><a id="events-DOM_DELTA_PIXEL"><code class="constant-name">DOM_DELTA_PIXEL</code></a></dt>
                     <dd>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> shall be pixels.  This is the most typical case in most operating system and implementation configurations.</dd>
-                    <dt>
-                      <a id="events-DOM_DELTA_LINE">
-                        <code class="constant-name">DOM_DELTA_LINE</code>
-                      </a>
-                    </dt>
+
+                    <dt><a id="events-DOM_DELTA_LINE"><code class="constant-name">DOM_DELTA_LINE</code></a></dt>
                     <dd>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> shall be individual lines of text.  This is the case for many form controls.</dd>
-                    <dt>
-                      <a id="events-DOM_DELTA_PAGE">
-                        <code class="constant-name">DOM_DELTA_PAGE</code>
-                      </a>
-                    </dt>
+
+                    <dt><a id="events-DOM_DELTA_PAGE"><code class="constant-name">DOM_DELTA_PAGE</code></a></dt>
                     <dd>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> shall be pages, either defined as a single screen or as a demarcated page.</dd>
+
                   </dl>
                 </dd>
               </dl>
             </dd>
-            <dt>
-              <strong>Attributes</strong>
-            </dt>
+
+            <dt><strong>Attributes</strong></dt>
             <dd>
               <dl>
                 <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaX">deltaX</a></code> of type <code>long</code>, readonly</dt>
                 <dd>The distance the wheel has rotated around the x-axis.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaY">deltaY</a></code> of type <code>long</code>, readonly</dt>
                 <dd>The distance the wheel has rotated around the y-axis.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaZ">deltaZ</a></code> of type <code>long</code>, readonly</dt>
                 <dd>The distance the wheel has rotated around the z-axis.<br /></dd>
+
                 <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaMode">deltaMode</a></code> of type <code>unsigned long</code>, readonly</dt>
-                <dd>The <code>deltaMode</code> attribute contains an indication of to indicate the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values.  The default value is <a href="#events-DOM_DELTA_PIXEL"><code class="constant-name">DOM_DELTA_PIXEL</code></a> (pixels).  The value of <code>deltaMode</code> may be different for each of <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaX">deltaX</a></code>, <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaY">deltaY</a></code>, and <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaZ">deltaZ</a></code>, based on system configuration.<br />
-
-                        <!-- <p class="issue"><strong>Issue:</strong> deltaMode is the proposed solution for <a href="http://www.w3.org/2008/webapps/track/issues/9" title="ISSUE-9 - Web Applications Working Group Tracker">ISSUE-9</a>.</p> -->
-
-                      </dd>
+                <dd>
+                  The <code>deltaMode</code> attribute contains an indication of to indicate the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values.  The default value is <a href="#events-DOM_DELTA_PIXEL"><code class="constant-name">DOM_DELTA_PIXEL</code></a> (pixels).  The value of <code>deltaMode</code> may be different for each of <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaX">deltaX</a></code>, <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaY">deltaY</a></code>, and <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaZ">deltaZ</a></code>, based on system configuration.<br />
+                  <!-- <p class="issue"><strong>Issue:</strong> deltaMode is the proposed solution for <a href="http://www.w3.org/2008/webapps/track/issues/9" title="ISSUE-9 - Web Applications Working Group Tracker">ISSUE-9</a>.</p> -->
+                </dd>
               </dl>
             </dd>
-            <dt>
-              <strong>Methods</strong>
-            </dt>
+
+            <dt><strong>Methods</strong></dt>
             <dd>
               <dl>
                 <dt><code class="method-name"><a id="events-event-type-initWheelEvent">initWheelEvent</a></code> introduced in <strong class="since">DOM Level 3</strong></dt>
                 <dd>
                   <div class="method">Initializes attributes of a <code>WheelEvent</code> object. This method has the same behavior as <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a>.
-                          <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">screenXArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">screenYArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">clientXArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">clientYArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">buttonArg</code> of type <code>unsigned short</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">modifiersListArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">deltaXArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a>.<br /></dd><dt><code class="parameter-name">deltaYArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a>.<br /></dd><dt><code class="parameter-name">deltaZArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaZ"><code>WheelEvent.deltaZ</code></a>.<br /></dd><dt><code class="parameter-name">deltaModeArg</code> of type <code>unsigned long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaMode"><code>WheelEvent.deltaMode</code></a>.<br /></dd></dl></div></div>
-                          <!-- parameters -->
-                          <div><strong>No Return Value</strong></div>
-                          <div><strong>No Exceptions</strong></div>
-                        </div>
+                    <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">screenXArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">screenYArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">clientXArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">clientYArg</code> of type <code>long</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">buttonArg</code> of type <code>unsigned short</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">modifiersListArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">deltaXArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a>.<br /></dd>
+<dt><code class="parameter-name">deltaYArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a>.<br /></dd>
+<dt><code class="parameter-name">deltaZArg</code> of type <code>long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaZ"><code>WheelEvent.deltaZ</code></a>.<br /></dd>
+<dt><code class="parameter-name">deltaModeArg</code> of type <code>unsigned long</code></dt><dd>Specifies <a href="#events-Events-WheelEvent-deltaMode"><code>WheelEvent.deltaMode</code></a>.<br /></dd>
+</dl></div></div>
+                    <!-- parameters -->
+                    <div><strong>No Return Value</strong></div>
+
+                    <div><strong>No Exceptions</strong></div>
+                  </div>
 <!-- method -->
                 </dd>
               </dl>
             </dd>
-            
           </dl>
         </dd>
       </dl>
@@ -3106,69 +2895,64 @@
 <!-- wheel -->
       <div class="event-definition assert must">
         <dl>
-          <dt id="event-type-wheel">
-            <a class="eventtype noxref" href="#event-type-wheel"><code>wheel</code></a>
-          </dt>
-          <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>wheel</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-WheelEvent"><code>WheelEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>scroll (or zoom) the document</a> event</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a>, <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a>, <a href="#events-Events-WheelEvent-deltaZ"><code>WheelEvent.deltaZ</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, and <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> are in use if the wheel is associated to a pointing device. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> the pointing device is pointing at, if any. <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> is not in use.</td></tr></table>
-            A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a mouse wheel has been rotated around any axis, or when an equivalent input device (such as a mouse-ball, certain tablets or touchpads, etc.) has emulated such an action. 
+          <dt id="event-type-wheel"><dfn>
+              <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a>
+            </dfn></dt>
+          <dd>
+            <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+              <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>wheel</code></strong></td></tr>
+              <tr class="assert must"><th>Interface</th><td><a href="#events-Events-WheelEvent"><code>WheelEvent</code></a></td></tr>
+              <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+              <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
+              <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+              <tr class="assert must"><th>Default action</th><td>scroll (or zoom) the document</td></tr>
+              <tr class="assert must"><th>Context info</th><td><a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a>, <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a>, <a href="#events-Events-WheelEvent-deltaZ"><code>WheelEvent.deltaZ</code></a>, <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>, <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>, <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>, <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>, and <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> are in use. <a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>, <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>, <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>, <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>, and <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> are in use if the wheel is associated to a pointing device. <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a> indicates the <a class="def" href="#glossary-event-target">event target</a> the pointing device is pointing at, if any. <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> is not in use.</td></tr>
+            </table>
+            <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a mouse wheel has been rotated around any axis, or when an equivalent input device (such as a mouse-ball, certain tablets or touchpads, etc.) has emulated such an action.</p>
             <p>The typical default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event type is to scroll (or in some cases, zoom) the document by the indicated amount.  If this event is canceled, the implementation must not scroll or zoom the document (or perform whatever other implementation-specific default action is associated with this event type).</p>
-            
             <p>Due to a lack of early standardization for a mouse-wheel event type, there are several related proprietary events which have been implemented by different <a class="def" href="#glossary-user-agent">user agents</a>, with different names and characteristics.  This specification does not attempt to specify these legacy events due to lack of interoperability, but supplies the following equivalency information which may help implementers and authors.  A <a class="def" href="#glossary-user-agent">user agent</a> may dispatch an event of one or more of the following event types as a <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event, depending upon the property values of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event and implementation support:</p>
-            
-            <h5 id="mousewheel"><strong>mousewheel</strong></h5>
-            
+            <h5 id="mousewheel">
+              <strong>mousewheel</strong>
+            </h5>
             <p>Dispatched when <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</p>
-
             <p><strong>In Microsoft Internet Explorer:</strong></p>
             <p><code>mousewheel.wheelDelta = -(WheelEvent.deltaY) / 120</code></p>
-
             <p><strong>In Opera:</strong></p>
             <p><code>mousewheel.wheelDelta = WheelEvent.deltaY / 120</code></p>
-            
-            
-            <h5 id="DOMMouseScroll"><strong>DOMMouseScroll</strong></h5>
-            
+            <h5 id="DOMMouseScroll">
+              <strong>DOMMouseScroll</strong>
+            </h5>
             <p>Dispatched when <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</p>
-            
             <p><strong>In Mozilla Firefox:</strong></p>
             <p><code>DOMMouseScroll.detail = WheelEvent.deltaY / 3</code></p>
             <p><code>DOMMouseScroll.axis = VERTICAL_AXIS</code></p>
-
-            
             <p>Dispatched when <a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a> is non-zero.</p>
-            
             <p><strong>In Mozilla Firefox:</strong></p>
             <p><code>DOMMouseScroll.detail = WheelEvent.deltaX / 3</code></p>
             <p><code>DOMMouseScroll.axis = HORIZONTAL_AXIS</code></p>
-
-            
-            <h5 id="MozMousePixelScroll"><strong>MozMousePixelScroll</strong></h5>
-
+            <h5 id="MozMousePixelScroll">
+              <strong>MozMousePixelScroll</strong>
+            </h5>
             <p>Dispatched when <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero, and <a href="#events-Events-WheelEvent-deltaMode"><code>deltaMode</code></a> is <a href="#events-DOM_DELTA_PIXEL"><code>DOM_DELTA_PIXEL</code></a>.</p>
-            
             <p><strong>In Mozilla Firefox:</strong></p>
             <p><code>MozMousePixelScroll.detail = WheelEvent.deltaY / 3</code></p>
             <p><code>MozMousePixelScroll.axis = VERTICAL_AXIS</code></p>
-
-            
             <p>Dispatched when <a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a> is non-zero, and <a href="#events-Events-WheelEvent-deltaMode"><code>deltaMode</code></a> is <a href="#events-DOM_DELTA_PIXEL"><code>DOM_DELTA_PIXEL</code></a>.</p>
-            
             <p><strong>In Mozilla Firefox:</strong></p>
             <p><code>MozMousePixelScroll.detail = WheelEvent.deltaX / 3</code></p>
             <p><code>MozMousePixelScroll.axis = HORIZONTAL_AXIS</code></p>
-
             <p class="note" id="note-delta-speed"><strong>Note:</strong> In some <a class="def" href="#glossary-user-agent">user agents</a>, or with some input devices, the speed that the wheel has been turned may affect the <a href="#glossary-delta"><code>delta</code></a> values, with a faster speed producing a higher <a href="#glossary-delta"><code>delta</code></a> value.</p>
-
             <p class="note" id="note-no-scroll-default"><strong>Note:</strong> Though events of event type <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> often result in scrolling, which results in a <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> event, there is no direct connection between these event types, and the <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> event is not a <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event.</p>
           </dd>
         </dl>
       </div>
-      
-<!-- div3 Events-eventgroupings-uievents -->
-      <div class="div3">
-        <h3 class="div3"><a id="events-textevents" href="#events-textevents">5.2.5 Text Events Types</a></h3>
+<!-- div3 Events-eventgroupings-textevents -->
+      <div>
+        <h3><a id="events-textevents" href="#events-textevents">5.2.5 Text Events Types</a></h3>
+
         <p>This module defines the feature TextEvents 3.0 and depends on the feature UIEvents 3.0.</p>
-        <p>The text event module originates from the [<cite><a class="noxref informative" href="#references-HTML40">HTML 4.01</a></cite>] <code>onkeypress</code> attribute. Unlike this attribute, the event type <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> applies only to characters and is designed for use with any text input devices, not just keyboards. Refer to <a href="#keyset">Keyboard events and key values</a> for examples on how text events are used in combination with keyboard events.</p>
+        <p>The text event module originates from the [<cite><a class="informative" href="#references-HTML40">HTML 4.01</a></cite>] <code>onkeypress</code> attribute. Unlike this attribute, the event type <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> applies only to characters and is designed for use with any text input devices, not just keyboards. Refer to <a href="#keyset">Keyboard events and key values</a> for examples on how text events are used in combination with keyboard events.</p>
         <dl>
           <dt><strong>Interface <em><a id="events-Events-TextEvent">TextEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
           <dd>
@@ -3206,99 +2990,68 @@
                                      in DOMString dataArg, 
                                      in unsigned long inputMode);
 };
-</pre>
+                  </pre>
                 </div>
                 <br />
               </dd>
+
               <dt>
                 <strong>Definition group <em><a id="events-ID-TextEvent-InputModeCode">InputModeCode</a></em></strong>
               </dt>
               <dd>
                 <p>This set of constants shall be used to indicate the origin of the text input. In case a DOM implementation wishes to provide a new location information, a value different from the following constant values must be used.</p>
                 <dl>
-                  <dt>
-                    <strong>Defined Constants</strong>
-                  </dt>
+                  <dt><strong>Defined Constants</strong></dt>
                   <dd>
                     <dl>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_UNKNOWN">
-                          <code class="constant-name">DOM_INPUT_METHOD_UNKNOWN</code>
-                        </a>
-                      </dt>
+                      <dt><a id="events-DOM_INPUT_METHOD_UNKNOWN"><code class="constant-name">DOM_INPUT_METHOD_UNKNOWN</code></a></dt>
                       <dd>The text string was input by an unknown means.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_KEYBOARD">
-                          <code class="constant-name">DOM_INPUT_METHOD_KEYBOARD</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_KEYBOARD"><code class="constant-name">DOM_INPUT_METHOD_KEYBOARD</code></a></dt>
                       <dd>The text string was input through a keyboard.  This may be associated with one or more of <code>keypress</code>,  <code>keydown</code>, or <code>keyup</code> events.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_PASTE">
-                          <code class="constant-name">DOM_INPUT_METHOD_PASTE</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_PASTE"><code class="constant-name">DOM_INPUT_METHOD_PASTE</code></a></dt>
                       <dd>The text string was pasted in from a clipboard.  This may be associated with a <code>paste</code> event, specified elsewhere.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_DROP">
-                          <code class="constant-name">DOM_INPUT_METHOD_DROP</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_DROP"><code class="constant-name">DOM_INPUT_METHOD_DROP</code></a></dt>
                       <dd>The text string was inserted as part of a drag-and-drop operation.  This may be associated with a <code>drop</code> event, specified elsewhere.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_IME">
-                          <code class="constant-name">DOM_INPUT_METHOD_IME</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_IME"><code class="constant-name">DOM_INPUT_METHOD_IME</code></a></dt>
                       <dd>The text string was entered through an Input Method Editor.  This may be associated with a <code>compositionend</code> event.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_OPTION">
-                          <code class="constant-name">DOM_INPUT_METHOD_OPTION</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_OPTION"><code class="constant-name">DOM_INPUT_METHOD_OPTION</code></a></dt>
                       <dd>The text string was selected from a set of options presented, such as from a form.  This may be associated with various other events, specified elsewhere.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_HANDWRITING">
-                          <code class="constant-name">DOM_INPUT_METHOD_HANDWRITING</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_HANDWRITING"><code class="constant-name">DOM_INPUT_METHOD_HANDWRITING</code></a></dt>
                       <dd>The text string was input through a pen/tablet device and processed by handwriting recognition software.  This may be associated with a specific event defined elsewhere.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_VOICE">
-                          <code class="constant-name">DOM_INPUT_METHOD_VOICE</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_VOICE"><code class="constant-name">DOM_INPUT_METHOD_VOICE</code></a></dt>
                       <dd>The text string was input by a voice device and interpreted by speech recognition software.  This may be associated with a specific event defined elsewhere.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_MULTIMODAL">
-                          <code class="constant-name">DOM_INPUT_METHOD_MULTIMODAL</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_MULTIMODAL"><code class="constant-name">DOM_INPUT_METHOD_MULTIMODAL</code></a></dt>
                       <dd>The text string was inserted as part of an operation involving multiple input modalities in combination, such as pointer-enhanced speech.  This may be associated with various other events, specified elsewhere.</dd>
-                      <dt>
-                        <a id="events-DOM_INPUT_METHOD_SCRIPT">
-                          <code class="constant-name">DOM_INPUT_METHOD_SCRIPT</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_INPUT_METHOD_SCRIPT"><code class="constant-name">DOM_INPUT_METHOD_SCRIPT</code></a></dt>
                       <dd>The text string was inserted via a script operation on the DOM.  This may be associated with one or more  <code>mutation</code> events.</dd>
+
                     </dl>
                   </dd>
                 </dl>
               </dd>
-              <dt>
-                <strong>Attributes</strong>
-              </dt>
+
+              <dt><strong>Attributes</strong></dt>
               <dd>
                 <dl>
                   <dt><code class="attribute-name"><a id="events-Events-TextEvent-data">data</a></code> of type <code>DOMString</code>, readonly</dt>
-                  <dd><code>data</code> holds the value of the characters generated by the character device. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class="noxref normative" href="#references-Unicode">Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <em>NFC</em>, defined in [<cite><a class="noxref normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute cannot be null or contain the empty string.<br /></dd>
+                  <dd><code>data</code> holds the value of the characters generated by the character device. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class="normative" href="#references-Unicode">Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <em>NFC</em>, defined in [<cite><a class="normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute cannot be null or contain the empty string.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-TextEvent-inputMode">inputMode</a></code> of type <code>unsigned long</code>, readonly</dt>
                   <dd>The <code>inputMode</code> attribute contains an indication of the origin of the text input, as described in <a href="#events-ID-TextEvent-InputModeCode">InputModeCode</a>.<br /></dd>
+
                 </dl>
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -3308,16 +3061,22 @@
                   </dt>
                   <dd>
                     <div class="method">Initializes attributes of a <code>TextEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.
-<div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">dataArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a>.<br /></dd><dt><code class="parameter-name">inputModeArg</code> of type <code>unsigned long</code></dt><dd>Specifies <a href="#events-Events-TextEvent-inputMode"><code>TextEvent.inputMode</code></a>.<br /></dd></dl></div></div>
+<div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">dataArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a>.<br /></dd>
+<dt><code class="parameter-name">inputModeArg</code> of type <code>unsigned long</code></dt><dd>Specifies <a href="#events-Events-TextEvent-inputMode"><code>TextEvent.inputMode</code></a>.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
                   </dd>
                 </dl>
               </dd>
-              
             </dl>
           </dd>
         </dl>
@@ -3326,19 +3085,29 @@
 <!-- textInput -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-textInput">
-              <a class="eventtype noxref" href="#event-type-textInput"><code>textInput</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>textInput</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-TextEvent"><code>TextEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a>, and <a href="#events-Events-TextEvent-inputMode"><code>TextEvent.inputMode</code></a> are in use.</td></tr></table>
-               A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when one or more characters have been entered. These characters may originate from a variety of sources, e.g., characters resulting from a key being pressed or released on a keyboard device, from the processing of an <a class="def" href="#glossary-ime">input method editor</a>, or resulting from a voice command.  Where a "paste" operation generates a simple sequence of characters, i.e. a text passage without any structure or style information, this event type should be generated as well.</dd>
+            <dt id="event-type-textInput"><dfn>
+                <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>textInput</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-TextEvent"><code>TextEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a>, and <a href="#events-Events-TextEvent-inputMode"><code>TextEvent.inputMode</code></a> are in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when one or more characters have been entered. These characters may originate from a variety of sources, e.g., characters resulting from a key being pressed or released on a keyboard device, from the processing of an <a class="def" href="#glossary-ime">input method editor</a>, or resulting from a voice command.  Where a "paste" operation generates a simple sequence of characters, i.e. a text passage without any structure or style information, this event type should be generated as well.</p>
+            </dd>
           </dl>
         </div>
       </div>
-      
-      
 <!-- div3 Events-TextEvents-Interfaces -->
-      <div class="div3">
-        <h3 class="div3"><a id="events-keyboardevents" href="#events-keyboardevents">5.2.6 Keyboard Event Types</a></h3>
+      <div>
+        <h3><a id="events-keyboardevents" href="#events-keyboardevents">5.2.6 Keyboard Event Types</a></h3>
+
         <p>This module defines the feature KeyboardEvents 3.0 and depends on the feature UIEvents 3.0.</p>
         <p>Keyboard events are device dependent, i.e. they rely on the capabilities of the input devices and how they are mapped in the operating systems. It is therefore highly recommended to rely on <a href="#events-Events-TextEvent">Text events types</a> when dealing with character input.  Refer to <a href="#keyset">Keyboard events and key values</a> for more details, including examples on how Keyboard Events are used in combination with Composition Events.</p>
         <dl>
@@ -3355,8 +3124,8 @@
               <dd>
                 <div class="idl-code">
                   <pre>
-  // Introduced in DOM Level 3:
-  interface <a href="#events-Events-KeyboardEvent">KeyboardEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
+// Introduced in DOM Level 3:
+interface <a href="#events-Events-KeyboardEvent">KeyboardEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
 
   // KeyLocationCode
   const unsigned long       <a href="#events-DOM_KEY_LOCATION_STANDARD">DOM_KEY_LOCATION_STANDARD</a>      = 0x00;
@@ -3382,88 +3151,74 @@
                                      in unsigned long locationArg, 
                                      in DOMString modifiersListArg,
                                      in boolean repeat);
-  };
-  </pre>
+};
+                  </pre>
                 </div>
                 <br />
               </dd>
+
               <dt>
                 <strong>Definition group <em><a id="events-ID-KeyboardEvent-KeyLocationCode">KeyLocationCode</a></em></strong>
               </dt>
               <dd>
                 <p>This set of constants shall be used to indicate the location of a key on the device. In case a DOM implementation wishes to provide a new location information, a value different from the following constant values must be used.</p>
                 <dl>
-                  <dt>
-                    <strong>Defined Constants</strong>
-                  </dt>
+                  <dt><strong>Defined Constants</strong></dt>
                   <dd>
                     <dl>
-                      <dt>
-                        <a id="events-DOM_KEY_LOCATION_LEFT">
-                          <code class="constant-name">DOM_KEY_LOCATION_LEFT</code>
-                        </a>
-                      </dt>
+                      <dt><a id="events-DOM_KEY_LOCATION_LEFT"><code class="constant-name">DOM_KEY_LOCATION_LEFT</code></a></dt>
                       <dd>The key activated shall be in the left key location (there is more than one possible location for this key). <i class="example"><strong>Example:</strong> the left <code class="value">'Control'</code> key on a PC 101 Key US keyboard.</i></dd>
-                      <dt>
-                        <a id="events-DOM_KEY_LOCATION_NUMPAD">
-                          <code class="constant-name">DOM_KEY_LOCATION_NUMPAD</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_KEY_LOCATION_NUMPAD"><code class="constant-name">DOM_KEY_LOCATION_NUMPAD</code></a></dt>
                       <dd>The key activation originated on the numeric keypad or with a virtual key corresponding to the numeric keypad. <i class="example"><strong>Example:</strong> the <code class="value">'1'</code> key on a PC 101 Key US keyboard located on the numeric pad.</i></dd>
-                      <dt>
-                        <a id="events-DOM_KEY_LOCATION_RIGHT">
-                          <code class="constant-name">DOM_KEY_LOCATION_RIGHT</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_KEY_LOCATION_RIGHT"><code class="constant-name">DOM_KEY_LOCATION_RIGHT</code></a></dt>
                       <dd>The key activation shall be in the right key location (there is more than one possible location for this key). <i class="example"><strong>Example:</strong> the right <code class="value">'Shift'</code> key on a PC 101 Key US keyboard.</i></dd>
-                      <dt>
-                        <a id="events-DOM_KEY_LOCATION_STANDARD">
-                          <code class="constant-name">DOM_KEY_LOCATION_STANDARD</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_KEY_LOCATION_STANDARD"><code class="constant-name">DOM_KEY_LOCATION_STANDARD</code></a></dt>
                       <dd>The key activation shall not be distinguished as the left or right version of the key, and did not originate from the numeric keypad (or did not originate with a virtual key corresponding to the numeric keypad). <i class="example"><strong>Example:</strong> the <code class="value">'Q'</code> key on a PC 101 Key US keyboard.</i></dd>
-                      <dt>
-                        <a id="events-DOM_KEY_LOCATION_MOBILE">
-                          <code class="constant-name">DOM_KEY_LOCATION_MOBILE</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_KEY_LOCATION_MOBILE"><code class="constant-name">DOM_KEY_LOCATION_MOBILE</code></a></dt>
                       <dd>The key activation originated on a mobile device, either on a physical keypad or a virtual keyboard. <i class="example"><strong>Example:</strong> the <code class="value">'#'</code> key or softkey on a mobile device.</i></dd>
-                      <dt>
-                        <a id="events-DOM_KEY_LOCATION_JOYSTICK">
-                          <code class="constant-name">DOM_KEY_LOCATION_JOYSTICK</code>
-                        </a>
-                      </dt>
+
+                      <dt><a id="events-DOM_KEY_LOCATION_JOYSTICK"><code class="constant-name">DOM_KEY_LOCATION_JOYSTICK</code></a></dt>
                       <dd>The key activation originated on a game controller or a joystick on a mobile device. <i class="example"><strong>Example:</strong> the <code class="value">'DownLeft'</code> key on a game controller.</i></dd>
+
                     </dl>
                   </dd>
                 </dl>
               </dd>
-              <dt>
-                <strong>Attributes</strong>
-              </dt>
+
+              <dt><strong>Attributes</strong></dt>
               <dd>
                 <dl>
                   <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-altKey">altKey</a></code> of type <code>boolean</code>, readonly</dt>
                   <dd><code>true</code> if the alternative (Alt) key modifier is activated.
   <p class="note"><strong>Note:</strong> The Option key modifier on Macintosh systems must be represented using this key modifier.</p></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-ctrlKey">ctrlKey</a></code> of type <code>boolean</code>, readonly</dt>
                   <dd><code>true</code> if the control (Ctrl) key modifier is activated.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-key">key</a></code> of type <code>DOMString</code>, readonly</dt>
                   <dd><code>key</code> holds the key value of the key pressed. The key values are defined in <a href="#keyset-keyvalues">Key values set</a>. Implementations that are unable to identify a key must use the key value <code class="value">'Unidentified'</code>.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-location">location</a></code> of type <code>unsigned long</code>, readonly</dt>
                   <dd>The <code>location</code> attribute contains an indication of the location of the key on the device, as described in <a href="#events-ID-KeyboardEvent-KeyLocationCode">Keyboard event types</a>.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-metaKey">metaKey</a></code> of type <code>boolean</code>, readonly</dt>
                   <dd><code>true</code> if the meta (Meta) key modifier is activated.
   <p class="note"><strong>Note:</strong> The Command key modifier on Macintosh systems must be represented using this key modifier.</p></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-shiftKey">shiftKey</a></code> of type <code>boolean</code>, readonly</dt>
                   <dd><code>true</code> if the shift (Shift) key modifier is activated.<br /></dd>
+
                   <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-repeat">repeat</a></code> of type <code>boolean</code>, readonly</dt>
                   <dd><code>true</code> if the key has been pressed in a sustained manner.  Depending on the system configuration, holding down a key results may result in multiple consecutive <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> events,  <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> events, and <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> events, for appropriate keys.   For mobile devices which have <em>long-key-press</em> behavior, the first key event with a <a href="#events-Events-KeyboardEvent-repeat">repeat</a> attribute value of <code>'true'</code> shall serve as an indication of a <em>long-key-press</em>.  The length of time that the key must be pressed in order to begin repeating is configuration-dependent.</dd>
+
                 </dl>
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -3472,18 +3227,32 @@
                     </code>
                   </dt>
                   <dd>
-                    <div class="method">Queries the state of a modifier using a key value. See also <a href="#keyset-Modifiers">Modifier keys</a>.
-  <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt><dd>A modifier key value.  Modifier keys defined in this specification are <code class="value">'Alt'</code>, <code class="value">'AltGraph'</code>, <code class="value">'CapsLock'</code>, <code class="value">'Control'</code>, <code class="value">'Fn'</code>, <code class="value">'Meta'</code>, <code class="value">'NumLock'</code>, <code class="value">'Scroll'</code>, and <code class="value">'Shift'</code>, and <code class="value">'Win'</code>.  User agents may support additional implementation-specific modifier keys depending on the environment.
-  <p class="note"><strong>Note:</strong> If an application wishes to distinguish between right and left modifiers, this information could be deduced using keyboard events and <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.</p>
-                            </dd></dl></div></div>
+                    <div class="method">
+                      Queries the state of a modifier using a key value. See also <a href="#keyset-Modifiers">Modifier keys</a>.
+                      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt><dd>
+                              A modifier key value.  Modifier keys defined in this specification are 
+                              <code class="value">'Alt'</code>, 
+                              <code class="value">'AltGraph'</code>, 
+                              <code class="value">'CapsLock'</code>, 
+                              <code class="value">'Control'</code>, 
+                              <code class="value">'Fn'</code>, 
+                              <code class="value">'Meta'</code>, 
+                              <code class="value">'NumLock'</code>, 
+                              <code class="value">'Scroll'</code>, 
+                              <code class="value">'Shift'</code>, and 
+                              <code class="value">'Win'</code>.  
+                              User agents may support additional implementation-specific modifier keys depending on the environment.
+                              <p class="note"><strong>Note:</strong> If an application wishes to distinguish between right and left modifiers, this information could be deduced using keyboard events and <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.</p>
+                            </dd>
+                          </dl></div></div>
                       <!-- parameters -->
                       <div class="return"><strong>Return Value</strong><div class="returntable"><table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr><td><p><code>boolean</code></p></td><td><p><code>true</code> if it is a modifier key and the modifier is activated, <code>false</code> otherwise.</p></td></tr></table></div></div>
                       <!-- return -->
                       <div><strong>No Exceptions</strong></div>
                     </div>
-                    <!-- method -->
+<!-- method -->
                   </dd>
-                 
+
                   <dt>
                     <code class="method-name">
                       <a id="events-Events-KeyboardEvent-initKeyboardEvent">initKeyboardEvent</a>
@@ -3491,9 +3260,17 @@
                   </dt>
                   <dd>
                     <div class="method">Initializes attributes of a <code>KeyboardEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.
-  <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>.<br /></dd><dt><code class="parameter-name">locationArg</code> of type <code>unsigned long</code></dt><dd>Specifies <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.<br /></dd><dt><code class="parameter-name">modifiersListArg</code> of type <code>DOMString</code></dt><dd>A <a class="normative" href="http://www.w3.org/TR/2004/REC-xml-20040204/#NT-S"><em>white space</em></a> separated list of modifier key values to be activated on this object. As an example, <code>"Control Alt"</code> must mark the control and alt modifiers as activated.<br /></dd></dl></div></div>
+  <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>.<br /></dd>
+<dt><code class="parameter-name">locationArg</code> of type <code>unsigned long</code></dt><dd>Specifies <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.<br /></dd>
+<dt><code class="parameter-name">modifiersListArg</code> of type <code>DOMString</code></dt><dd>A <a class="normative" href="http://www.w3.org/TR/2004/REC-xml-20040204/#NT-S"><em>white space</em></a> separated list of modifier key values to be activated on this object. As an example, <code>"Control Alt"</code> must mark the control and alt modifiers as activated.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
@@ -3503,19 +3280,18 @@
             </dl>
           </dd>
         </dl>
-        
         <p class="warning" id="keycode-charcode"><strong>Warning!</strong>  Legacy keyboard event implementations may include two additional attributes, <code>keyCode</code> and <code>charCode</code>.  The <code>keyCode</code> attribute indicates a numeric value associated with a particular key on a computer keyboard, while the <code>charCode</code> attribute indicates the <acronym title="American Standard Code for Information Interchange">ASCII</acronym> value of the character associated with that key (which may or may not be the same as the <code>keyCode</code> value) and is applicable only to keys that produce a <a class="def" href="#glossary-character-value">character value</a>.  In practice, <code>keyCode</code> and <code>charCode</code> are inconsistent across platforms and even the same implementation on different operating systems or using different localizations.  DOM Level 3 Events  does not define behavior for either <code>keyCode</code> or <code>charCode</code>; authors should use <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> instead, in conforming DOM Level 3 Events implementations.  <em>For more information, see the informative table in <a href="#keyset-keyCode-charCode">Key values, keyCode, and charCode</a>.</em></p>
-                
         <p>Depending on the character generation device, keyboard events may or may not be generated.</p>
-        
         <p class="note" id="note-virtual-keyboards"><strong>Note:</strong>  For compatibility with existing content, virtual keyboards, such as software keyboards on screen-based input devices, should produce the normal range of keyboard events, even though they do not possess physical keys.</p>
-        
         <p>The keyboard event types are listed below.</p>
-        
-        <h4 class="div3 needswork"><a id="events-keyboard-event-order" href="#events-keyboard-event-order">5.2.6.1 Keyboard Event Order</a></h4>
+        <h4 class="needswork">
+          <a id="events-keyboard-event-order" href="#events-keyboard-event-order">5.2.6.1 Keyboard Event Order</a>
+        </h4>
         <p>The keyboard events defined in this specification occur in a set order relative to one another, for any given key:</p>
         <ol>
-          <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a></li>
+          <li>
+            <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>
+          </li>
           <li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (only for keys which produce a <a class="def" href="#glossary-character-value">character value</a>)</li>
           <li>If the key is depressed for a sustained period, the following events may repeat at an environment-dependent rate:
             <!-- and the key should seek counseling -->
@@ -3524,13 +3300,18 @@
               <li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (with <a href="#events-Events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>; only for keys which produce a <a class="def" href="#glossary-character-value">character value</a>)</li>
             </ul>
           </li>
-          <li><em>Any <a class="def" href="#glossary-default-action">default actions</a> related to this key</em></li>
-          <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a></li>
+          <li>
+            <em>Any <a class="def" href="#glossary-default-action">default actions</a> related to this key</em>
+          </li>
+          <li>
+            <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>
+          </li>
         </ol>
-        
         <p>Keys associated with a <a class="def" href="#glossary-character-value">character value</a> must, under normal circumstances, produce a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event as well.  The order of text events relative to keyboard events is as follows:</p>
         <ol>
-          <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a></li>
+          <li>
+            <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>
+          </li>
           <li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (only for keys which produce a <a class="def" href="#glossary-character-value">character value</a>)</li>
           <li>If a <a class="def" href="#glossary-character-value">character value</a> is produced, <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a></li>
           <li>If the key is depressed for a sustained period, the following events may repeat at an environment-dependent rate:
@@ -3541,58 +3322,71 @@
               <li>If a <a class="def" href="#glossary-character-value">character value</a> is produced, <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a></li>
             </ul>
           </li>
-          <li><em>Any <a class="def" href="#glossary-default-action">default actions</a> associated with this key</em></li>
-          <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a></li>
+          <li>
+            <em>Any <a class="def" href="#glossary-default-action">default actions</a> associated with this key</em>
+          </li>
+          <li>
+            <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>
+          </li>
         </ol>
-        
         <p class="note" id="key-default"><strong>Note</strong>  Typically, any <a class="def" href="#glossary-default-action">default actions</a> associated with any particular key must be completed before the <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event is dispatched, which may delay the <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event slightly (though this is not likely to be a perceptible delay).</p>
-        
         <p class="warning"><strong>Warning!</strong> Because of hardware limitations, on some keyboard devices, the order between the text event and keyboard events may differ.  For example, some mobile devices may dispatch the <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event after the <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event.</p>
-                
-<text id="text_1" x="10" y="25" font-size="18" fill="crimson" text-anchor="middle"></text>
 
 <!-- keydown -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-keydown">
-              <a class="eventtype noxref" href="#event-type-keydown"><code>keydown</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keydown</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>, <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>, <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>, and <a href="#events-Events-KeyboardEvent-repeat"><code>KeyboardEvent.repeat</code></a> are in use.</td></tr></table>
-               A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a key is pressed down. The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This event type shall be generated after the keyboard mapping but before the processing of an <a class="def" href="#glossary-ime">input method editor</a>, normally associated with the dispatching of a <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>, <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a>, or <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event. This event type must be dispatched before the <a class="eventtype" href="#event-type-compositionstart"><code>keypress</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events event associated with the same key.  Whether or not a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> contributes to the generation of a text event is implementation dependent.
-               
-               <p>if the document's currently focused element can receive text (such as a form input or an editable text block), the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a> attribute, and the focused element as the  <a class="def" href="#glossary-proximal-event-target">proximal event target</a>, and for that character to be appended to the text content of that element;</p>
-               
-               <p>The default action of the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event depends upon the key:</p>
-               <ul>
-                 <li>if the key is associated with a character, the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a> attribute
+            <dt id="event-type-keydown"><dfn>
+                <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keydown</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>, <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>, <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>, and <a href="#events-Events-KeyboardEvent-repeat"><code>KeyboardEvent.repeat</code></a> are in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a key is pressed down. The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This event type shall be generated after the keyboard mapping but before the processing of an <a class="def" href="#glossary-ime">input method editor</a>, normally associated with the dispatching of a <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>, <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a>, or <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event. This event type must be dispatched before the <a class="eventtype" href="#event-type-compositionstart"><code>keypress</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events event associated with the same key.  Whether or not a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> contributes to the generation of a text event is implementation dependent.</p>
+              <p>The default action of the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event depends upon the key:</p>
+              <ul>
+                <li>if the key is associated with a character, the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a> attribute
                    <ul>
                      <li>if the document's currently focused element can receive text (such as a form input or an editable text block), the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a> attribute, and the focused element as the value of the <a href="#events-event-type-target">Event.target</a> attribute, and for that character to be appended to the text content of that element</li>
                    </ul>
                  </li>
-                 <li>if the key is associated with a <a class="def" href="#glossary-text-composition-system">text composition system</a>, the default action shall be to launch that system</li>
-                 <li>if the key is the <code>tab</code> key, the default action shall be to shift the document focus from the currently focused element (if any) to the new focused element, as described in <a href="#events-focusevent">Focus Event Types</a></li>
-                 <li>if the key is the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> or <a href="#key-Space"><code class="value keyname">'Space'</code></a> key and the current focus is on a state-changing element, the default action shall be to dispatch a <a class="eventtype" href="#event-type-click"><code>click</code></a> event, and a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event if that event type is supported by the <a class="def" href="#glossary-user-agent">user agent</a> (refer to <a href="#event-flow-activation">activation triggers and behavior</a> for more details)</li>
-                 <li>if the key is associated with any other event type, such as the <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> event, the default action shall be to dispatch an event of that type.</li>
-               </ul>
-
-               
-               <p>If this event is canceled, the associated events types must not be dispatched, and the associated actions must not be performed.</p>
-
-               <p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events are traditionally associated with detecting any key, not just those which produce a <a class="def" href="#glossary-character-value">character value</a>.</p></dd>
+                <li>if the key is associated with a <a class="def" href="#glossary-text-composition-system">text composition system</a>, the default action shall be to launch that system</li>
+                <li>if the key is the <code>tab</code> key, the default action shall be to shift the document focus from the currently focused element (if any) to the new focused element, as described in <a href="#events-focusevent">Focus Event Types</a></li>
+                <li>if the key is the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> or <a href="#key-Space"><code class="value keyname">'Space'</code></a> key and the current focus is on a state-changing element, the default action shall be to dispatch a <a class="eventtype" href="#event-type-click"><code>click</code></a> event, and a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event if that event type is supported by the <a class="def" href="#glossary-user-agent">user agent</a> (refer to <a href="#event-flow-activation">activation triggers and behavior</a> for more details)</li>
+                <li>if the key is associated with any other event type, such as the <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> event, the default action shall be to dispatch an event of that type.</li>
+              </ul>
+              <p>If this event is canceled, the associated events types must not be dispatched, and the associated actions must not be performed.</p>
+              <p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events are traditionally associated with detecting any key, not just those which produce a <a class="def" href="#glossary-character-value">character value</a>.</p>
+            </dd>
           </dl>
         </div>
 
 <!-- keypress -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-keypress">
-              <a class="eventtype noxref" href="#event-type-keypress"><code>keypress</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keypress</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>, <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>, <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>, and <a href="#events-Events-KeyboardEvent-repeat"><code>KeyboardEvent.repeat</code></a> are in use.</td></tr></table>
-               A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a key is pressed down, if and only if that key normally produces a <a class="def" href="#glossary-character-value">character value</a>. The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This event type shall be generated after the keyboard mapping but before the processing of an <a class="def" href="#glossary-ime">input method editor</a>, normally associated with the dispatching of a <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>, <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a>, or <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event. This event type must be dispatched after the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event and before the <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event associated with the same key.
-
+            <dt id="event-type-keypress"><dfn>
+                <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keypress</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>, <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>, <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>, and <a href="#events-Events-KeyboardEvent-repeat"><code>KeyboardEvent.repeat</code></a> are in use.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a key is pressed down, if and only if that key normally produces a <a class="def" href="#glossary-character-value">character value</a>. The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This event type shall be generated after the keyboard mapping but before the processing of an <a class="def" href="#glossary-ime">input method editor</a>, normally associated with the dispatching of a <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>, <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a>, or <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event. This event type must be dispatched after the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event and before the <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event associated with the same key.</p>
               <p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event is traditionally associated with detecting a <a class="def" href="#glossary-character-value">character value</a> rather than a physical key, and may not be available on all keys in some configurations.</p>
-              
               <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type.</p>
             </dd>
           </dl>
@@ -3601,21 +3395,30 @@
 <!-- keyup -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-keyup">
-              <a class="eventtype noxref" href="#event-type-keyup"><code>keyup</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keyup</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>, and <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> are in use. <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, and <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a> are in use unless the <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> corresponds to the key modifier itself.</td></tr></table>
-               A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a key is released.  The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system.  This event type shall be generated after the keyboard mapping. This event type must be dispatched after the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> events event associated with the same key.  Whether or not a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> contributes to the generation of a text event is implementation dependent.
-
-               <p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events are traditionally associated with detecting any key, not just those which produce a <a class="def" href="#glossary-character-value">character value</a>.</p></dd>
+            <dt id="event-type-keyup"><dfn>
+                <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keyup</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>, and <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> are in use. <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, and <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a> are in use unless the <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> corresponds to the key modifier itself.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a key is released.  The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system.  This event type shall be generated after the keyboard mapping. This event type must be dispatched after the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> events event associated with the same key.  Whether or not a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> contributes to the generation of a text event is implementation dependent.</p>
+              <p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events are traditionally associated with detecting any key, not just those which produce a <a class="def" href="#glossary-character-value">character value</a>.</p>
+            </dd>
           </dl>
         </div>
       </div>
-      
-      
-<!-- div3 Events-eventgroupings-uievents -->
-      <div class="div3">
-        <h3 class="div3"><a id="events-compositionevents" href="#events-compositionevents">5.2.7 Composition Events Types</a></h3>
+<!-- div3 Events-eventgroupings-compositionevents -->
+      <div>
+        <h3><a id="events-compositionevents" href="#events-compositionevents">5.2.7 Composition Events Types</a></h3>
+
         <p>This module defines the feature CompositionEvents 3.0 and depends on the feature UIEvents 3.0.</p>
         <p>Composition Events provide a means for inputing text in a supplementary or alternate manner than by Keyboard Events, in order to allow the use of characters that may not be commonly available on keyboard. For example, Composition events may be used to add accents to characters despite their absence from standard US keyboards, to build up logograms of many Asian languages from their base components or categories, to select word choices from a combination of key presses on a mobile device keyboard, or to convert voice commands into text using a speech recognition processor.  Refer to <a href="#keyset">Keyboard events and key values</a> for examples on how Composition Events are used in combination with keyboard events.</p>
         <p>Conceptually, a composition session consists of one <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event, one or more <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> events, and one <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event, with the value of the <a href="#events-Events-CompositionEvent-data">data</a> attribute persisting between each "stage" of this event chain during each session.  While a composition session is active, keyboard events should not be dispatched to the DOM (i.e., the <a class="def" href="#glossary-text-composition-system">text composition system</a> "swallows" the keyboard events), and only <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> events may be dispatched to indicate the composition process.</p>
@@ -3633,33 +3436,30 @@
               <dd>
                 <div class="idl-code">
                   <pre>
-      // Introduced in DOM Level 3:
-      interface <a href="#events-Events-CompositionEvent">CompositionEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
-
-      readonly attribute DOMString       <a href="#events-Events-CompositionEvent-data">data</a>;
-      void               <a href="#events-event-type-initCompositionEvent">initCompositionEvent</a>(in DOMString typeArg, 
-                                 in boolean canBubbleArg, 
-                                 in boolean cancelableArg, 
-                                 in views::AbstractView viewArg, 
-                                 in DOMString dataArg);
-      };
-      </pre>
+// Introduced in DOM Level 3:
+interface <a href="#events-Events-CompositionEvent">CompositionEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
+  readonly attribute DOMString       <a href="#events-Events-CompositionEvent-data">data</a>;
+  void               <a href="#events-event-type-initCompositionEvent">initCompositionEvent</a>(in DOMString typeArg, 
+                             in boolean canBubbleArg, 
+                             in boolean cancelableArg, 
+                             in views::AbstractView viewArg, 
+                             in DOMString dataArg);
+};
+                  </pre>
                 </div>
                 <br />
               </dd>
-              <dt>
-                <strong>Attributes</strong>
-              </dt>
+
+              <dt><strong>Attributes</strong></dt>
               <dd>
                 <dl>
-                  <dt><code class="attribute-name"><a id="events-Events-CompositionEvent-data">data</a></code> of type <code>DOMString</code>, readonly
-                  </dt>
-                  <dd><code>data</code> holds the value of the characters generated by an input method. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class="noxref normative" href="#references-Unicode">Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <em>NFC</em>, defined in [<cite><a class="noxref normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute may be null or contain the empty string.<br /></dd>
+                  <dt><code class="attribute-name"><a id="events-Events-CompositionEvent-data">data</a></code> of type <code>DOMString</code>, readonly</dt>
+                  <dd><code>data</code> holds the value of the characters generated by an input method. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class="normative" href="#references-Unicode">Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <em>NFC</em>, defined in [<cite><a class="normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute may be null or contain the empty string.<br /></dd>
+
                 </dl>
               </dd>
-              <dt>
-                <strong>Methods</strong>
-              </dt>
+
+              <dt><strong>Methods</strong></dt>
               <dd>
                 <dl>
                   <dt>
@@ -3669,9 +3469,15 @@
                   </dt>
                   <dd>
                     <div class="method">Initializes attributes of a <code>CompositionEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.
-      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd><dt><code class="parameter-name">dataArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.<br /></dd></dl></div></div>
+                      <div class="parameters"><strong>Parameters</strong><div class="paramtable"><dl><dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">canBubbleArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">cancelableArg</code> of type <code>boolean</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt><dd>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class="parameter-name">dataArg</code> of type <code>DOMString</code></dt><dd>Specifies <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.<br /></dd>
+</dl></div></div>
                       <!-- parameters -->
                       <div><strong>No Return Value</strong></div>
+
                       <div><strong>No Exceptions</strong></div>
                     </div>
 <!-- method -->
@@ -3682,32 +3488,49 @@
           </dd>
         </dl>
         <p>The composition event types are listed below.</p>
-
-        <h4 class="div3 needswork"><a id="events-composition-event-order" href="#events-composition-event-order">5.2.7.1 Composition Event Order</a></h4>
+        <h4 class="needswork">
+          <a id="events-composition-event-order" href="#events-composition-event-order">5.2.7.1 Composition Event Order</a>
+        </h4>
         <p>The composition events defined in this specification occur in a set order relative to one another:</p>
         <ol>
-          <li><a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a></li>
+          <li>
+            <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>
+          </li>
           <li><a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> (multiple events)</li>
-          <li><a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a></li>
-        </ol>        
-
+          <li>
+            <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a>
+          </li>
+        </ol>
         <p>Composition events which are not canceled and which do not have the empty string as a value produce a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event as well.  The order of text events relative to composition events is as follows:</p>
         <ol>
-          <li><a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a></li>
+          <li>
+            <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>
+          </li>
           <li><a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> (multiple events)</li>
-          <li><a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a></li>
+          <li>
+            <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a>
+          </li>
           <li>If a <a class="def" href="#glossary-character-value">character value</a> is produced, <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a></li>
-        </ol>        
+        </ol>
 
 <!-- compositionstart -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-compositionstart">
-              <a class="eventtype noxref" href="#event-type-compositionstart"><code>compositionstart</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionstart</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td>Launch <a class="def" href="#glossary-text-composition-system">text composition system</a></td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, and <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> is invoked in preparation for composing a passage of text.  This event type is device-dependent, and may rely upon the capabilities of the text conversion system and how it is mapped into the operating system.  When a keyboard is used to feed an input method editor, this event type is generated after a <code>keydown</code> event, but speech or handwriting recognition systems may send this event type without keyboard events.  Some implemenations may populate the <a href="#events-Events-CompositionEvent-data"><code>data</code></a> attribute of the <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event with the text currently selected in the document (for editing and replacement); otherwise, the value of the <a href="#events-Events-CompositionEvent-data"><code>data</code></a> attribute shall be <code>null</code>.  
-              
+            <dt id="event-type-compositionstart"><dfn>
+                <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionstart</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td>Launch <a class="def" href="#glossary-text-composition-system">text composition system</a></td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, and <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> is invoked in preparation for composing a passage of text.  This event type is device-dependent, and may rely upon the capabilities of the text conversion system and how it is mapped into the operating system.  When a keyboard is used to feed an input method editor, this event type is generated after a <code>keydown</code> event, but speech or handwriting recognition systems may send this event type without keyboard events.  Some implemenations may populate the <a href="#events-Events-CompositionEvent-data"><code>data</code></a> attribute of the <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event with the text currently selected in the document (for editing and replacement); otherwise, the value of the <a href="#events-Events-CompositionEvent-data"><code>data</code></a> attribute shall be <code>null</code>.</p>
               <p>This event is dispatched immediately before a <a class="def" href="#glossary-text-composition-system">text composition system</a> is launched.  The default action of this event is to launch the appropriate <a class="def" href="#glossary-text-composition-system">text composition system</a>.  If this event is canceled, the <a class="def" href="#glossary-text-composition-system">text composition system</a> must not be launched.</p>
               <p>(<i class="issue" id="issue-composition_events"><strong>Issue:</strong> see <a href="http://lists.w3.org/Archives/Public/www-dom/2009JulSep/0143.html" title="Extra notes on composition events from Daniel Danilatos on 2009-08-07 ([email protected] from July to September 2009)">Extra notes on composition events</a> for more details.</i>)</p>
             </dd>
@@ -3717,32 +3540,54 @@
 <!-- compositionupdate -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-compositionupdate">
-              <a class="eventtype noxref" href="#event-type-compositionupdate"><code>compositionupdate</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionupdate</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>No</td></tr><tr class="assert must"><th>Default action</th><td>none</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, and <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> should dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> updates its active text passage with a new character, which is added to the string in <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.  Note that some <a class="def" href="#glossary-text-composition-system">text composition systems</a> may not expose this information to the DOM, in which case this event will not fire during the composition process.  If the composition session is canceled, this event will be fired immediately before the <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event, and the <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code> attribute will be set to <code>null</code><i class="issue" id="issue-null_vs_empty-string">(<strong>Issue:</strong> "null" or "empty string"? What's the distinction?)</i>.</a></dd>
+            <dt id="event-type-compositionupdate"><dfn>
+                <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionupdate</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+                <tr class="assert must"><th>Default action</th><td>none</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, and <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> should dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> updates its active text passage with a new character, which is added to the string in <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.  Note that some <a class="def" href="#glossary-text-composition-system">text composition systems</a> may not expose this information to the DOM, in which case this event will not fire during the composition process.  If the composition session is canceled, this event will be fired immediately before the <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event, and the <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code> attribute will be set to <code>null</code><i class="issue" id="issue-null_vs_empty-string">(<strong>Issue:</strong> "null" or "empty string"? What's the distinction?)</i>.</a></p>
+            </dd>
           </dl>
         </div>
 
 <!-- compositionend -->
         <div class="event-definition assert must">
           <dl>
-            <dt id="event-type-compositionend">
-              <a class="eventtype noxref" href="#event-type-compositionend"><code>compositionend</code></a>
-            </dt>
-            <dd><table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0"><tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionend</code></strong></td></tr><tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr><tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr><tr class="assert must"><th>Bubbles</th><td>Yes</td></tr><tr class="assert must"><th>Target</th><td><code>Element</code></td></tr><tr class="assert must"><th>Cancelable</th><td>Yes</td></tr><tr class="assert must"><th>Default action</th><td><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event</td></tr><tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, and <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</td></tr></table>
-              A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> completes the composition of its active text passage, or cancels the composition process.  If the result of the <a class="def" href="#glossary-text-composition-system">text composition system</a> is not null and does not contain the empty string, this event type will be followed by a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type with the appropriate <a href="#events-Events-TextEvent-inputMode">inputMode</a> value, such as <a href="#events-DOM_INPUT_METHOD_IME">DOM_INPUT_METHOD_IME</a>, <a href="#events-DOM_INPUT_METHOD_HANDWRITING">DOM_INPUT_METHOD_HANDWRITING</a>, <a href="#events-DOM_INPUT_METHOD_VOICE">DOM_INPUT_METHOD_VOICE</a>, or <a href="#events-DOM_INPUT_METHOD_MULTIMODAL">DOM_INPUT_METHOD_MULTIMODAL</a>.
-              
+            <dt id="event-type-compositionend"><dfn>
+                <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a>
+              </dfn></dt>
+            <dd>
+              <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+                <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionend</code></strong></td></tr>
+                <tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
+                <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+                <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
+                <tr class="assert must"><th>Cancelable</th><td>Yes</td></tr>
+                <tr class="assert must"><th>Default action</th><td><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event</td></tr>
+                <tr class="assert must"><th>Context info</th><td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>, and <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</td></tr>
+              </table>
+              <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> completes the composition of its active text passage, or cancels the composition process.  If the result of the <a class="def" href="#glossary-text-composition-system">text composition system</a> is not null and does not contain the empty string, this event type will be followed by a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type with the appropriate <a href="#events-Events-TextEvent-inputMode">inputMode</a> value, such as <a href="#events-DOM_INPUT_METHOD_IME">DOM_INPUT_METHOD_IME</a>, <a href="#events-DOM_INPUT_METHOD_HANDWRITING">DOM_INPUT_METHOD_HANDWRITING</a>, <a href="#events-DOM_INPUT_METHOD_VOICE">DOM_INPUT_METHOD_VOICE</a>, or <a href="#events-DOM_INPUT_METHOD_MULTIMODAL">DOM_INPUT_METHOD_MULTIMODAL</a>.</p>
               <p>This event is dispatched immediately after the <a class="def" href="#glossary-text-composition-system">text composition system</a> is completed (e.g. the <a class="def" href="#glossary-ime">IME</a> closed, minimized, switched out of focus, or otherwise dismissed, with the focus switched back to the <a class="def" href="#glossary-user-agent">user agent</a>).  The default action of this event is to dispatch the <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type as described above.  If this event is canceled, the <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type must not be dispatch, no matter the value of the <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a> attribute.  Note that canceling the <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> <em>event type</em> is distinct from canceling the <a class="def" href="#glossary-text-composition-system">text composition system</a> session (e.g. by hitting a cancel button or closing an <a class="def" href="#glossary-ime">IME</a> window).</p>
             </dd>
           </dl>
         </div>
-        <div class="div3">
-          <h4 class="adiv3"><a id="handwriting" href="#handwriting">5.2.7.2 Handwriting Recognition Systems</a></h4>
+
+        <div>