--- a/html/DOM3-Events.html Fri Jul 17 11:07:06 2009 +0900
+++ b/html/DOM3-Events.html Mon Jul 20 13:59:10 2009 +0900
@@ -125,465 +125,202 @@
<dd><a href="http://bjoern.hoehrmann.de/">Björn Höhrmann</a> Invited Expert (until December 2007)</dd>
<dd>Philippe Le Hégaret, <em>W3C (until November 2003)</em></dd>
<dd>Tom Pixley, <em>Netscape Communications Corporation (until July 2002)</em></dd>
+ <dd>Arnaud Le Hors, W3C (until November 2003)</dd>
+ <dd>Robert S. Sutor, IBM Research (for DOM Level 1)</dd>
</dl>
- <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2008 <a href="http://www.w3.org/">
- <acronym title="World Wide Web Consortium">W3C</acronym>
- </a><sup>®</sup> (<a href="http://www.csail.mit.edu/">
- <acronym title="Massachusetts Institute of Technology">MIT</acronym>
- </a>, <a href="http://www.ercim.org/">
- <acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym>
- </a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
+
+ <p class="copyright" id="copyright-copy-2009-w3creg-mit-ercim-kei"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
+ © 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web
+ Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute
+ of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium
+ for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+ <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
+ and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
+ use</a> rules apply.</p>
+
+
</div>
<hr title="separator from header"/>
<h2 id="Overview-abstract">Abstract</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 class="noxref" href="#references-DOM2Events">DOM Level 2 Events</a>].</p>
</div>
- <h2 id="Overview-status">Status of this document</h2>
- <div class="status">
- <p>This document is for review by the <a href="http://www.w3.org/2006/webapi/">WebAPI Working Group</a> and is subject to change without notice. This document has no formal standing within W3C. Please consult the <a href="http://www.w3.org/2006/webapi/">group's home page</a> and the <a href="http://www.w3.org/TR/">W3C technical reports index</a> for information about the latest publications by this group.</p>
+
+ <h2 class="no-num no-toc" id="sotd">Status of this Document</h2>
+
+ <div>
+
+ <p id="this-section-describes-the-status-of-thi"><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 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
+ connection with the deliverables of the group; that page also includes
+ instructions for disclosing a patent. An individual who has actual
+ knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
+ Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the W3C Patent Policy</a>.</p>
+
+ <p id="working-draft">This is the 16 July 2009 Working Draft version of the "Document Object Model (DOM) Level 3 Events" specification. This document was previously published as a W3C Note, pending further feedback from implementers, and is now being revised to reflect the current state of implementation. It is expected that this specification will progress to Recommendation status.</p>
+
+ <p id="this-document-is-produced-by-the-web-app">This document is produced
+ by the <a href="http://www.w3.org/2008/webapps/">Web Applications WG</a>,
+ part of the <a href="http://www.w3.org/2006/rwc/Activity">Rich Web
+ Clients Activity</a> in the W3C <a href="http://www.w3.org/Interaction/">Interaction Domain</a>. It is
+ expected that this document will progress along the W3C's Recommendation
+ track. 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="latest-editors-draft"><strong>You can find the
+ latest <a href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html">Editor's Draft</a>
+ of this document in the <a href="http://dev.w3.org/">W3C's CVS
+ repository</a>, which is updated on a regular basis.</strong> The
+ public is encouraged to send comments to the WebApps Working Group's
+ public mailing list for DOM specifications <a href="mailto:www-dom@@w3.org">www-dom@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/www-dom@/">archive</a>).
+ See <a href="http://www.w3.org/Mail/">W3C mailing list and archive usage
+ guidelines</a>. <!-- A detailed <a href="http://dev.w3.org/cvsweb/2009/dom/">list of changes</a>
+ from the previous version is also available from the W3C's CVS server. --></p>
+
+ <p id="unstable"><strong class="redNote">Implementers should be aware that this document is not
+ stable.</strong> Implementers who are not taking part in the discussions
+ are likely to find the specification changing out from under them in
+ incompatible ways. Vendors interested in implementing this document
+ 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 name="Overview-contents" id="Overview-contents">Table of Contents</a>
- </h2>
+ <h2 id="Overview-table-of-contents"><a name="Overview-contents" id="Overview-contents">Table of Contents</a></h2>
<ul class="toc">
- <li class="tocline2">
- <a class="tocxref" href="#expanded-toc">Expanded Table of Contents</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#copyright-notice">W3C Copyright Notices and Licenses</a>
- </li>
- </ul>
- <ul class="toc">
- <li class="tocline2">
- <a class="tocxref" href="#events">1. Document Object Model Events</a>
- </li>
- </ul>
- <ul class="toc">
- <li class="tocline2">
- <a class="tocxref" href="#glossary">Glossary</a>
+ <li><a href="#events-Events">1. Document Object Model Events</a>
+ <ul class="toc">
+ <li><a href="#events-Events-overview">1.1 Introduction</a></li>
+ <li><a href="#events-Conformance">1.2 Conformance</a></li>
+ </ul>
</li>
- <li class="tocline2">
- <a class="tocxref" href="#keyset">Appendix A: Keyboard events and key identifiers</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#changes">Appendix B: Changes</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#security-considerations">Appendix C: Security Considerations</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#idl-definitions">Appendix D: IDL Definitions</a>
+ <li><a href="#glossary-role-glossary" class="glossary">2. Glossary</a></li>
+ <li><a href="#events-Events-flow">3. DOM Event Architecture</a>
+ <ul class="toc">
+ <li><a href="#events-Events-flow">3.1 Event dispatch and DOM event flow</a></li>
+ <li><a href="#events-Events-flow-cancelation">3.2 Default actions and cancelable events</a></li>
+ <li><a href="#events-Events-flow-activation">3.3 Activation requests and behavior</a></li>
+ </ul>
</li>
- <li class="tocline2">
- <a class="tocxref" href="#java-binding">Appendix E: Java Language Binding</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#ecma-script-binding">Appendix F: ECMAScript Language Binding</a>
+ <li><a href="#events-Events-interface">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="#events-Events-document">4.5 Event creation</a></li>
+ <li><a href="#interface-DocumentEvent">4.5.1 Interface DocumentEvent</a></li>
+ </ul>
</li>
- <li class="tocline2">
- <a class="tocxref" href="#acknowledgements">Appendix G: Acknowledgements</a>
+ <li><a href="#events-Events">5. Events</a>
+ <ul class="toc">
+ <li><a href="#events-Event-types">5.1 Event Types</a>
+ <ul class="toc">
+ <li><a href="#events-Events-EventTypes-complete">5.1.1 Complete List of Event Types</a></li>
+ </ul>
+ </li>
+ <li><a href="#events-Events-definitions">5.2 Event Module Definitions</a>
+ <ul class="toc">
+ <li><a href="#events-Events-eventgroupings-uievents">5.2.1 User Interface Event Types</a></li>
+ <li><a href="#events-Events-eventgroupings-basicevents">5.2.2 Basic Event Types</a></li>
+ <li><a href="#events-Events-eventgroupings-mouseevents">5.2.3 Mouse Event Types</a></li>
+ <li><a href="#events-Events-eventgroupings-mousewheelevents">5.2.4 Mouse Wheel Event Types</a></li>
+ <li><a href="#events-Events-eventgroupings-wheelevents">5.2.5 Wheel Event Types</a></li>
+ <li><a href="#events-Events-TextEvents-Interfaces">5.2.6 Text Events Types</a></li>
+ <li><a href="#events-Events-KeyboardEvents-Interfaces">5.2.7 Keyboard Event Types</a></li>
+ <li><a href="#events-Events-eventgroupings-mutationevents">5.2.8 Mutation Events</a></li>
+ <li><a href="#events-Events-eventgroupings-mutationnameevents">5.2.9 Mutation Name Event Types</a></li>
+ </ul>
+ </li>
+ </ul>
</li>
- <li class="tocline2">
- <a class="tocxref" href="#references">References</a>
+ <li><a href="#keyset-KeySet">Appendix A: Keyboard events and key identifiers</a>
+ <ul class="toc">
+ <li><a href="#keyset-KeySet-intro">A.1 Introduction</a>
+ <ul class="toc">
+ <li><a href="#keyset-Modifiers">A.1.1 Modifier keys</a></li>
+ <li><a href="#keyset-DeadKeys">A.1.2 Dead keys</a></li>
+ <li><a href="#keyset-IME">A.1.3 Input Method Editors</a></li>
+ <li><a href="#keyset-cancelable_keys">A.1.4 Default actions and cancelable keyboard events</a></li>
+ <li><a href="#keyset-Guide">A.1.5 Guidelines for defining key identifiers</a></li>
+ </ul>
+ </li>
+ <li><a href="#keyset-KeySet-Set">A.2 Key identifiers set</a>
+ <ul class="toc">
+ <li><a href="#keyset-KeySet-Set-keyCode-charCode">A.2.1 Key identifiers, keyCode, and charCode</a></li>
+ </ul>
+ </li>
+ </ul>
</li>
- <li class="tocline2">
- <a class="tocxref" href="#def-index">Index</a>
+ <li><a href="#changes-Changes">Appendix B: Changes</a>
+ <ul class="toc">
+ <li><a href="#changes-DOMEvents2to3Changes">B.1 Changes between DOM Level 2 Events and DOM Level 3 Events</a>
+ <ul class="toc">
+ <li><a href="#changes-DOMEvents2to3Changes-flow">B.1.1 Changes to DOM Level 2 event flow</a></li>
+ <li><a href="#changes-DOMEvents2to3Changes-event-types">B.1.2 Changes to DOM Level 2 event types</a></li>
+ <li><a href="#changes-DOMLevel2to3Changes">B.1.3 Changes to DOM Level 2 Events interfaces</a></li>
+ <li><a href="#changes-DOMLevel3Addons">B.1.4 New Interfaces</a></li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ <li><a href="#security-considerations-Security">Appendix C: Security Considerations</a></li>
+ <li><a href="#idl-definitions-idl">Appendix D: IDL Definitions</a>
+ <!-- <ul class="toc">
+ <li><a href="#idl-definitions-idl-events.idl"></a><a href="idl/events.idl">events.idl</a></li>
+ </ul> -->
+ </li>
+ <li><a href="#java-binding-java-binding">Appendix E: Java Language Binding</a>
+ <!-- <ul class="toc">
+ <li><a href="#java-binding-org.w3c.dom.events.EventException">EventException.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.Event">Event.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.CustomEvent">CustomEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.EventTarget">EventTarget.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.EventListener">EventListener.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.DocumentEvent">DocumentEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.UIEvent">UIEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.TextEvent">TextEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.KeyboardEvent">KeyboardEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.MouseEvent">MouseEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.WheelEvent">WheelEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.MouseWheelEvent">MouseWheelEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.MutationEvent">MutationEvent.java</a></li>
+ <li><a href="#java-binding-org.w3c.dom.events.MutationNameEvent">MutationNameEvent.java</a></li>
+ </ul> -->
+ </li>
+ <li><a href="#ecma-script-binding-ecma-binding">Appendix F: ECMAScript Language Binding</a></li>
+ <li><a href="#acknowledgements-contributors">Appendix G: Acknowledgements</a>
+ <ul class="toc">
+ <li><a href="#acknowledgements-Productions">G.1 Production Systems</a>
+ </ul>
+ </li>
+ <li><a href="#references-role-references" class="references">References</a>
+ <ul class="toc">
+ <li><a href="#references-References-Normative">H.1 Normative References</a>
+ <li><a href="#references-References-Informative">H.2 Informative References</a></li>
+ </ul>
</li>
</ul>
- <div id="expanded-toc" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2009</p>
- </div>
- <div class="div1">
- <h1 id="expanded-toc-TOC" class="div1">Expanded Table of Contents</h1>
- <ul class="toc">
- <li class="tocline2">
- <a class="tocxref" href="#expanded-toc">Expanded Table of Contents</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#copyright-notice">W3C Copyright Notices and Licenses</a>
- <ul class="toc">
- <li class="tocline3">
- <a class="tocxref" href="#copyright-notice-Copyright-notice-document">W3C<sup>®</sup> Document Copyright Notice and License</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#copyright-notice-Copyright-notice-software">W3C<sup>®</sup> Software Copyright Notice and License</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#copyright-notice-Copyright-short-notice">W3C<sup>®</sup> Short Software Notice</a>
- </li>
- </ul>
- </li>
- </ul>
- <ul class="toc">
- <li class="tocline2">
- <a class="tocxref" href="#events">1 Document Object Model Events</a>
- <ul class="toc">
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-overview">1.1 Introduction</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#events-Conformance">1.1.1 Conformance</a>
- </li>
- </ul>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-flow">1.2 Event dispatch and DOM event flow</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-flow-cancelation">1.3 Default actions and cancelable events</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-flow-activation">1.4 Activation requests and behavior</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Event-types">1.5 Event types</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-EventTypes-complete">1.5.1 Complete list of event types</a>
- </li>
- </ul>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-interface">1.6 Basic interfaces</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-document">1.6.1 Event creation</a>
- </li>
- </ul>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-eventgroupings">1.7 Event module definitions</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-uievents">1.7.1 User Interface event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-TextEvents-Interfaces">1.7.2 Text events types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-KeyboardEvents-Interfaces">1.7.3 Keyboard event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mouseevents">1.7.4 Mouse event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mousewheelevents">1.7.5 Mouse wheel event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-wheelevents">1.7.6 Wheel event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mutationevents">1.7.7 Mutation event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mutationnameevents">1.7.8 Mutation name event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-basicevents">1.7.9 Basic event types</a>
- </li>
- </ul>
- </li>
- </ul>
- </li>
- </ul>
- <ul class="toc">
- <li class="tocline2">
- <a class="tocxref" href="#glossary">Glossary</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#keyset">Appendix A: Keyboard events and key identifiers</a>
- <ul class="toc">
- <li class="tocline3">
- <a class="tocxref" href="#keyset-KeySet-intro">A.1 Introduction</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#keyset-Modifiers">A.1.1 Modifier keys</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#keyset-DeadKeys">A.1.2 Dead keys</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#keyset-IME">A.1.3 Input Method Editors</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#keyset-cancelable_keys">A.1.4 Default actions and cancelable keyboard events</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#keyset-Guide">A.1.5 Guidelines for defining key identifiers</a>
- </li>
- </ul>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#keyset-KeySet-Set">A.2 Key identifiers set</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#keyset-KeySet-Set-keyCode-charCode">A.2.1 Key identifiers, keyCode, and charCode</a>
- </li>
- </ul>
- </li>
- </ul>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#changes">Appendix B: Changes</a>
- <ul class="toc">
- <li class="tocline3">
- <a class="tocxref" href="#changes-DOMEvents2to3Changes">B.1 Changes between DOM Level 2 Events and DOM Level 3 Events</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#changes-DOMEvents2to3Changes-flow">B.1.1 Changes to DOM Level 2 event flow</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#changes-DOMEvents2to3Changes-event-types">B.1.2 Changes to DOM Level 2 event types</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#changes-DOMLevel2to3Changes">B.1.3 Changes to DOM Level 2 Events interfaces</a>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#changes-DOMLevel3Addons">B.1.4 New Interfaces</a>
- </li>
- </ul>
- </li>
- </ul>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#security-considerations">Appendix C: Security Considerations</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#idl-definitions">Appendix D: IDL Definitions</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#java-binding">Appendix E: Java Language Binding</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#ecma-script-binding">Appendix F: ECMAScript Language Binding</a>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#acknowledgements">Appendix G: Acknowledgements</a>
- <ul class="toc">
- <li class="tocline3">
- <a class="tocxref" href="#acknowledgements-Productions">G.1 Production Systems</a>
- </li>
- </ul>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#references">References</a>
- <ul class="toc">
- <li class="tocline3">
- <a class="tocxref" href="#references-References-Normative">1 Normative References</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#references-References-Informative">2 Informative References</a>
- </li>
- </ul>
- </li>
- <li class="tocline2">
- <a class="tocxref" href="#def-index">Index</a>
- </li>
- </ul>
- </div>
- <!-- div1 TOC -->
- <div id="copyright-notice" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2009</p>
- </div>
- <div class="div1">
- <h1 id="copyright-notice-Copyright-Notice" class="div1">W3C Copyright Notices and Licenses</h1>
- <p>
- <strong>Copyright © 2009 <a class="normative" href="http://www.w3.org/">World Wide Web Consortium</a>, (<a class="normative" href="http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a class="normative" href="http://www.ercim.org/">European Research Consortium for Informatics and Mathematics</a>, <a class="normative" href="http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved.</strong>
- </p>
- <p>This document is published under the <a href="#copyright-notice-Copyright-notice-document">W3C<sup>®</sup> Document Copyright Notice and License</a>. The bindings within this document are published under the <a href="#copyright-notice-Copyright-notice-software">W3C<sup>®</sup> Software Copyright Notice and License</a>. The software license requires "Notice of any changes or modifications to the W3C files, including the date changes were made." Consequently, modified versions of the DOM bindings must document that they do not conform to the W3C standard; in the case of the IDL definitions, the pragma prefix can no longer be 'w3c.org'; in the case of the Java language binding, the package names can no longer be in the 'org.w3c' package.</p>
- <div class="div2">
- <hr width="50" align="center" title="Area separator"/>
- <h2 id="copyright-notice-Copyright-notice-document" class="div2">W3C<sup>®</sup> Document Copyright Notice and License</h2>
- <p><strong>Note:</strong> This section is a copy of the W3C<sup>®</sup> Document Notice and License and could be found at <a class="normative" href="http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231">http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231</a>.</p>
- <p>
- <strong>Copyright © 2009 <a class="normative" href="http://www.w3.org/">World Wide Web Consortium</a>, (<a class="normative" href="http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a class="normative" href="http://www.ercim.org/">European Research Consortium for Informatics and Mathematics</a>, <a class="normative" href="http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved.</strong>
- </p>
- <p>
- <strong>http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231</strong>
- </p>
- <p>Public documents on the W3C site are provided by the copyright holders under the following license. By using and/or copying this document, or the W3C document from which this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:</p>
- <p>Permission to copy, and distribute the contents of this document, or the W3C document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on <em>ALL</em> copies of the document, or portions thereof, that you use:</p>
- <ol>
- <li>A link or URL to the original W3C document.</li>
- <li>The pre-existing copyright notice of the original author, or if it doesn't exist, a notice (hypertext is preferred, but a textual representation is permitted) of the form: "Copyright © [$date-of-document] <a class="normative" href="http://www.w3.org/">World Wide Web Consortium</a>, (<a class="normative" href="http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a class="normative" href="http://www.ercim.org/">European Research Consortium for Informatics and Mathematics</a>, <a class="normative" href="http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved. <a class="normative" href="http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231">http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231</a>"</li>
- <li><em>If it exists</em>, the STATUS of the W3C document.</li>
- </ol>
- <p>When space permits, inclusion of the full text of this <strong>NOTICE</strong> should be provided. We request that authorship attribution be provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.</p>
- <p>No right to create modifications or derivatives of W3C documents is granted pursuant to this license. However, if additional requirements (documented in the <a class="normative" href="http://www.w3.org/Consortium/Legal/IPR-FAQ">Copyright FAQ</a>) are satisfied, the right to create modifications or derivatives is sometimes granted by the W3C to individuals complying with those requirements.</p>
- <p>THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.</p>
- <p>COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.</p>
- <p>The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to this document or its contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright holders.</p>
- </div>
- <!-- div2 Copyright-notice-document -->
- <div class="div2">
- <hr width="50" align="center" title="Area separator"/>
- <h2 id="copyright-notice-Copyright-notice-software" class="div2">W3C<sup>®</sup> Software Copyright Notice and License</h2>
- <p><strong>Note:</strong> This section is a copy of the W3C<sup>®</sup> Software Copyright Notice and License and could be found at <a class="normative" href="http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231">http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231</a></p>
- <p>
- <strong>Copyright © 2009 <a class="normative" href="http://www.w3.org/">World Wide Web Consortium</a>, (<a class="normative" href="http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a class="normative" href="http://www.ercim.org/">European Research Consortium for Informatics and Mathematics</a>, <a class="normative" href="http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved.</strong>
- </p>
- <p>
- <strong>http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231</strong>
- </p>
- <p>This work (and included software, documentation such as READMEs, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.</p>
- <p>Permission to copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications:</p>
- <ol>
- <li>The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.</li>
- <li>Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the <a href="#copyright-notice-Copyright-short-notice">W3C<sup>®</sup> Short Software Notice</a> should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative code.</li>
- <li>Notice of any changes or modifications to the files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)</li>
- </ol>
- <p>THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.</p>
- <p>COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.</p>
- <p>The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.</p>
- </div>
- <!-- div2 Copyright-notice-software -->
- <div class="div2">
- <h2 id="copyright-notice-Copyright-short-notice" class="div2">W3C<sup>®</sup> Short Software Notice</h2>
- <p><strong>Note:</strong> This section is a copy of the W3C<sup>®</sup> Short Software Notice and could be found at <a class="normative" href="http://www.w3.org/Consortium/Legal/2002/copyright-software-short-notice-20021231">http://www.w3.org/Consortium/Legal/2002/copyright-software-short-notice-20021231</a></p>
- <p>
- <strong>Copyright © 2009 <a class="normative" href="http://www.w3.org/">World Wide Web Consortium</a>, (<a class="normative" href="http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a class="normative" href="http://www.ercim.org/">European Research Consortium for Informatics and Mathematics</a>, <a class="normative" href="http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved.</strong>
- </p>
- <p>Copyright © [$date-of-software] <a class="normative" href="http://www.w3.org/">World Wide Web Consortium</a>, (<a class="normative" href="http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a class="normative" href="http://www.ercim.org/">European Research Consortium for Informatics and Mathematics</a>, <a class="normative" href="http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved. This work is distributed under the W3C<sup>®</sup> Software License [1] in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.</p>
- <p>[1] http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231</p>
- </div>
- <!-- div2 Copyright-short-notice -->
- </div>
- <!-- div1 Copyright-Notice -->
- <div id="events" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2009</p>
</div>
<div class="div1">
<h1 id="events-Events" class="div1">1. Document Object Model Events</h1>
- <dl>
- <dt><em>Editors</em>:</dt>
- <dd>Doug Schepers, W3C</dd>
- <dd><a href="http://bjoern.hoehrmann.de/">Björn Höhrmann</a> Invited Expert (until December 2007)</dd>
- <dd>Philippe Le Hégaret, W3C (until November 2003)</dd>
- <dd>Tom Pixley, Netscape Communications Corporation (until July 2002)</dd>
- </dl>
- <div class="noprint">
- <h2 id="events-table-of-contents">Table of Contents</h2>
- <ul class="toc">
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-overview">1.1 Introduction</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#events-Conformance">1.1.1 Conformance</a>
- </li>
- </ul>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-flow">1.2 Event dispatch and DOM event flow</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-flow-cancelation">1.3 Default actions and cancelable events</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-flow-activation">1.4 Activation requests and behavior</a>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Event-types">1.5 Event types</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-EventTypes-complete">1.5.1 Complete list of event types</a>
- </li>
- </ul>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-interface">1.6 Basic interfaces</a>
- <ul class="toc">
- <li class="tocline4"><a href="#events-Events-Event">Event</a>, <a href="#events-Events-CustomEvent">CustomEvent</a>, <a href="#events-Events-EventTarget">EventTarget</a>, <a href="#events-Events-EventListener">EventListener</a>, <a href="#events-Events-EventException">EventException</a>, <a href="#events-Events-EventException-EventExceptionCode">EventExceptionCode</a></li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-document">1.6.1 Event creation</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-DocumentEvent">DocumentEvent</a>
- </li>
- </ul>
- </li>
- </ul>
- </li>
- <li class="tocline3">
- <a class="tocxref" href="#events-Events-eventgroupings">1.7 Event module definitions</a>
- <ul class="toc">
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-uievents">1.7.1 User Interface event types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-UIEvent">UIEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-TextEvents-Interfaces">1.7.2 Text events types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-TextEvent">TextEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-KeyboardEvents-Interfaces">1.7.3 Keyboard event types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-KeyboardEvent">KeyboardEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mouseevents">1.7.4 Mouse event types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-MouseEvent">MouseEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mousewheelevents">1.7.5 Mouse wheel event types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-MouseWheelEvent">MouseWheelEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-wheelevents">1.7.6 Wheel event types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-WheelEvent">WheelEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mutationevents">1.7.7 Mutation event types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-MutationEvent">MutationEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-mutationnameevents">1.7.8 Mutation name event types</a>
- <ul>
- <li class="tocline5">
- <a href="#events-Events-MutationNameEvent">MutationNameEvent</a>
- </li>
- </ul>
- </li>
- <li class="tocline4">
- <a class="tocxref" href="#events-Events-eventgroupings-basicevents">1.7.9 Basic event types</a>
- </li>
- </ul>
- </li>
- </ul>
- </div>
+
<div class="div2">
<h2 id="events-Events-overview" class="div2">1.1 Introduction</h2>
<p>DOM Events is designed with two main goals. The first goal is the design of an <a href="#glossary-dt-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 href="#glossary-dt-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 id="events-Conformance" class="div3">1.1.1 Conformance</h3>
+ <h3 id="events-Conformance" class="div3">1.2 Conformance</h3>
<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">DOM Level 3 Core</a></cite>] and the general considerations for DOM implementations apply. For example, handling of <a href="#glossary-dt-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>, and 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>. 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">DOM Level 3 Core</a></cite>].</p>
<p>An implementation is DOM Level 3 Events conformant if it supports the Core module defined in [<cite><a class="noxref normative" href="#references-DOM2Core">DOM Level 2 Core</a></cite>], the <a href="#events-Events-flow">Event dispatch and DOM event flow</a> mechanism and the interfaces with their associated semantics defined in <a href="#events-Events-interface">Basic interfaces</a>. An implementation conforms to a DOM Level 3 Events module if it conforms to DOM Level 3 Events, the event types defined in the module, and the modules the module depends upon (if any).</p>
@@ -597,28 +334,113 @@
<!-- div3 Conformance -->
</div>
+ <!-- div1 glossary -->
+ <div class="div1" id="glossary-glossary">
+ <h1 id="glossary-role-glossary" class="glossary">2. Glossary</h1>
+ <p class="first">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-dt-activation-behavior">activation behavior</dt>
+ <dd>The action taken when an <a href="#glossary-dt-event">event</a>, typically initiated by users through an input device, causes an element to fulfill a defined role. The role may be defined for that element by the host language, or by author-defined variables, or both. The role 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><a></code> element shall be to cause the user agent 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><input></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.</dd>
+
+ <dt id="glossary-dt-bubbling-phase">bubbling phase</dt>
+ <dd>The process by which an <a href="#glossary-dt-event">event</a> can be handled by one of the target ancestors after being handled by the <a href="#glossary-dt-target-node">target node</a>.</dd>
+
+ <dt id="glossary-dt-capture-phase">capture phase</dt>
+ <dd>The process by which an <a href="#glossary-dt-event">event</a> can be handled by one of the target ancestors before being handled by the <a href="#glossary-dt-target-node">target node</a>.</dd>
+
+ <dt id="glossary-dt-dead-key">dead key</dt>
+ <dd>A dead key is a key or combination of key that produces no character by itself, but which in combination or sequence with another key produces a modified character, such as a character with diacritical marks (e.g. <code>ö</code>, <code>é</code>, <code>â</code>).</dd>
+
+ <dt id="glossary-dt-default-action">default action</dt>
+ <dd>A <a href="#glossary-dt-default-action">default action</a> is a supplementary behavior that an implementation must perform in combination with the dispatch of the event object. Each event, and each specification, defines the <a href="#glossary-dt-default-action">default action</a> for that event. A <a href="#glossary-dt-default-action">default action</a> may be cancelled through the invocation of the <a href="#events-Events-Event-preventDefault"><code>Event.preventDefault()</code></a> method. For more details, see <a href="#events-Events-flow-cancelation">Default actions and cancelable events</a>.</dd>
+
+ <dt id="glossary-dt-defaultView">defaultView</dt>
+ <dd>The <code>defaultView</code> is the <a href="http://www.w3.org/TR/DOM-Level-2-Views/views.html#Views-AbstractView" title="Document Object Model Views"><code>AbstractView</code> interface</a> of the <code>Document</code>'s <a href="http://www.w3.org/TR/DOM-Level-2-Views/views.html#Views-DocumentView" title="Document Object Model Views"><code>DocumentView</code> interface</a>, which serves as a reference to the containing frame or window. This interface may also be accessed as the <code>Window</code> interface in many implementations.</dd>
+
+ <dt id="glossary-dt-dispatch">dispatch</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.</dd>
+
+ <dt id="glossary-dt-DOM-Level-0">DOM Level 0</dt>
+ <dd>The term "DOM Level 0" refers to a mix (not formally specified) of HTML document functionalities offered by Netscape Navigator version 3.0 and Microsoft Internet Explorer version 3.0. In some cases, attributes or methods have been included for reasons of backward compatibility with "DOM Level 0".</dd>
+
+ <dt id="glossary-dt-event">event</dt>
+ <dd>An event is the representation of some asynchronous occurrence (such as a mouse click on the presentation of the element, or the removal of child node from an element, or any of unthinkably many other possibilities) that gets associated with an <a href="#glossary-dt-event-target">event target</a>.</dd>
+
+ <dt id="glossary-dt-event-phase">event phase</dt>
+ <dd>See <a href="#glossary-dt-phase">phase</a>.</dd>
+
+ <dt id="glossary-dt-event-type">event target</dt>
+ <dd>The object to which an <a href="#glossary-dt-event">event</a> is targeted.</dd>
+
+ <dt id="glossary-dt-event-type">event type</dt>
+ <dd>An <a href="#glossary-dt-event">event</a> object which defines particular trigger conditions, properties, interfaces, and other characteristics which distinguish it from other event types. For example, the <a href="#events-event-click"><code>click</code></a> event type has different characteristics than the <a href="#events-event-mouseover"><code>mouseover</code></a> or <a href="#events-event-load"><code>load</code></a> event types. The event type is exposed as the <a class="noxref" href="#events-Events-Event-type"><code class="interface-attribute">type</code></a> attribute on the event object. See <a href="#events-Event-types">event types</a> for more details. Also loosely referred to as 'event', such as the <em><code>click</code> event</em>.</dd>
+
+ <dt id="glossary-dt-host-language">host language</dt>
+ <dd>Any language which integrates the features of another language, while normatively referencing the origin language rather than redefining those features, and extending those features only in ways defined by the origin language. An origin language 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-dt-ime">IME</dt>
+ <dt id="glossary-dt-input-method-editor">input method editor</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 IME may also be used for dictionary-based word completion, such as on mobile devices. See <a href="#keyset-IME">Input Method Editors</a> in Appendix A for treatment of IMEs in this specification.</dd>
+
+ <dt id="glossary-dt-localname">local name</dt>
+ <dd>See local name in [<cite><a class="noxref informative" href="#references-Namespaces11">XML Namespaces 1.1</a></cite>].</dd>
+
+ <dt id="glossary-dt-namespaceURI">namespace URI</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-Namespaces11">XML Namespaces 1.1</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-dt-phase">phase</dt>
+ <dd>In the context of <a href="#glossary-dt-event">events</a>, a phase is set of logical traversals from node to node along the DOM tree, from the <a href="#glossary-dt-root-element">root element</a> down to the <a href="#glossary-dt-event-target">event target</a> (<a href="glossary-dt-capture-phase">capture phase</a>), at the <a href="#glossary-dt-event-target">event target</a> itself (<a href="glossary-dt-target-phase">target phase</a>), and back up to the <a href="#glossary-dt-root-element">root element</a> (<a href="glossary-dt-bubbling-phase">bubbling phase</a>).</dd>
+
+ <dt id="glossary-dt-propagation-path">propagation path</dt>
+ <dd>The ordered set of <a href="#glossary-dt-event-target">event targets</a> though which an <a href="#glossary-dt-event">event</a> object will pass sequentially on the way to and back from the ultimate <a href="#glossary-dt-event-target">event target</a>. The propagation path is initially comprised of one or more <a href="#glossary-dt-event-phase">event phases</a> as defined by the <a href="#glossary-dt-event-type">event type</a>, but may be interrupted. Also known as an <em>event target chain</em>.</dd>
+
+ <dt id="glossary-dt-target-node">target node</dt>
+ <dd>The target node is the node representing the <a href="#glossary-dt-event-target">event target</a> to which an <a href="#glossary-dt-event">event</a> is targeted using the DOM event flow.</dd>
+
+ <dt id="glossary-dt-root-element">root element</dt>
+ <dd>The first element node of a document, of which all other elements are children; the document element.</dd>
+
+ <dt id="glossary-dt-target-phase">target phase</dt>
+ <dd>The process by which an <a href="#glossary-dt-event">event</a> can be handled by the <a href="#glossary-dt-event-target">event target</a>.</dd>
+
+ <dt id="glossary-dt-topmost-event-target">topmost event target</dt>
+ <dd>The <a href="#glossary-dt-topmost-event-target">topmost event target</a> shall be the element highest in the rendering order which is capable of being an <a href="#glossary-dt-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 'z-index' property. In some cases, such as when using some values of the SVG 'pointer-events' 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 href="#glossary-dt-topmost-event-target">topmost event target</a>. Note that visibility of the element does not necessarily affect its ability to be the <a href="#glossary-dt-topmost-event-target">topmost event target</a>, since an element which is hidden by use of the CSS 'visibility' property can still receive pointer events (though not one with a 'display' property of 'none'), and the <a href="#glossary-dt-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 href="#glossary-dt-topmost-event-target">topmost event target</a> in any event.</dd>
+
+ <dt id="glossary-dt-tree">tree</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-dt-Unicode-character-categories">Unicode character categories</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>
+
+ </dl>
+ </div>
+ <!-- div1 glossary -->
+
<!-- <span class='assert must'></span> -->
<!-- div2 Events-overview -->
+ <h2 id="events-Events-flow" class="div2">3. DOM Event Architecture</h2>
<div class="div2">
- <h2 id="events-Events-flow" class="div2">1.2 Event dispatch and DOM event flow</h2>
+ <h3 id="events-Events-flow" class="div2">3.1 Event dispatch and DOM event flow</h3>
<p>This section defines the event <a href="#glossary-dt-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">
+ <object type="image/svg+xml" data="images/eventflow.svg" width="520" height="560">
<img src="images/eventflow.png" alt="graphical representation of an event dispatched in a DOM tree using the DOM event flow" title="graphical representation of an event dispatched in a DOM tree using the DOM event flow"/>
</object>
<p style="text-align:left"><em>Figure: graphical representation of an event dispatched in a DOM tree using the DOM event flow</em></p>
</div>
- <p>Event objects are always dispatched to a node called the <em>event target</em>. <span class='assert must'>At the beginning of the dispatch, implementations must first determine the event object's <em>propagation path</em>. The propagation path shall be an ordered list of event targets through which the object must pass.</span> The last item in the list shall be the event target; the preceding items in the list are referred to as the <em>target's ancestors</em>, and the immediately preceding item as the <em>target's parent</em>. <span class='assert mustnot'>Once determined, the propagation path cannot be changed.</span> As an example, in the DOM event flow event listeners might change the position of the target node in the document while the event object is being dispatched; such changes do not affect the propagation path. <span class="issue">What if an element is removed from the document altogether? Is there different behavior if the event target is removed versus one of its ancestors?</span></p>
-
- <p>As the next step the event object <em>accomplishes</em> one or more <em>event phases</em>. This specification defines the following event phases. Event objects accomplish them in the specified order using the partial propagation paths as defined below. <span class='assert must'>A phase shall be skipped if it is not supported, or if the event object's propagation has been stopped.</span> For example, if the <a href="#events-Events-Event-canBubble"><code>Event.bubbles</code></a> attribute is set to false, the bubble phase shall be skipped, and if <a href="#events-Events-Event-stopPropagation"><code>Event.stopPropagation()</code></a> has been called prior to the dispatch, all phases must be skipped.</p>
+ <p>Event objects are always dispatched to a node called the <em>event target</em>. <span class='assert must'>At the beginning of the dispatch, implementations must first determine the event object's <a href="#glossary-dt-propagation-path">propagation path</a>. The propagation path shall be an ordered list of event targets through which the object must pass.</span> <span class='assert must'>The last item in the list shall be the event target</span>; the preceding items in the list are referred to as the <em>target's ancestors</em>, and the immediately preceding item as the <em>target's parent</em>. <span class='assert mustnot'>Once determined, the propagation path must not be changed, even if an element in the propagation path is moved within the DOM or removed from the DOM.</span> As an example, in the DOM event flow event listeners might change the position of the target node in the document while the event object is being dispatched; such changes do not affect the propagation path.</p>
+
+ <p id="event phase">As the next step, the event object must complete one or more <a href="#glossary-dt-phase">event phases</a>. This specification defines three event phases: <a href="#capture-phase">capture phase</a>; <a href="#target-phase">target phase</a>; and <a href="#bubble-phase">bubble phase</a>. Event objects complete these phases in the specified order using the partial propagation paths as defined below. <span class='assert must'>A phase shall be skipped if it is not supported, or if the event object's propagation has been stopped.</span> For example, if the <a href="#events-Events-Event-canBubble"><code>Event.bubbles</code></a> attribute is set to false, the bubble phase shall be skipped, and if <a href="#events-Events-Event-stopPropagation"><code>Event.stopPropagation()</code></a> has been called prior to the dispatch, all phases must be skipped.</p>
<ol>
- <li>The <strong id="capture-phase">capture phase</strong>: the event object propagates through the target's ancestors to the target's parent. This phase is also known as the <em>capturing phase</em>. Event listeners registered for this phase shall handle the event before it reaches its target.</li>
- <li>The <strong id="target-phase">target phase</strong>: the event object has reached the event's target. This phase is also known as the <em>at-target phase</em>. Event listeners registered for this phase shall handle the event once it has reached its target.</li>
- <li>The <strong id="bubble-phase">bubble phase</strong>: the event object propagates through the target's ancestors in reverse order, starting with the target's parent. This phase is also known as the <em>bubbling phase</em>. Event listeners registered for this phase shall handle the event after it has reached its target.</li>
+ <li>The <strong id="capture-phase">capture phase</strong>: <span class='assert must'>the event object must propagate through the target's ancestors from the <a href="#glossary-dt-defaultView">defaultView</a> to the target's parent.</span> This phase is also known as the <em>capturing phase</em>. <span class='assert must'>Event listeners registered for this phase must handle the event before it reaches its target.</span></li>
+
+ <li>The <strong id="target-phase">target phase</strong>: <span class='assert must'>the event object must arrive at the event's target.</span> This phase is also known as the <em>at-target phase</em>. <span class='assert must'>Event listeners registered for this phase must handle the event once it has reached its target.</span> <span class='assert must'>If the <a href="#glossary-dt-event-type">event type</a> indicates that the event must not bubble, the event object must halt after completion of this phase.</span></li>
+
+ <li>The <strong id="bubble-phase">bubble phase</strong>: <span class='assert must'>the event object propagates through the target's ancestors in reverse order, starting with the target's parent and ending with the <a href="#glossary-dt-defaultView">defaultView</a>.</span> This phase is also known as the <em>bubbling phase</em>. <span class='assert must'>Event listeners registered for this phase shall handle the event after it has reached its target.</span></li>
</ol>
<p><span class='assert must'>Implementations let event objects accomplish an event phase by applying the following steps while there are pending event targets in the partial propagation path for this phase and the event object's propagation has not been stopped through <a href="#events-Events-Event-stopPropagation"><code>Event.stopPropagation()</code></a>.</span></p>
@@ -636,311 +458,60 @@
<p><span class='assert must'>An implementation shall trigger a listener by invoking the <a href="#events-Events-EventListener-handleEvent"><code class="method-name">EventListener.handleEvent()</code></a> method or an equivalent binding-specific mechanism.</span></p>
<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 href="#glossary-dt-default-action">default actions</a> prior to the event dispatch.</p>
-
- <p>The model defined above applies regardless of the specific event flow associated with an event target. Each event flow defines 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 all events accomplish the capture and target phases. Whether an event accomplishes the bubble phase shall be defined individually for each event type. An alternate application of this model can be found in [<cite><a class="noxref informative" href="#references-DOMLS">DOM Level 3 Load and Save</a></cite>].</p>
- <p>The DOM event model shall 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>
+
+ <p>In the production of the <a href="#glossary-dt-propagation-path">propagation path</a>, if the <a href="#glossary-dt-defaultView">defaultView</a> implements the <a href="#events-Events-EventTarget">EventTarget</a> interface, the event propagates from <a href="#glossary-dt-defaultView">defaultView</a> to the <code>document</code> object during the <a href="#glossary-dt-capture-phase">capture phase</a>, and from the <code>document</code> object to the <a href="#glossary-dt-defaultView">defaultView</a> during the <a href="#glossary-dt-bubble-phase">bubble phase</a>. Note that for legacy reasons, the <a href="#events-event-load">load</a> event does not bubble to the <a href="#glossary-dt-defaultView">defaultView</a> in HTML implementations.</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 href="#glossary-dt-defaultView">defaultView</a>; all events accomplish the capture and target phases; whether an event accomplishes the bubble phase shall be defined individually for each event type. An alternate application of this model can be found in [<cite><a class="noxref informative" href="#references-DOMLS">DOM Level 3 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">
- <h2 id="events-Events-flow-cancelation" class="div2">1.3 Default actions and cancelable events</h2>
- <p>Event objects may have <a href="#glossary-dt-default-action">default actions</a> associated with them. These are actions the implementation must perform in combination with the dispatch of the event object, usually after the dispatch has been completed, but in exceptional cases also immediately before the event is dispatched. An example is the [<cite><a class="noxref informative" href="#references-HTML40">HTML 4.01</a></cite>] form element. When the user submits the form (e.g. by pressing on a submit button), the event <a href="#events-event-submit">submit</a> shall be dispatched to the element and the <a href="#glossary-dt-default-action">default action</a> for this event type shall be generally to send a request to a Web server with the parameters from the form.</p>
+ <h3 id="events-Events-flow-cancelation" class="div2">3.2 Default actions and cancelable events</h3>
+ <p>Event objects may have <a href="#glossary-dt-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-HTML40">HTML 4.01</a></cite>] form element. When the user submits the form (e.g. by pressing on a submit button), the event <a href="#events-event-submit">submit</a> shall be dispatched to the element and the <a href="#glossary-dt-default-action">default action</a> for this event type shall be generally to send a request to a Web server with the parameters from the form.</p>
+
+ <p><a href="#glossary-dt-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">@@ insert example here: <input type="checkbox">'s .checked handling comes to mind.
+ .checked is changed just before 'click' event is dispatched, and if
+ default action is prevented, .checked is set to its original value.</span>
+
<p id="events-dt-cancelable-event">Some event objects are <em>cancelable</em>, meaning the <a href="#glossary-dt-default-action">default action</a> can be prevented from occuring, or, if the <a href="#glossary-dt-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-Events-Event-canCancel"><code>Event.cancelable</code></a> attribute. Event listeners can cancel <a href="#glossary-dt-default-action">default actions</a> of cancelable event objects by invoking the <a href="#events-Events-Event-preventDefault"><code>Event.preventDefault()</code></a> method, and determine whether an event has been canceled through the <a href="#events-Events-Event-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 DOM application itself.</p>
- <p>This specification does not offer features to programatically query if an event object has any <a href="#glossary-dt-default-action">default action</a> associated to it or associate new ones. It is expected that other specifications define what default actions, if any, are associated with certain event objects. Further, implementations may associate <a href="#glossary-dt-default-action">default actions</a> with events as necessary and appropriate. As an example, an implementation may scroll a document view by a certain amount as <a href="#glossary-dt-default-action">default action</a> of a mouse wheel event.</p>
+ <p>This specification does not offer features to programatically query if an event object has any <a href="#glossary-dt-default-action">default action</a> associated with it, or to associate new <a href="#glossary-dt-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 href="#glossary-dt-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 href="#glossary-dt-default-action">default action</a> of a mouse wheel event, while another implementation may instead zoom the document as its <a href="#glossary-dt-default-action">default action</a> for a mouse wheel event.</p>
</div>
<!-- div2 Events-flow-cancelation -->
<div class="div2">
- <h2 id="events-Events-flow-activation" class="div2">1.4 Activation requests and behavior</h2>
+ <h3 id="events-Events-flow-activation" class="div2">3.3 Activation requests and behavior</h3>
<p>(This section is currently being rewritten.)</p>
- <p>Event targets may have associated <a href="#glossary-dt-activation-behavior">activation behavior</a> that implementations perform in response to an <em>activation request</em>. As an example, the typical activiation behavior associated with hyperlinks is to follow the link. Activation requests are typically initiated by users through an input device.</p>
+ <p>Event targets may have associated <a href="#glossary-dt-activation-behavior">activation behavior</a> that implementations perform in response to an <em>activation request</em>. As an example, the typical activation behavior associated with hyperlinks is to follow the link. Activation requests are typically initiated by users through an input device.</p>
<p>In terms of this specification, the activation behavior of the event target shall be the <a href="#glossary-dt-default-action">default action</a> of the event type <a href="#events-event-DOMActivate">DOMActivate</a>. DOM applications should use this event type whenever they wish to make or react to an activation request.</p>
<p>Implementations must dispatch the <code>DOMActivate</code> event as the <a href="#glossary-dt-default-action">default action</a> of a <a href="#events-event-click">click</a> event. This click event shall be either part of the activation request (e.g., a user requests activiation using a mouse), or synthesized by the implementation to accomodate legacy applications. Context information of such a <code>click</code> event is implementation dependent.</p>
<p>When implementations dispatch a synthesized <code>click</code> event, the expectation shall be that they do so as <a href="#glossary-dt-default-action">default action</a> of another event type. For example, when a user activates a hyperlink using a keyboard, the <code>click</code> event would be dispatched as <a href="#glossary-dt-default-action">default action</a> of the respective keyboard event.</p>
<p>Implementations are required to dispatch the synthesized <code>click</code> event as described above even if they do not dispatch such an event (e.g., when activation is requested by a voice command, since this specification does not address event types for voice input).</p>
<p><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>
</div>
+
+
<!-- div2 Events-flow-activation -->
+
+
+ <!-- div2 Event-interfaces -->
<div class="div2">
- <h2 id="events-Event-types" class="div2">1.5 Event types</h2>
- <p>Each event shall be associated with a type, called <em>event type</em> and available as the <a class="noxref" href="#events-Events-Event-type"><code class="interface-attribute">type</code></a> attribute on the event object. The event type shall be composed of a <a href="#glossary-dt-localname">local name</a> and a <a href="#glossary-dt-namespaceURI">namespace URI</a> as used in [<cite><a class="noxref normative" href="#references-DOMCore">DOM Level 3 Core</a></cite>]. All events defined in this specification are in no namespace.</p>
- <div class="div3">
- <h3 id="events-Events-EventTypes-complete" class="div3">1.5.1 Complete list of event types</h3>
- <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-HTML40">HTML 4.01</a></cite>] application, the specifications of those languages may restrict the semantics and scope (in particular the possible target nodes) 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 event types are in no namespace and this specification refers to them by their local name only. All events must accomplish the capture and target phases, but not all of them must accomplish the bubbling phase (see also <a href="#events-Events-flow">Event dispatch and DOM event flow</a>). Some events are not <a href="#events-dt-cancelable-event">cancelable</a> (see <a href="#events-Events-flow-cancelation">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 border="1" cellpadding="2" cellspacing="0"
- 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.">
- <tr>
- <th>type</th>
- <th>Bubbling phase</th>
- <th>Cancelable</th>
- <th>Target node types</th>
- <th>DOM interface</th>
- </tr>
- <tr>
- <td><a href="#events-event-DOMActivate">DOMActivate</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-DOMFocusIn">DOMFocusIn</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-DOMFocusOut">DOMFocusOut</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-focus">focus</a></td>
- <td>No</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-blur">blur</a></td>
- <td>No</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-textInput">textInput</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-TextEvent"><code>TextEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-click">click</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-click">dblclick</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-mousedown">mousedown</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-mouseup">mouseup</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-mouseover">mouseover</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-mousemove">mousemove</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-mouseout">mouseout</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-keydown">keydown</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-keyup">keyup</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-wheel">wheel</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-WheelEvent"><code>WheelEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-mousewheel">mousewheel</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-MouseWheelEvent"><code>MouseWheelEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-DOMSubtreeModified">DOMSubtreeModified</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Document</code>, <code>DocumentFragment</code>, <code>Element</code>, <code>Attr</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-DOMNodeInserted">DOMNodeInserted</a></td>
- <td>Yes</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>
- </tr>
- <tr>
- <td><a href="#events-event-DOMNodeRemoved">DOMNodeRemoved</a></td>
- <td>Yes</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>
- </tr>
- <tr>
- <td><a href="#events-event-DOMNodeRemovedFromDocument">DOMNodeRemovedFromDocument</a></td>
- <td>No</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>
- </tr>
- <tr>
- <td><a href="#events-event-DOMNodeInsertedIntoDocument">DOMNodeInsertedIntoDocument</a></td>
- <td>No</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>
- </tr>
- <tr>
- <td><a href="#events-event-DOMAttrModified">DOMAttrModified</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-DOMCharacterDataModified">DOMCharacterDataModified</a></td>
- <td>Yes</td>
- <td>No</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>
- </tr>
- <tr>
- <td><a href="#events-event-DOMElementNameChanged">DOMElementNameChanged</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-DOMAttributeNameChanged">DOMAttributeNameChanged</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-load">load</a></td>
- <td>No</td>
- <td>No</td>
- <td><code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-unload">unload</a></td>
- <td>No</td>
- <td>No</td>
- <td><code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-abort">abort</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-error">error</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-select">select</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-change">change</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-submit">submit</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-reset">reset</a></td>
- <td>Yes</td>
- <td>Yes</td>
- <td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-resize">resize</a></td>
- <td>Yes</td>
- <td>No</td>
- <td><code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
- </tr>
- <tr>
- <td><a href="#events-event-scroll">scroll</a></td>
- <td>No</td>
- <td>No</td>
- <td><code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
- </tr>
- </table>
-
- <p>As an example, the event <a href="#events-event-load">load</a> must trigger event listeners attached on <code>Element</code> nodes for that event and on the capture and target phases. This event cannot be cancelled. If an event listener for the <a href="#events-event-load">load</a> event is attached to a node other than <code>Document</code> or <code>Element</code> nodes, or if it is attached to the bubbling phase only, this event listener must not be triggered.</p>
-
- <p>The event objects associated with the event types described above may contain context information. Refer to the description of the DOM interfaces for further information.</p>
+ <h2 id="events-Events-interface" class="div2">4. Basic Event Interfaces</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">
+ <object type="image/svg+xml" data="images/event-inheritance.svg" width="960" height="230">
+ <img src="images/event-inheritance.png" alt="graphical representation of the DOM3 Events interface inheritance"/>
+ </object>
+ <p style="text-align:left"><em>Figure: graphical representation of the DOM3 Events interface inheritance</em></p>
</div>
- <!-- div3 Events-EventTypes-complete -->
- </div>
-
-
- <!-- div2 Event-types -->
- <div class="div2">
- <h2 id="events-Events-interface" class="div2">1.6 Basic interfaces</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>
+
+
+
+ <h3 id="interface-Event" class="div2">4.1 Interface Event</h3>
<dl>
<dt><strong>Interface <em>
<a name="events-Events-Event" id="events-Events-Event">Event</a>
@@ -1008,7 +579,7 @@
<dt>
<a name="events-AT_TARGET" id="events-AT_TARGET"><code class="constant-name">AT_TARGET</code></a>
</dt>
- <dd>The current event is in the <a href="#glossary-dt-capture-phase">target phase</a>, i.e. it is being evaluated at the <a href="#glossary-dt-event-target">event target</a>.</dd>
+ <dd>The current event is in the <a href="#glossary-dt-target-phase">target phase</a>, i.e. it is being evaluated at the <a href="#glossary-dt-event-target">event target</a>.</dd>
<dt>
<a name="events-BUBBLING_PHASE" id="events-BUBBLING_PHASE"><code class="constant-name">BUBBLING_PHASE</code></a>
</dt>
@@ -1190,6 +761,9 @@
</dd>
</dl>
</dd>
+
+
+ <h3 id="interface-CustomEvent" class="div2">4.2 Interface CustomEvent</h3>
<dt><strong>Interface <em>
<a name="events-Events-CustomEvent" id="events-Events-CustomEvent">CustomEvent</a>
</em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
@@ -1274,6 +848,9 @@
</dd>
</dl>
</dd>
+
+
+ <h3 id="interface-EventTarget" class="div2">4.3 Interface EventTarget</h3>
<dt><strong>Interface <em>
<a name="events-Events-EventTarget" id="events-Events-EventTarget">EventTarget</a>
</em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
@@ -1512,6 +1089,9 @@
</dd>
</dl>
</dd>
+
+
+ <h3 id="interface-EventListener" class="div2">4.4 Interface EventListener</h3>
<dt><strong>Interface <em>
<a name="events-Events-EventListener" id="events-Events-EventListener">EventListener</a>
</em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
@@ -1620,10 +1200,14 @@
</dl>
</dd>
</dl>
+
+
<div class="div3">
- <h3 id="events-Events-document" class="div3">1.6.1 Event creation</h3>
+ <h3 id="events-Events-document" class="div3">4.5 Event creation</h3>
<p>In most cases, the events dispatched by the DOM Events implementation are also created by the implementation. It is however 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 application must then initialize the object by calling the appropriate initialization method before invoking <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a>. The <a class="noxref" 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>
+
+ <h3 id="interface-DocumentEvent" class="div2">4.5.1 Interface DocumentEvent</h3>
<dl>
<dt><strong>Interface <em>
<a name="events-Events-DocumentEvent" id="events-Events-DocumentEvent">DocumentEvent</a>
@@ -1659,7 +1243,10 @@
<a name="events-Events-DocumentEvent-canDispatch" id="events-Events-DocumentEvent-canDispatch">canDispatch</a>
</code> introduced in <strong class="since">DOM Level 3</strong></dt>
<dd>
- <div class="method">Tests if the implementation can generate events of a specified type.
+ <div class="method">Tests if the implementation can generate events of a specified type.
+ <br/><span class="issue">@@ what is the use case for this? Perhaps to test if an implementation supports a particular event, such as an event from an uncommon language, or a custom event?</span>
+ <br/><span class="issue">@@ Or what does the "implementation can generate" mean? -Olli</span>
+
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
@@ -1767,11 +1354,297 @@
<!-- div3 Events-document -->
</div>
<!-- div2 Events-interface -->
+
+
+
+ <!-- div2 Events-types -->
<div class="div2">
- <h2 id="events-Events-eventgroupings" class="div2">1.7 Event module definitions</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. The DOM will 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>
+ <h2 id="events-Events" class="div2">5. Events</h2>
+ <h3 id="events-Event-types" class="div2">5.1 Event Types</h3>
+ <p>Each event shall be associated with a type, called <em>event type</em> and available as the <a class="noxref" href="#events-Events-Event-type"><code class="interface-attribute">type</code></a> attribute on the event object. The event type shall be composed of a <a href="#glossary-dt-localname">local name</a> and a <a href="#glossary-dt-namespaceURI">namespace URI</a> as used in [<cite><a class="noxref normative" href="#references-DOMCore">DOM Level 3 Core</a></cite>]. All events defined in this specification are in the <code>null</code> namespace.</p>
<div class="div3">
- <h3 id="events-Events-eventgroupings-uievents" class="div3">1.7.1 User Interface event types</h3>
+ <h4 id="events-Events-EventTypes-complete" class="div3">5.1.1 Complete List of Event Types</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-HTML40">HTML 4.01</a></cite>] application, the specifications of those languages may restrict the semantics and scope (in particular the possible target nodes) 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 event types are in no namespace and this specification refers to them by their local name only. All events must accomplish the capture and target phases, but not all of them must accomplish the bubbling phase (see also <a href="#events-Events-flow">Event dispatch and DOM event flow</a>). Some events are not <a href="#events-dt-cancelable-event">cancelable</a> (see <a href="#events-Events-flow-cancelation">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 border="1" cellpadding="2" cellspacing="0"
+ 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.">
+ <tr>
+ <th>type</th>
+ <th>Bubbling phase</th>
+ <th>Cancelable</th>
+ <th>Target node types</th>
+ <th>DOM interface</th>
+ </tr>
+ <tr>
+ <td><a href="#events-event-abort">abort</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-blur">blur</a></td>
+ <td>No</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-change">change</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-click">click</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-click">dblclick</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMActivate">DOMActivate</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMAttributeNameChanged">DOMAttributeNameChanged</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMAttrModified">DOMAttrModified</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMCharacterDataModified">DOMCharacterDataModified</a></td>
+ <td>Yes</td>
+ <td>No</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>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMElementNameChanged">DOMElementNameChanged</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMFocusIn">DOMFocusIn</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMFocusOut">DOMFocusOut</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMNodeInserted">DOMNodeInserted</a></td>
+ <td>Yes</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>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMNodeInsertedIntoDocument">DOMNodeInsertedIntoDocument</a></td>
+ <td>No</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>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMNodeRemoved">DOMNodeRemoved</a></td>
+ <td>Yes</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>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMNodeRemovedFromDocument">DOMNodeRemovedFromDocument</a></td>
+ <td>No</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>
+ </tr>
+ <tr>
+ <td><a href="#events-event-DOMSubtreeModified">DOMSubtreeModified</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Document</code>, <code>DocumentFragment</code>, <code>Element</code>, <code>Attr</code></td>
+ <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-error">error</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-focus">focus</a></td>
+ <td>No</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-keydown">keydown</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-keyup">keyup</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-load">load</a></td>
+ <td>No</td>
+ <td>No</td>
+ <td><code>Document</code>, <code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-mousedown">mousedown</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-mousemove">mousemove</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-mouseout">mouseout</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-mouseover">mouseover</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-mouseup">mouseup</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-mousewheel">mousewheel</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Document</code>, <code>Element</code></td>
+ <td><a href="#events-Events-MouseWheelEvent"><code>MouseWheelEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-reset">reset</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-resize">resize</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Document</code>, <code>Element</code></td>
+ <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-scroll">scroll</a></td>
+ <td>No</td>
+ <td>No</td>
+ <td><code>Document</code>, <code>Element</code></td>
+ <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-select">select</a></td>
+ <td>Yes</td>
+ <td>No</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-submit">submit</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-textInput">textInput</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Element</code></td>
+ <td><a href="#events-Events-TextEvent"><code>TextEvent</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-unload">unload</a></td>
+ <td>No</td>
+ <td>No</td>
+ <td><code>Document</code>, <code>Element</code></td>
+ <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ </tr>
+ <tr>
+ <td><a href="#events-event-wheel">wheel</a></td>
+ <td>Yes</td>
+ <td>Yes</td>
+ <td><code>Document</code>, <code>Element</code></td>
+ <td><a href="#events-Events-WheelEvent"><code>WheelEvent</code></a></td>
+ </tr>
+ </table>
+
+ <p>As an example, the event <a href="#events-event-load">load</a> must trigger event listeners attached on <code>Element</code> nodes for that event and on the capture and target phases. This event cannot be cancelled. If an event listener for the <a href="#events-event-load">load</a> event is attached to a node other than <code>Document</code> or <code>Element</code> nodes, or if it is attached to the bubbling phase only, this event listener must not be triggered.</p>
+
+ <p>The event objects associated with the event types described above may contain context information. Refer to the description of the DOM interfaces for further information.</p>
+ </div>
+ <!-- div3 Events-EventTypes-complete -->
+ </div>
+
+
+ <!-- div2 Events-definitions -->
+ <div class="div2">
+ <h2 id="events-Events-definitions" class="div2">5.2 Event Module Definitions</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 id="events-Events-eventgroupings-uievents" class="div3">5.2.1 User Interface Event Types</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.</p>
<dl>
@@ -2109,9 +1982,1398 @@
</dl>
</div>
</div>
+
+
+ <!-- div3 Events-eventgroupings-basicevents -->
+ <div class="div3">
+ <h3 class="div3" id="events-Events-eventgroupings-basicevents">5.2.2 Basic Event Types</h3>
+ <p>This event module contains basic event types associated with document manipulation. It defines the feature BasicEvents 3.0 and depends on the feature Events 3.0. The basic event types are listed below.</p>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-load">
+ <a class="noxref" href="#events-event-load">load</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 bgcolor="#CFCFCF"><strong><code>load</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</td>
+ </tr>
+ <tr class="assert must">
+ <th>Bubbles</th>
+ <td>No</td>
+ </tr>
+ <tr class="assert must">
+ <th>Target</th>
+ <td><code>Document</code>, <code>Element</code></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>
+ 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.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-unload">
+ <a class="noxref" href="#events-event-unload">unload</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 bgcolor="#CFCFCF"><strong><code>unload</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</td>
+ </tr>
+ <tr class="assert must">
+ <th>Bubbles</th>
+ <td>No</td>
+ </tr>
+ <tr class="assert must">
+ <th>Target</th>
+ <td><code>Document</code>, <code>Element</code></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>
+ 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>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-abort">
+ <a class="noxref" href="#events-event-abort">abort</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 bgcolor="#CFCFCF"><strong><code>abort</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</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>Context info</th>
+ <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
+ </tr>
+ </table>
+ Loading of a resource has been aborted.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-error">
+ <a class="noxref" href="#events-event-error">error</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 bgcolor="#CFCFCF"><strong><code>error</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</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>Context info</th>
+ <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
+ </tr>
+ </table>
+ 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>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-select">
+ <a class="noxref" href="#events-event-select">select</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 bgcolor="#CFCFCF"><strong><code>select</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</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>Context info</th>
+ <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
+ </tr>
+ </table>
+ A user selects some text. DOM Level 3 Events does not provide contextual information to access the selected text. The selection occurred before the dispatch of this event type.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-change">
+ <a class="noxref" href="#events-event-change">change</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 bgcolor="#CFCFCF"><strong><code>change</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</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>Context info</th>
+ <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
+ </tr>
+ </table>
+ A control loses the input focus and its value has been modified since gaining focus. This event type shall be dispatched before the event type <a href="#events-event-blur">blur</a>.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-submit">
+ <a class="noxref" href="#events-event-submit">submit</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 bgcolor="#CFCFCF"><strong><code>submit</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>Context info</th>
+ <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
+ </tr>
+ </table>
+ A form, such as a [<cite><a class="noxref informative" href="#references-HTML40">HTML 4.01</a></cite>] or [<cite><a class="noxref informative" href="#references-XHTML10">XHTML 1.0</a></cite>] form, is submitted.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-reset">
+ <a class="noxref" href="#events-event-reset">reset</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 bgcolor="#CFCFCF"><strong><code>reset</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>Context info</th>
+ <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
+ </tr>
+ </table>
+ A form, such as a [<cite><a class="noxref informative" href="#references-HTML40">HTML 4.01</a></cite>] or [<cite><a class="noxref informative" href="#references-XHTML10">XHTML 1.0</a></cite>] form, is reset.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-resize">
+ <a class="noxref" href="#events-event-resize">resize</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 bgcolor="#CFCFCF"><strong><code>resize</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</td>
+ </tr>
+ <tr class="assert must">
+ <th>Bubbles</th>
+ <td>Yes</td>
+ </tr>
+ <tr class="assert must">
+ <th>Target</th>
+ <td><code>Document</code>, <code>Element</code></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 document view or an element has been resized. The resize occurred before the dispatch of this event type.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-scroll">
+ <a class="noxref" href="#events-event-scroll">scroll</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 bgcolor="#CFCFCF"><strong><code>scroll</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>No</td>
+ </tr>
+ <tr class="assert must">
+ <th>Bubbles</th>
+ <td>No</td>
+ </tr>
+ <tr class="assert must">
+ <th>Target</th>
+ <td><code>Document</code>, <code>Element</code></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 document view or an element has been scrolled. The scroll occurred before the dispatch of this event type.</dd>
+ </dl>
+ </div>
+ </div>
+ <!-- div3 Events-eventgroupings-basicevents -->
+ </div>
+ <!-- div2 Events-eventgroupings -->
+
+
+
+
+ <!-- div3 Events-KeyboardEvents-Interfaces -->
+ <div class="div3">
+ <h3 id="events-Events-eventgroupings-mouseevents" class="div3">5.2.3 Mouse Event Types</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>
+ <dl>
+ <dt><strong>Interface <em>
+ <a name="events-Events-MouseEvent" id="events-Events-MouseEvent">MouseEvent</a>
+ </em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dd>
+ <p>The <code>MouseEvent</code> interface provides specific contextual information associated with Mouse events.</p>
+ <p>In the case of nested elements mouse events are always targeted at the most deeply nested element. Ancestors of the targeted element may use bubbling to obtain notification of mouse events which occur within their descendent elements.</p>
+ <p>To create an instance of the <code>MouseEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("MouseEvent")</code></a> method call.</p>
+ <p><strong>Note:</strong> When initializing <code>MouseEvent</code> objects using <code>initMouseEvent</code> or <code>initMouseEventNS</code>, implementations should use the client coordinates <code>clientX</code> and <code>clientY</code> for calculation of other coordinates (such as target coordinates exposed by <a href="#glossary-dt-DOM-Level-0">DOM Level 0</a> implementations).</p>
+ <dl>
+ <dt>
+ <br/>
+ <strong>IDL Definition</strong>
+ </dt>
+ <dd>
+ <div class="idl-code">
+ <pre>
+ // Introduced in DOM Level 2:
+ interface <a class="noxref" href="#events-Events-MouseEvent">MouseEvent</a> : <a class="noxref" href="#events-Events-UIEvent">UIEvent</a> {
+ readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-screenX">screenX</a>;
+ readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-screenY">screenY</a>;
+ readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-clientX">clientX</a>;
+ readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-clientY">clientY</a>;
+ readonly attribute boolean <a class="noxref" href="#events-Events-KeyboardEvent-inputMode">inputMode</a>;
+ readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-ctrlKey">ctrlKey</a>;
+ readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-shiftKey">shiftKey</a>;
+ readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-altKey">altKey</a>;
+ readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-metaKey">metaKey</a>;
+ readonly attribute unsigned short <a class="noxref" href="#events-Events-MouseEvent-button">button</a>;
+ readonly attribute <a class="noxref" href="#events-Events-EventTarget">EventTarget</a> <a class="noxref" href="#events-Events-MouseEvent-relatedTarget">relatedTarget</a>;
+ void <a class="noxref" href="#events-Events-Event-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 <a class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
+ // Introduced in DOM Level 3:
+ boolean <a class="noxref" href="#events-Events-MouseEvent-getModifierState">getModifierState</a>(in DOMString keyIdentifierArg);
+ // Introduced in DOM Level 3:
+ void <a class="noxref" href="#events-Events-Event-initMouseEventNS">initMouseEventNS</a>(in DOMString namespaceURIArg,
+ 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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
+ in DOMString modifiersListArg);
+ };
+ </pre>
+ </div>
+ <br/>
+ </dd>
+ <dt>
+ <strong>Attributes</strong>
+ </dt>
+ <dd>
+ <dl>
+ <dt><code class="attribute-name">
+ <a name="events-Events-MouseEvent-altKey" 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 name="events-Events-MouseEvent-button" 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 mouse button changed state. <code>0</code> indicates the normal button of the mouse (in general on the left or the one button on Macintosh mice, used to activate a button or select text). <code>2</code> indicates the contextual property (in general on the right, used to display a context menu) button of the mouse if present. <code>1</code> indicates the extra (in general in the middle and often combined with the mouse wheel) button. Some mice may provide or simulate more buttons, and values higher than <code>2</code> can be used to represent such buttons.<br/></dd>
+ <dt><code class="attribute-name">
+ <a name="events-Events-MouseEvent-clientX" 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 name="events-Events-MouseEvent-clientY" 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 name="events-Events-MouseEvent-ctrlKey" 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 name="events-Events-MouseEvent-metaKey" 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 name="events-Events-MouseEvent-relatedTarget" 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 name="events-Events-MouseEvent-screenX" 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 name="events-Events-MouseEvent-screenY" 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 name="events-Events-MouseEvent-shiftKey" 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>
+ <dd>
+ <dl>
+ <dt><code class="method-name">
+ <a name="events-Events-MouseEvent-getModifierState" 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 identifier. See also <a href="#keyset-Modifiers">Modifier keys</a>.
+ <div class="parameters">
+ <strong>Parameters</strong>
+ <div class="paramtable">
+ <dl>
+ <dt><code class="parameter-name">keyIdentifierArg</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 -->
+ <div>
+ <strong>No Exceptions</strong>
+ </div>
+ </div>
+ <!-- method -->
+ </dd>
+ <dt><code class="method-name">
+ <a name="events-Events-Event-initMouseEvent" id="events-Events-Event-initMouseEvent">initMouseEvent</a>
+ </code>
+ </dt>
+ <dd>
+ <div class="method">Initializes attributes of a <code>MouseEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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 -->
+ </dd>
+ <dt><code class="method-name">
+ <a name="events-Events-Event-initMouseEventNS" id="events-Events-Event-initMouseEventNS">initMouseEventNS</a>
+ </code> introduced in <strong class="since">DOM Level 3</strong></dt>
+ <dd>
+ <div class="method">Initializes attributes of a <code>MouseEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a>.
+ <div class="parameters">
+ <strong>Parameters</strong>
+ <div class="paramtable">
+ <dl>
+ <dt><code class="parameter-name">namespaceURIArg</code> of type <code>DOMString</code></dt>
+ <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a> method for a description of this parameter.<br/></dd>
+ <dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt>
+ <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-KeyboardEvent-initKeyboardEventNS"><code>KeyboardEvent.initKeyboardEventNS()</code></a> method for a description of this parameter.<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>
+ <p>The Mouse event types are listed below. In the case of nested elements, mouse event types are always targeted at the most deeply nested element. Ancestors of the targeted element may use bubbling to obtain notification of mouse events which occur within its descendent elements.</p>
+ <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 "double click" might not happen if there is a long delay between the two clicks.</p>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-click">
+ <a class="noxref" href="#events-event-click">click</a>
+ </dt>
+ <dd>
+ <p>
+ <!-- <a href="#glossary-dt-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 bgcolor="#CFCFCF"><strong><code>click</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>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 href="#events-event-mousedown">mousedown</a>, <a href="#events-event-mouseup">mouseup</a>, and <a href="#events-event-click">click</a>. The sequence of these events is: <a href="#events-event-mousedown">mousedown</a>, <a href="#events-event-mouseup">mouseup</a>, and <a href="#events-event-click">click</a>. It depends on the environment configuration whether the event type <a href="#events-event-click">click</a> can occur if one or more of the event types <a href="#events-event-mouseover">mouseover</a>, <a href="#events-event-mousemove">mousemove</a>, and <a href="#events-event-mouseout">mouseout</a> occur between the press and release of the pointing device button. In addition, the event type is dispatched as described in <a href="#events-Events-flow-activation">Activation requests and behavior</a>. -->
+ The <a href="#events-event-click"><code>click</code></a> event must be dispatched on the <a href="#glossary-dt-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 href="#events-event-click"><code>click</code></a> event may be preceded by the <a href="#events-event-mousedown"><code>mousedown</code></a> and <a href="#events-event-mouseup"><code>mouseup</code></a> events on the same element. Depending upon the environment configuration, the <a href="#events-event-click"><code>click</code></a> event may be dispatched if one or more of the event types <a href="#events-event-mouseover"><code>mouseover</code></a>, <a href="#events-event-mousemove"><code>mousemove</code></a>, and <a href="#events-event-mouseout"><code>mouseout</code></a> occur between the press and release of the pointing device button. The <a href="#events-event-click"><code>click</code></a> event may also be followed by the <a href="#events-event-dblclick"><code>dblclick</code></a> event. The <a href="#events-event-click"><code>click</code></a> event type must be dispatched as described in <a href="#events-Events-flow-activation">Activation requests and behavior</a>.
+ </dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-dblclick">
+ <a class="noxref" href="#events-event-dblclick">dblclick</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 bgcolor="#CFCFCF"><strong><code>dblclick</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>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 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 href="#events-event-mousedown">mousedown</a>, <a href="#events-event-mouseup">mouseup</a>, and <a href="#events-event-dblclick">dblclick</a>. This event type must be dispatched after the event type <a href="#events-event-click">click</a> if a click and double click occur simultaneously, and after the event type <a href="#events-event-mouseup">mouseup</a> otherwise.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-mousedown">
+ <a class="noxref" href="#events-event-mousedown">mousedown</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 bgcolor="#CFCFCF"><strong><code>mousedown</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>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 class="noxref" href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> must contain the value <code>1</code>.</td>
+ </tr>
+ </table>
+ A pointing device button must be pressed over an element.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-mouseup">
+ <a class="noxref" href="#events-event-mouseup">mouseup</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 bgcolor="#CFCFCF"><strong><code>mouseup</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>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 pointing device button is released over an element.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-mouseover">
+ <a class="noxref" href="#events-event-mouseover">mouseover</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 bgcolor="#CFCFCF"><strong><code>mouseover</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>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 href="#glossary-dt-event-target">event target</a> a pointing device is exiting, if any.</td>
+ </tr>
+ </table>
+ A pointing device is moved onto an element.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-mousemove">
+ <a class="noxref" href="#events-event-mousemove">mousemove</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 bgcolor="#CFCFCF"><strong><code>mousemove</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>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 pointing device is moved while it is over an element.</dd>
+ </dl>
+ </div>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-mouseout">
+ <a class="noxref" href="#events-event-mouseout">mouseout</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 bgcolor="#CFCFCF"><strong><code>mouseout</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</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>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 href="#glossary-dt-event-target">event target</a> a pointing device is entering, if any.</td>
+ </tr>
+ </table>
+ A pointing device is moved away from an element.</dd>
+ </dl>
+ </div>
+ </div>
+
+ <!-- div3 Events-eventgroupings-wheelevents -->
+ <div class="div3">
+ <h3 id="events-Events-eventgroupings-mousewheelevents" class="div3">5.2.4 Mouse Wheel Event Types</h3>
+ <p>This module defines the feature MouseWheelEvents 3.0 and depends on the feature MouseEvents 3.0.</p>
+ <p>Mouse wheel events are included for specification of legacy support, but are deprecated. Authors are encouraged to use <a href="#events-Events-eventgroupings-wheelevents">Wheel event types</a> instead.</p>
+ <!--
+ <p>Mouse wheel events are a subset of mouse multi wheel events. See <a href='#events-Events-eventgroupings-wheelevents'>Wheel event types</a> for additional information.</p>
+ -->
+ <dl>
+ <dt><strong>Interface <em>
+ <a name="events-Events-MouseWheelEvent" 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 class="noxref" href="#events-Events-MouseWheelEvent">MouseWheelEvent</a> : <a class="noxref" href="#events-Events-MouseEvent">MouseEvent</a> {
+ readonly attribute long <a class="noxref" href="#events-Events-MouseWheelEvent-wheelDelta">wheelDelta</a>;
+ void <a class="noxref" href="#events-Events-Event-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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
+ in DOMString modifiersListArg,
+ in long wheelDeltaArg);
+ void <a class="noxref" href="#events-Events-Event-initMouseWheelEventNS">initMouseWheelEventNS</a>(in DOMString namespaceURIArg,
+ 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 class="noxref" 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 name="events-Events-MouseWheelEvent-wheelDelta" 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 name="events-Events-Event-initMouseWheelEventNS" id="events-Events-Event-initMouseWheelEventNS">initMouseWheelEventNS</a>
+ </code>
+ </dt>
+ <dd>
+ <div class="method">Initializes attributes of a <code>MouseWheelEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</code></a>.
+ <div class="parameters">
+ <strong>Parameters</strong>
+ <div class="paramtable">
+ <dl>
+ <dt><code class="parameter-name">namespaceURIArg</code> of type <code>DOMString</code></dt>
+ <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a> method for a description of this parameter.<br/></dd>
+ <dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt>
+ <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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>
+ <!-- parameters -->
+ <div>
+ <strong>No Return Value</strong>
+ </div>
+ <div>
+ <strong>No Exceptions</strong>
+ </div>
+ </div>
+ <!-- method -->
+ </dd>
+ </dl>
+ </dd>
+ </dl>
+ </dd>
+ </dl>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-mousewheel">
+ <a class="noxref" href="#events-event-mousewheel">mousewheel</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 bgcolor="#CFCFCF"><strong><code>mousewheel</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</td>
+ </tr>
+ <tr class="assert must">
+ <th>Bubbles</th>
+ <td>Yes</td>
+ </tr>
+ <tr class="assert must">
+ <th>Target</th>
+ <td><code>Document</code>, <code>Element</code></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 href="#glossary-dt-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 mouse wheel has been rotated around the y-axis.</dd>
+ </dl>
+ </div>
+ </div>
+ <!-- div3 Events-eventgroupings-mousewheelevents -->
+
+
+
+ <!-- div3 Events-eventgroupings-mouseevents -->
+ <div class="div3">
+ <h3 id="events-Events-eventgroupings-wheelevents" class="div3">5.2.5 Wheel Event Types</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-term" href="events-Events-WheelEvent-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><code class="def-term" id="events-Events-WheelEvent-delta">delta</code>
+ </dt>
+ <dd>
+ <p>The distance the wheel has rotated around the its axis.</p>
+ <p>The value of a <a class="def-term" href="events-Events-WheelEvent-delta">delta</a> shall be a integer indicating a distance, measured as the number of <a class="def-term" href="events-Events-WheelEvent-roll">rolls</a> the wheel has been <a class="def-term" href="events-Events-WheelEvent-rotation">rotated</a>. A positive value shall indicate that the wheel has been <a class="def-term" href="events-Events-WheelEvent-rotation">rotated</a> away from the user on vertically-aligned devices or in a left-hand manner on horizontally aligned devices, and a negative value shall indicate that the wheel has been <a class="def-term" href="events-Events-WheelEvent-rotation">rotated</a> towards the user on vertically-aligned devices or in a right-hand manner on horizontally-aligned devices. The default value of a delta attribute shall be 0.</p>
+ </dd>
+ <dt><code class="def-term" id="events-Events-WheelEvent-roll">roll</code>
+ </dt>
+ <dd>A unit of <a class="def-term" href="events-Events-WheelEvent-rotation">rotation</a> for a device using the <a href="events-Events-eventgroupings-wheelevents">WheelEvent</a> interface. On some devices this may be a finite physical step. On devices with smooth <a class="def-term" href="events-Events-WheelEvent-rotation">rotation</a>, a <a class="def-term" href="events-Events-WheelEvent-roll">roll</a> becomes the smallest reported amount of <a class="def-term" href="events-Events-WheelEvent-rotation">rotation</a>.</dd>
+ <dt><code class="def-term" id="events-Events-WheelEvent-rotation">rotation</code>
+ </dt>
+ <dd>An indication of incremental change. 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>
+ </dl>
+
+ <p class="issue">Should we include some additional attribute that denotes what units the roll is in, such as pixels or lines? See <a href="http://www.w3.org/2008/webapps/track/issues/9"
+ title="ISSUE-9 - Web Applications Working Group Tracker">ISSUE-9</a>.</p>
+
+ <dl>
+ <dt><strong>Interface <em>
+ <a name="events-Events-WheelEvent" id="events-Events-WheelEvent">WheelEvent</a>
+ </em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
+ <dd>
+ <p>The <code>WheelEvent</code> interface provides specific contextual information associated with omnidirectional mouse wheel events.</p>
+ <p>To create an instance of the <code>WheelEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("WheelEvent")</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 class="noxref" href="#events-Events-WheelEvent">WheelEvent</a> : <a class="noxref" href="#events-Events-MouseEvent">MouseEvent</a> {
+ readonly attribute long <a class="noxref" href="#events-Events-WheelEvent-deltaX">deltaX</a>;
+ readonly attribute long <a class="noxref" href="#events-Events-WheelEvent-deltaY">deltaY</a>;
+ readonly attribute long <a class="noxref" href="#events-Events-WheelEvent-deltaZ">deltaZ</a>;
+ void <a class="noxref" href="#events-Events-Event-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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
+ in DOMString modifiersListArg,
+ in long deltaXArg,
+ in long deltaYArg,
+ in long deltaZArg);
+ void <a class="noxref" href="#events-Events-Event-initWheelEventNS">initWheelEventNS</a>(in DOMString namespaceURIArg,
+ 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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
+ in DOMString modifiersListArg,
+ in long deltaXArg,
+ in long deltaYArg,
+ in long deltaZArg);
+ };
+ </pre>
+ </div>
+ <br/>
+ </dd>
+ <dt>
+ <strong>Attributes</strong>
+ </dt>
+ <dd>
+ <dl>
+ <dt><code class="attribute-name">
+ <a name="events-Events-WheelEvent-deltaX" 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 name="events-Events-WheelEvent-deltaY" 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 name="events-Events-WheelEvent-deltaZ" 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>
+ </dl>
+ </dd>
+ <dt>
+ <strong>Methods</strong>
+ </dt>
+ <dd>
+ <dl>
+ <dt><code class="method-name">
+ <a name="events-Events-Event-initWheelEventNS" id="events-Events-Event-initWheelEventNS">initWheelEventNS</a>
+ </code>
+ </dt>
+ <dd>
+ <div class="method">Initializes attributes of a <code>WheelEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</code></a>.
+ <div class="parameters">
+ <strong>Parameters</strong>
+ <div class="paramtable">
+ <dl>
+ <dt><code class="parameter-name">namespaceURIArg</code> of type <code>DOMString</code></dt>
+ <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a> method for a description of this parameter.<br/></dd>
+ <dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt>
+ <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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>
+ </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>
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="events-event-wheel">
+ <a class="noxref" href="#events-event-wheel">wheel</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 bgcolor="#CFCFCF"><strong><code>wheel</code></strong></td>
+ </tr>
+ <tr class="assert must">
+ <th>Namespace</th>
+ <td><code>None</code></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>Cancelable</th>
+ <td>Yes</td>
+ </tr>
+ <tr class="assert must">
+ <th>Bubbles</th>
+ <td>Yes</td>
+ </tr>
+ <tr class="assert must">
+ <th>Target</th>
+ <td><code>Document</code>, <code>Element</code></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 href="#glossary-dt-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 mouse wheel has been rotated. A <a href="#glossary-dt-default-action">default action</a> of user agent generated event objects of this type causes implementations to dispatch a <code>mousewheel</code> event iff it supports that event type and <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</dd>
+ </dl>
+ </div>
+ </div>
+
+
+
<!-- div3 Events-eventgroupings-uievents -->
- <div class="div3" id="events-Events-TextEvents-Interfaces">
- <h3 class="div3">1.7.2 Text events types</h3>
+ <div class="div3">
+ <h3 class="div3" id="events-Events-TextEvents-Interfaces">5.2.6 Text Events Types</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 href="#events-event-textInput">textInput</a> applies only to characters and is designed for use with any text input devices, not just keyboards. Refer to Appendix A, "<a href="#keyset-KeySet">Keyboard events and key identifiers</a>", for examples on how text events are used in combination with keyboard events.</p>
<dl>
@@ -2280,9 +3542,10 @@
</dl>
</div>
</div>
+
<!-- div3 Events-TextEvents-Interfaces -->
<div class="div3">
- <h3 id="events-Events-KeyboardEvents-Interfaces" class="div3">1.7.3 Keyboard event types</h3>
+ <h3 id="events-Events-KeyboardEvents-Interfaces" class="div3">5.2.7 Keyboard Event Types</h3>
<p>(This part of the specification is likely to be moved to a separate specification on keyboard events.)</p>
<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.</p>
@@ -2622,976 +3885,17 @@
</dl>
</div>
</div>
- <!-- div3 Events-KeyboardEvents-Interfaces -->
- <div class="div3">
- <h3 id="events-Events-eventgroupings-mouseevents" class="div3">1.7.4 Mouse event types</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>
- <dl>
- <dt><strong>Interface <em>
- <a name="events-Events-MouseEvent" id="events-Events-MouseEvent">MouseEvent</a>
- </em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
- <dd>
- <p>The <code>MouseEvent</code> interface provides specific contextual information associated with Mouse events.</p>
- <p>In the case of nested elements mouse events are always targeted at the most deeply nested element. Ancestors of the targeted element may use bubbling to obtain notification of mouse events which occur within their descendent elements.</p>
- <p>To create an instance of the <code>MouseEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("MouseEvent")</code></a> method call.</p>
- <p><strong>Note:</strong> When initializing <code>MouseEvent</code> objects using <code>initMouseEvent</code> or <code>initMouseEventNS</code>, implementations should use the client coordinates <code>clientX</code> and <code>clientY</code> for calculation of other coordinates (such as target coordinates exposed by <a href="#glossary-dt-DOM-Level-0">DOM Level 0</a> implementations).</p>
- <dl>
- <dt>
- <br/>
- <strong>IDL Definition</strong>
- </dt>
- <dd>
- <div class="idl-code">
- <pre>
-// Introduced in DOM Level 2:
-interface <a class="noxref" href="#events-Events-MouseEvent">MouseEvent</a> : <a class="noxref" href="#events-Events-UIEvent">UIEvent</a> {
- readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-screenX">screenX</a>;
- readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-screenY">screenY</a>;
- readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-clientX">clientX</a>;
- readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-clientY">clientY</a>;
- readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-ctrlKey">ctrlKey</a>;
- readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-shiftKey">shiftKey</a>;
- readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-altKey">altKey</a>;
- readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-metaKey">metaKey</a>;
- readonly attribute unsigned short <a class="noxref" href="#events-Events-MouseEvent-button">button</a>;
- readonly attribute <a class="noxref" href="#events-Events-EventTarget">EventTarget</a> <a class="noxref" href="#events-Events-MouseEvent-relatedTarget">relatedTarget</a>;
- void <a class="noxref" href="#events-Events-Event-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 <a class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
- // Introduced in DOM Level 3:
- boolean <a class="noxref" href="#events-Events-MouseEvent-getModifierState">getModifierState</a>(in DOMString keyIdentifierArg);
- // Introduced in DOM Level 3:
- void <a class="noxref" href="#events-Events-Event-initMouseEventNS">initMouseEventNS</a>(in DOMString namespaceURIArg,
- 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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
- in DOMString modifiersListArg);
-};
-</pre>
- </div>
- <br/>
- </dd>
- <dt>
- <strong>Attributes</strong>
- </dt>
- <dd>
- <dl>
- <dt><code class="attribute-name">
- <a name="events-Events-MouseEvent-altKey" 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 name="events-Events-MouseEvent-button" 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 mouse button changed state. <code>0</code> indicates the normal button of the mouse (in general on the left or the one button on Macintosh mice, used to activate a button or select text). <code>2</code> indicates the contextual property (in general on the right, used to display a context menu) button of the mouse if present. <code>1</code> indicates the extra (in general in the middle and often combined with the mouse wheel) button. Some mice may provide or simulate more buttons, and values higher than <code>2</code> can be used to represent such buttons.<br/></dd>
- <dt><code class="attribute-name">
- <a name="events-Events-MouseEvent-clientX" 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 name="events-Events-MouseEvent-clientY" 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 name="events-Events-MouseEvent-ctrlKey" 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 name="events-Events-MouseEvent-metaKey" 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 name="events-Events-MouseEvent-relatedTarget" 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 name="events-Events-MouseEvent-screenX" 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 name="events-Events-MouseEvent-screenY" 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 name="events-Events-MouseEvent-shiftKey" 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>
- <dd>
- <dl>
- <dt><code class="method-name">
- <a name="events-Events-MouseEvent-getModifierState" 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 identifier. See also <a href="#keyset-Modifiers">Modifier keys</a>.
-<div class="parameters">
- <strong>Parameters</strong>
- <div class="paramtable">
- <dl>
- <dt><code class="parameter-name">keyIdentifierArg</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 -->
- <div>
- <strong>No Exceptions</strong>
- </div>
- </div>
- <!-- method -->
- </dd>
- <dt><code class="method-name">
- <a name="events-Events-Event-initMouseEvent" id="events-Events-Event-initMouseEvent">initMouseEvent</a>
- </code>
- </dt>
- <dd>
- <div class="method">Initializes attributes of a <code>MouseEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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 -->
- </dd>
- <dt><code class="method-name">
- <a name="events-Events-Event-initMouseEventNS" id="events-Events-Event-initMouseEventNS">initMouseEventNS</a>
- </code> introduced in <strong class="since">DOM Level 3</strong></dt>
- <dd>
- <div class="method">Initializes attributes of a <code>MouseEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a>.
-<div class="parameters">
- <strong>Parameters</strong>
- <div class="paramtable">
- <dl>
- <dt><code class="parameter-name">namespaceURIArg</code> of type <code>DOMString</code></dt>
- <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a> method for a description of this parameter.<br/></dd>
- <dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt>
- <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-Event-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-Events-KeyboardEvent-initKeyboardEventNS"><code>KeyboardEvent.initKeyboardEventNS()</code></a> method for a description of this parameter.<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>
- <p>The Mouse event types are listed below. In the case of nested elements, mouse event types are always targeted at the most deeply nested element. Ancestors of the targeted element may use bubbling to obtain notification of mouse events which occur within its descendent elements.</p>
- <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 "double click" might not happen if there is a long delay between the two clicks.</p>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-click">
- <a class="noxref" href="#events-event-click">click</a>
- </dt>
- <dd>
- <p>
- <!-- <a href="#glossary-dt-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 bgcolor="#CFCFCF"><strong><code>click</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>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 href="#events-event-mousedown">mousedown</a>, <a href="#events-event-mouseup">mouseup</a>, and <a href="#events-event-click">click</a>. The sequence of these events is: <a href="#events-event-mousedown">mousedown</a>, <a href="#events-event-mouseup">mouseup</a>, and <a href="#events-event-click">click</a>. It depends on the environment configuration whether the event type <a href="#events-event-click">click</a> can occur if one or more of the event types <a href="#events-event-mouseover">mouseover</a>, <a href="#events-event-mousemove">mousemove</a>, and <a href="#events-event-mouseout">mouseout</a> occur between the press and release of the pointing device button. In addition, the event type is dispatched as described in <a href="#events-Events-flow-activation">Activation requests and behavior</a>. -->
- The <a href="#events-event-click"><code>click</code></a> event must be dispatched on the <a href="#glossary-dt-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 href="#events-event-click"><code>click</code></a> event may be preceded by the <a href="#events-event-mousedown"><code>mousedown</code></a> and <a href="#events-event-mouseup"><code>mouseup</code></a> events on the same element. Depending upon the environment configuration, the <a href="#events-event-click"><code>click</code></a> event may be dispatched if one or more of the event types <a href="#events-event-mouseover"><code>mouseover</code></a>, <a href="#events-event-mousemove"><code>mousemove</code></a>, and <a href="#events-event-mouseout"><code>mouseout</code></a> occur between the press and release of the pointing device button. The <a href="#events-event-click"><code>click</code></a> event may also be followed by the <a href="#events-event-dblclick"><code>dblclick</code></a> event (<span class="issue">@@ does the dblclick event cancel the click event?</span>). The <a href="#events-event-click"><code>click</code></a> event type must be dispatched as described in <a href="#events-Events-flow-activation">Activation requests and behavior</a>.
- </dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-dblclick">
- <a class="noxref" href="#events-event-dblclick">dblclick</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 bgcolor="#CFCFCF"><strong><code>dblclick</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>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 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 href="#events-event-mousedown">mousedown</a>, <a href="#events-event-mouseup">mouseup</a>, and <a href="#events-event-dblclick">dblclick</a>. This event type must be dispatched after the event type <a href="#events-event-click">click</a> if a click and double click occur simultaneously, and after the event type <a href="#events-event-mouseup">mouseup</a> otherwise.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-mousedown">
- <a class="noxref" href="#events-event-mousedown">mousedown</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 bgcolor="#CFCFCF"><strong><code>mousedown</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>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 class="noxref" href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> must contain the value <code>1</code>.</td>
- </tr>
- </table>
-A pointing device button must be pressed over an element.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-mouseup">
- <a class="noxref" href="#events-event-mouseup">mouseup</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 bgcolor="#CFCFCF"><strong><code>mouseup</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>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 pointing device button is released over an element.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-mouseover">
- <a class="noxref" href="#events-event-mouseover">mouseover</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 bgcolor="#CFCFCF"><strong><code>mouseover</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>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 href="#glossary-dt-event-target">event target</a> a pointing device is exiting, if any.</td>
- </tr>
- </table>
-A pointing device is moved onto an element.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-mousemove">
- <a class="noxref" href="#events-event-mousemove">mousemove</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 bgcolor="#CFCFCF"><strong><code>mousemove</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>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 pointing device is moved while it is over an element.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-mouseout">
- <a class="noxref" href="#events-event-mouseout">mouseout</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 bgcolor="#CFCFCF"><strong><code>mouseout</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>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 href="#glossary-dt-event-target">event target</a> a pointing device is entering, if any.</td>
- </tr>
- </table>
-A pointing device is moved away from an element.</dd>
- </dl>
- </div>
- </div>
-
- <!-- div3 Events-eventgroupings-wheelevents -->
- <div class="div3">
- <h3 id="events-Events-eventgroupings-mousewheelevents" class="div3">1.7.5 Mouse wheel event types</h3>
- <p>This module defines the feature MouseWheelEvents 3.0 and depends on the feature MouseEvents 3.0.</p>
- <p>Mouse wheel events are included for specification of legacy support, but are deprecated. Authors are encouraged to use <a href="#events-Events-eventgroupings-wheelevents">Wheel event types</a> instead.</p>
- <!--
-<p>Mouse wheel events are a subset of mouse multi wheel events. See <a href='#events-Events-eventgroupings-wheelevents'>Wheel event types</a> for additional information.</p>
--->
- <dl>
- <dt><strong>Interface <em>
- <a name="events-Events-MouseWheelEvent" 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 class="noxref" href="#events-Events-MouseWheelEvent">MouseWheelEvent</a> : <a class="noxref" href="#events-Events-MouseEvent">MouseEvent</a> {
- readonly attribute long <a class="noxref" href="#events-Events-MouseWheelEvent-wheelDelta">wheelDelta</a>;
- void <a class="noxref" href="#events-Events-Event-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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
- in DOMString modifiersListArg,
- in long wheelDeltaArg);
- void <a class="noxref" href="#events-Events-Event-initMouseWheelEventNS">initMouseWheelEventNS</a>(in DOMString namespaceURIArg,
- 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 class="noxref" 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 name="events-Events-MouseWheelEvent-wheelDelta" 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.<br/></dd>
- </dl>
- </dd>
- <dt>
- <strong>Methods</strong>
- </dt>
- <dd>
- <dl>
- <dt><code class="method-name">
- <a name="events-Events-Event-initMouseWheelEventNS" id="events-Events-Event-initMouseWheelEventNS">initMouseWheelEventNS</a>
- </code>
- </dt>
- <dd>
- <div class="method">Initializes attributes of a <code>MouseWheelEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</code></a>.
-<div class="parameters">
- <strong>Parameters</strong>
- <div class="paramtable">
- <dl>
- <dt><code class="parameter-name">namespaceURIArg</code> of type <code>DOMString</code></dt>
- <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a> method for a description of this parameter.<br/></dd>
- <dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt>
- <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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>
- <!-- parameters -->
- <div>
- <strong>No Return Value</strong>
- </div>
- <div>
- <strong>No Exceptions</strong>
- </div>
- </div>
- <!-- method -->
- </dd>
- </dl>
- </dd>
- </dl>
- </dd>
- </dl>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-mousewheel">
- <a class="noxref" href="#events-event-mousewheel">mousewheel</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 bgcolor="#CFCFCF"><strong><code>mousewheel</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</td>
- </tr>
- <tr class="assert must">
- <th>Bubbles</th>
- <td>Yes</td>
- </tr>
- <tr class="assert must">
- <th>Target</th>
- <td><code>Document</code>, <code>Element</code></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 href="#glossary-dt-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 mouse wheel has been rotated around the y-axis.</dd>
- </dl>
- </div>
- </div>
- <!-- div3 Events-eventgroupings-mousewheelevents -->
-
-
-
- <!-- div3 Events-eventgroupings-mouseevents -->
- <div class="div3">
- <h3 id="events-Events-eventgroupings-wheelevents" class="div3">1.7.6 Wheel event types</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-term" href="events-Events-WheelEvent-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><code class="def-term" id="events-Events-WheelEvent-delta">delta</code>
- </dt>
- <dd>
- <p>The distance the wheel has rotated around the its axis.</p>
- <p>The value of a <a class="def-term" href="events-Events-WheelEvent-delta">delta</a> shall be a integer indicating a distance, measured as the number of <a class="def-term" href="events-Events-WheelEvent-roll">rolls</a> the wheel has been <a class="def-term" href="events-Events-WheelEvent-rotation">rotated</a>. A positive value shall indicate that the wheel has been <a class="def-term" href="events-Events-WheelEvent-rotation">rotated</a> away from the user on vertically-aligned devices or in a left-hand manner on horizontally aligned devices, and a negative value shall indicate that the wheel has been <a class="def-term" href="events-Events-WheelEvent-rotation">rotated</a> towards the user on vertically-aligned devices or in a right-hand manner on horizontally-aligned devices. The default value of a delta attribute shall be 0.</p>
- </dd>
- <dt><code class="def-term" id="events-Events-WheelEvent-roll">roll</code>
- </dt>
- <dd>A unit of <a class="def-term" href="events-Events-WheelEvent-rotation">rotation</a> for a device using the <a href="events-Events-eventgroupings-wheelevents">WheelEvent</a> interface. On some devices this may be a finite physical step. On devices with smooth <a class="def-term" href="events-Events-WheelEvent-rotation">rotation</a>, a <a class="def-term" href="events-Events-WheelEvent-roll">roll</a> becomes the smallest reported amount of <a class="def-term" href="events-Events-WheelEvent-rotation">rotation</a>.</dd>
- <dt><code class="def-term" id="events-Events-WheelEvent-rotation">rotation</code>
- </dt>
- <dd>An indication of incremental change. 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>
- </dl>
-
- <p class="issue">Should we include some additional attribute that denotes what units the roll is in, such as pixels or lines? See <a href="http://www.w3.org/2008/webapps/track/issues/9"
- title="ISSUE-9 - Web Applications Working Group Tracker">ISSUE-9</a>.</p>
-
- <dl>
- <dt><strong>Interface <em>
- <a name="events-Events-WheelEvent" id="events-Events-WheelEvent">WheelEvent</a>
- </em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
- <dd>
- <p>The <code>WheelEvent</code> interface provides specific contextual information associated with omnidirectional mouse wheel events.</p>
- <p>To create an instance of the <code>WheelEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("WheelEvent")</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 class="noxref" href="#events-Events-WheelEvent">WheelEvent</a> : <a class="noxref" href="#events-Events-MouseEvent">MouseEvent</a> {
- readonly attribute long <a class="noxref" href="#events-Events-WheelEvent-deltaX">deltaX</a>;
- readonly attribute long <a class="noxref" href="#events-Events-WheelEvent-deltaY">deltaY</a>;
- readonly attribute long <a class="noxref" href="#events-Events-WheelEvent-deltaZ">deltaZ</a>;
- void <a class="noxref" href="#events-Events-Event-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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
- in DOMString modifiersListArg,
- in long deltaXArg,
- in long deltaYArg,
- in long deltaZArg);
- void <a class="noxref" href="#events-Events-Event-initWheelEventNS">initWheelEventNS</a>(in DOMString namespaceURIArg,
- 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 class="noxref" href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
- in DOMString modifiersListArg,
- in long deltaXArg,
- in long deltaYArg,
- in long deltaZArg);
-};
-</pre>
- </div>
- <br/>
- </dd>
- <dt>
- <strong>Attributes</strong>
- </dt>
- <dd>
- <dl>
- <dt><code class="attribute-name">
- <a name="events-Events-WheelEvent-deltaX" 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 name="events-Events-WheelEvent-deltaY" 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 name="events-Events-WheelEvent-deltaZ" 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>
- </dl>
- </dd>
- <dt>
- <strong>Methods</strong>
- </dt>
- <dd>
- <dl>
- <dt><code class="method-name">
- <a name="events-Events-Event-initWheelEventNS" id="events-Events-Event-initWheelEventNS">initWheelEventNS</a>
- </code>
- </dt>
- <dd>
- <div class="method">Initializes attributes of a <code>WheelEvent</code> object. This method has the same behavior as <a href="#events-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</code></a>.
-<div class="parameters">
- <strong>Parameters</strong>
- <div class="paramtable">
- <dl>
- <dt><code class="parameter-name">namespaceURIArg</code> of type <code>DOMString</code></dt>
- <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</code></a> method for a description of this parameter.<br/></dd>
- <dt><code class="parameter-name">typeArg</code> of type <code>DOMString</code></dt>
- <dd>Refer to the <a href="#events-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initUIEventNS"><code>UIEvent.initUIEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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-Events-Event-initMouseEventNS"><code>MouseEvent.initMouseEventNS()</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>
- </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>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-wheel">
- <a class="noxref" href="#events-event-wheel">wheel</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 bgcolor="#CFCFCF"><strong><code>wheel</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</td>
- </tr>
- <tr class="assert must">
- <th>Bubbles</th>
- <td>Yes</td>
- </tr>
- <tr class="assert must">
- <th>Target</th>
- <td><code>Document</code>, <code>Element</code></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 href="#glossary-dt-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 mouse wheel has been rotated. A <a href="#glossary-dt-default-action">default action</a> of user agent generated event objects of this type causes implementations to dispatch a <code>mousewheel</code> event iff it supports that event type and <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</dd>
- </dl>
- </div>
- </div>
+
<div class="div3">
- <h3 id="events-Events-eventgroupings-mutationevents" class="div3">1.7.7 Mutation event types</h3>
+ <h3 id="events-Events-eventgroupings-mutationevents" class="div3">5.2.8 Mutation Events</h3>
<p>This module defines the feature MutationEvents 3.0 and depends on the feature Events 3.0.</p>
+ <p><strong>Note:</strong> The <code>MutationEvent</code> interface was introduced in DOM Level 2 Events, but has not yet been completely and interoperably implemented across user agents. In addition, there have been critiques that the interface, as designed, introduces a performance and implementation challenge. A new specification is under development with the aim of addressing the use cases that mutation events solves, but in more performant manner. Thus, this specification describes mutation events for completeness, but deprecates the use of both the <code>MutationEvent</code> interface and the <code>MutationNameEvent</code> interface.</p>
<p>The mutation and mutation name event modules are designed to allow notification of any changes to the structure of a document, including attribute, text, or name modifications. It may be noted that none of the event types associated with the modules are designated as cancelable. This stems from the fact that it is very difficult to make use of existing DOM interfaces which cause document modifications if any change to the document might or might not take place due to cancelation of the resulting event. Although this is still a desired capability, it was decided that it would be better left until the addition of transactions into the DOM.</p>
- <p class="issue">Note that nodes that are not in the document, such as elements freshly created, or elements removed from the DOM, shall not fire mutation events when changes. For example, if an element is created but not yet inserted into the document, then an existing element located in the document shall be moved from its current location to be a child of the new element, there must be one mutation event, for removing the existing element from its previous location, but no event must fire for insertion of the element into the new element, regardless of any assigned mutation event listeners.</p>
- <p class="issue">?What happens to event listeners on an element when it is removed from the tree, or moved elsewhere in the tree?</p>
+ <!-- <p class="issue">Note that nodes that are not in the document, such as elements freshly created, or elements removed from the DOM, shall not fire mutation events when changes. For example, if an element is created but not yet inserted into the document, then an existing element located in the document shall be moved from its current location to be a child of the new element, there must be one mutation event, for removing the existing element from its previous location, but no event must fire for insertion of the element into the new element, regardless of any assigned mutation event listeners.</p>
+ <p class="issue">?What happens to event listeners on an element when it is removed from the tree, or moved elsewhere in the tree?</p> -->
<p>Many single modifications of the tree can cause multiple mutation events to be dispatched. Rather than attempt to specify the ordering of mutation events due to every possible modification of the tree, the ordering of these events is left to the implementation.</p>
<dl>
<dt><strong>Interface <em>
@@ -4078,10 +4382,12 @@
</dl>
</div>
</div>
+
<!-- div3 Events-eventgroupings-mutationevents -->
- <div class="div3" id="events-Events-eventgroupings-mutationnameevents">
- <h3 class="div3">1.7.8 Mutation name event types</h3>
+ <div class="div3">
+ <h3 class="div3" id="events-Events-eventgroupings-mutationnameevents">5.2.9 Mutation Name Event Types</h3>
<p>This module defines the feature MutationNameEvents 3.0 and depends on the features MutationEvents 3.0 and Core 3.0.</p>
+ <p><strong>Note:</strong> The <code>MutationNameEvents</code> interface, introduced in an earlier draft of this specification, derives from the <a href="#events-Events-eventgroupings-mutationevents"><code>MutationEvent</code></a> interface, which is deprecated in this specification. Thus, this specification describes the mutation name event types for completeness, but deprecates their use.</p>
<dl>
<dt><strong>Interface <em>
<a name="events-Events-MutationNameEvent" id="events-Events-MutationNameEvent">MutationNameEvent</a>
@@ -4301,519 +4607,15 @@
</div>
</div>
<!-- div3 Events-eventgroupings-mutationnameevents -->
- <div class="div3" id="events-Events-eventgroupings-basicevents">
- <h3 class="div3">1.7.9 Basic event types</h3>
- <p>This event module contains basic event types associated with document manipulation. It defines the feature BasicEvents 3.0 and depends on the feature Events 3.0. The basic event types are listed below.</p>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-load">
- <a class="noxref" href="#events-event-load">load</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 bgcolor="#CFCFCF"><strong><code>load</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</td>
- </tr>
- <tr class="assert must">
- <th>Bubbles</th>
- <td>No</td>
- </tr>
- <tr class="assert must">
- <th>Target</th>
- <td><code>Document</code>, <code>Element</code></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>
-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.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-unload">
- <a class="noxref" href="#events-event-unload">unload</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 bgcolor="#CFCFCF"><strong><code>unload</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</td>
- </tr>
- <tr class="assert must">
- <th>Bubbles</th>
- <td>No</td>
- </tr>
- <tr class="assert must">
- <th>Target</th>
- <td><code>Document</code>, <code>Element</code></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>
-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>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-abort">
- <a class="noxref" href="#events-event-abort">abort</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 bgcolor="#CFCFCF"><strong><code>abort</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</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>Context info</th>
- <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
- </tr>
- </table>
-Loading of a resource has been aborted.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-error">
- <a class="noxref" href="#events-event-error">error</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 bgcolor="#CFCFCF"><strong><code>error</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</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>Context info</th>
- <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
- </tr>
- </table>
-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>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-select">
- <a class="noxref" href="#events-event-select">select</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 bgcolor="#CFCFCF"><strong><code>select</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</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>Context info</th>
- <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
- </tr>
- </table>
-A user selects some text. DOM Level 3 Events does not provide contextual information to access the selected text. The selection occurred before the dispatch of this event type.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-change">
- <a class="noxref" href="#events-event-change">change</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 bgcolor="#CFCFCF"><strong><code>change</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</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>Context info</th>
- <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
- </tr>
- </table>
-A control loses the input focus and its value has been modified since gaining focus. This event type shall be dispatched before the event type <a href="#events-event-blur">blur</a>.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-submit">
- <a class="noxref" href="#events-event-submit">submit</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 bgcolor="#CFCFCF"><strong><code>submit</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>Context info</th>
- <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
- </tr>
- </table>
-A form, such as a [<cite><a class="noxref informative" href="#references-HTML40">HTML 4.01</a></cite>] or [<cite><a class="noxref informative" href="#references-XHTML10">XHTML 1.0</a></cite>] form, is submitted.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-reset">
- <a class="noxref" href="#events-event-reset">reset</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 bgcolor="#CFCFCF"><strong><code>reset</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>Yes</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>Context info</th>
- <td><a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a> may be in use.</td>
- </tr>
- </table>
-A form, such as a [<cite><a class="noxref informative" href="#references-HTML40">HTML 4.01</a></cite>] or [<cite><a class="noxref informative" href="#references-XHTML10">XHTML 1.0</a></cite>] form, is reset.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-resize">
- <a class="noxref" href="#events-event-resize">resize</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 bgcolor="#CFCFCF"><strong><code>resize</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</td>
- </tr>
- <tr class="assert must">
- <th>Bubbles</th>
- <td>Yes</td>
- </tr>
- <tr class="assert must">
- <th>Target</th>
- <td><code>Document</code>, <code>Element</code></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 document view or an element has been resized. The resize occurred before the dispatch of this event type.</dd>
- </dl>
- </div>
- <div class="event-definition assert must">
- <dl>
- <dt id="events-event-scroll">
- <a class="noxref" href="#events-event-scroll">scroll</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 bgcolor="#CFCFCF"><strong><code>scroll</code></strong></td>
- </tr>
- <tr class="assert must">
- <th>Namespace</th>
- <td><code>None</code></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>Cancelable</th>
- <td>No</td>
- </tr>
- <tr class="assert must">
- <th>Bubbles</th>
- <td>No</td>
- </tr>
- <tr class="assert must">
- <th>Target</th>
- <td><code>Document</code>, <code>Element</code></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 document view or an element has been scrolled. The scroll occurred before the dispatch of this event type.</dd>
- </dl>
- </div>
- </div>
- <!-- div3 Events-eventgroupings-basicevents -->
- </div>
- <!-- div2 Events-eventgroupings -->
+
</div>
<!-- div1 Events -->
- <!-- div1 contributors -->
- <div id="glossary" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
- <div class="div1" id="glossary-glossary">
- <h1 id="glossary-role-glossary" class="glossary">Glossary</h1>
- <dl>
- <dt><em>Editors</em>:</dt>
- <dd>Doug Schepers, W3C</dd>
- <dd>Arnaud Le Hors, W3C</dd>
- <dd>Robert S. Sutor, IBM Research (for DOM Level 1)</dd>
- </dl>
- <p class="first">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-dt-activation-behavior">activation behavior</dt>
- <dd>The action taken when an <a href="#glossary-dt-event">event</a>, typically initiated by users through an input device, causes an element to fulfill a defined role. The role may be defined for that element by the host language, or by author-defined variables, or both. The role 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><a></code> element shall be to cause the user agent 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><input></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.</dd>
-
- <dt id="glossary-dt-bubbling-phase">bubbling phase</dt>
- <dd>The process by which an <a href="#glossary-dt-event">event</a> can be handled by one of the target ancestors after being handled by the <a href="#glossary-dt-target-node">target node</a>.</dd>
-
- <dt id="glossary-dt-capture-phase">capture phase</dt>
- <dd>The process by which an <a href="#glossary-dt-event">event</a> can be handled by one of the target ancestors before being handled by the <a href="#glossary-dt-target-node">target node</a>.</dd>
-
- <dt id="glossary-dt-dead-key">dead key</dt>
- <dd>A dead key is a key or combination of key that produces no character by itself, but which in combination or sequence with another key produces a modified character, such as a character with diacritical marks (e.g. <code>ö</code>, <code>é</code>, <code>â</code>).</dd>
-
- <dt id="glossary-dt-default-action">default action</dt>
- <dd>A <a href="#glossary-dt-default-action">default action</a> is a supplementary behavior that an implementation must perform in combination with the dispatch of the event object. Each event, and each specification, defines the <a href="#glossary-dt-default-action">default action</a> for that event. A <a href="#glossary-dt-default-action">default action</a> may be cancelled through the invocation of the <a href="#events-Events-Event-preventDefault"><code>Event.preventDefault()</code></a> method. For more details, see <a href="#events-Events-flow-cancelation">Default actions and cancelable events</a>.</dd>
-
-
- <dt id="glossary-dt-dispatch">dispatch</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.</dd>
-
- <dt id="glossary-dt-DOM-Level-0">DOM Level 0</dt>
- <dd>The term "DOM Level 0" refers to a mix (not formally specified) of HTML document functionalities offered by Netscape Navigator version 3.0 and Microsoft Internet Explorer version 3.0. In some cases, attributes or methods have been included for reasons of backward compatibility with "DOM Level 0".</dd>
-
- <dt id="glossary-dt-event">event</dt>
- <dd>An event is the representation of some asynchronous occurrence (such as a mouse click on the presentation of the element, or the removal of child node from an element, or any of unthinkably many other possibilities) that gets associated with an <a href="#glossary-dt-event-target">event target</a>.</dd>
-
- <dt id="glossary-dt-event-target">event target</dt>
- <dd>The object to which an <a href="#glossary-dt-event">event</a> is targeted.</dd>
- <dt id="glossary-dt-host-language">host language</dt>
- <dd>Any language which integrates the features of another language, while normatively referencing the origin language rather than redefining those features, and extending those features only in ways defined by the origin language. An origin language 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-dt-ime">IME</dt>
- <dt id="glossary-dt-input-method-editor">input method editor</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 IME may also be used for dictionary-based word completion, such as on mobile devices. See <a href="#keyset-IME">Input Method Editors</a> in Appendix A for treatment of IMEs in this specification.</dd>
-
- <dt id="glossary-dt-localname">local name</dt>
- <dd>See local name in [<cite><a class="noxref informative" href="#references-Namespaces11">XML Namespaces 1.1</a></cite>].</dd>
-
- <dt id="glossary-dt-namespaceURI">namespace URI</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-Namespaces11">XML Namespaces 1.1</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-dt-phase">phase</dt>
- <dd>In the context of <a href="#glossary-dt-event">events</a>, a phase is set of logical traversals from node to node along the DOM tree, from the <a href="#glossary-dt-root-element">root element</a> down to the <a href="#glossary-dt-event-target">event target</a> (<a href="glossary-dt-capture-phase">capture phase</a>), at the <a href="#glossary-dt-event-target">event target</a> itself (<a href="glossary-dt-target-phase">target phase</a>), and back up to the <a href="#glossary-dt-root-element">root element</a> (<a href="glossary-dt-bubbling-phase">bubbling phase</a>).</dd>
-
- <dt id="glossary-dt-target-node">target node</dt>
- <dd>The target node is the node representing the <a href="#glossary-dt-event-target">event target</a> to which an <a href="#glossary-dt-event">event</a> is targeted using the DOM event flow.</dd>
-
- <dt id="glossary-dt-root-element">root element</dt>
- <dd>The first element node of a document, of which all other elements are children; the document element.</dd>
-
- <dt id="glossary-dt-target-phase">target phase</dt>
- <dd>The process by which an <a href="#glossary-dt-event">event</a> can be handled by the <a href="#glossary-dt-event-target">event target</a>.</dd>
-
- <dt id="glossary-dt-topmost-event-target">topmost event target</dt>
- <dd>The <a href="#glossary-dt-topmost-event-target">topmost event target</a> shall be the element highest in the rendering order which is capable of being an <a href="#glossary-dt-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 'z-index' property. In some cases, such as when using some values of the SVG 'pointer-events' 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 href="#glossary-dt-topmost-event-target">topmost event target</a>. Note that visibility of the element does not necessarily affect its ability to be the <a href="#glossary-dt-topmost-event-target">topmost event target</a>, since an element which is hidden by use of the CSS 'visibility' property can still receive pointer events (though not one with a 'display' property of 'none'), and the <a href="#glossary-dt-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 href="#glossary-dt-topmost-event-target">topmost event target</a> in any event.</dd>
-
- <dt id="glossary-dt-tree">tree</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-dt-Unicode-character-categories">Unicode character categories</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>
-
- </dl>
- </div>
- <!-- div1 glossary -->
-
- <div id="keyset" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
<div class="div1">
<h1 id="keyset-KeySet" class="adiv1">Appendix A: Keyboard events and key identifiers</h1>
- <dl>
- <dt><em>Editors</em>:</dt>
- <dd>Doug Schepers, W3C</dd>
- <dd><a href="http://bjoern.hoehrmann.de/">Björn Höhrmann</a> Invited Expert (until December 2007)</dd>
- <dd>Philippe Le Hégaret, W3C (until November 2003)</dd>
- </dl>
- <div class="noprint">
+ <!-- <div class="noprint">
<h2 id="keyset-table-of-contents">Table of Contents</h2>
<ul class="toc">
<li class="tocline3">
@@ -4840,7 +4642,7 @@
<a class="tocxref" href="#keyset-KeySet-Set">A.2 Key identifiers set</a>
</li>
</ul>
- </div>
+ </div> -->
<p>This section contains necessary information regarding keyboard events:</p>
<ul>
<li>Relations between keys, such as dead keys or modifiers keys.</li>
@@ -5018,16 +4820,16 @@
<!-- div3 cancelable_keys -->
<div class="div3">
<h3 id="keyset-Guide" class="adiv3">A.1.5 Guidelines for defining key identifiers</h3>
- <div class="atrisk">
- <p class="issue">This section is the original guideline. We are considering making a more detailed, normative guideline, below.</p>
- <p><strong>Note:</strong> This section is non-normative.</p>
+ <!-- <div class="atrisk">
+ <p class="issue">This section is the original guideline. We are considering making a more detailed, normative guideline, below.</p>
+ <p><strong>Note:</strong> This section is non-normative.</p>
<p>The list of key identifiers contained in this appendix is not exhaustive and input devices may have to define their own key identifiers. Here is a algorithm to determine which key identifier to use:</p>
<ol>
<li>Determine a representation for the key by looking at the keyboard layout mapping in use (and not the keyboard device in use). This representation should be unique, as human friendly as possible, platform independent, and consistent. For example, on PC/AT US keyboards with a US mapping, the 'Q' key shall be mapped to the key identifier "U+0051" (Latin Capital Letter Q key), the '1/!' key shall be mapped to the key identifier "U+0031" (Digit One key), the key '`/~' shall be mapped to the key identifier "U+0060" (Grave Accent key), and the 'Enter' key shall be mapped to the key identifier "Enter".</li>
<li>Find an appropriate mapping in the Unicode character set. There might not always be an appropriate and obvious mapping: the Unicode set contains characters and symbols, the key might generate different characters depending on the operating system, ... In general, unless the representation of the key can be mapped to a unique Unicode character, it is better to create a new one.</li>
<li>If no appropriate mapping was found, create a key identifier as human friendly as possible. The key identifier must not contain white spaces. As an example, the Enter key shall be mapped to the key identifier "Enter" and not to "U+000A" (Line Feed), given that this key generates the character "U+000A" on Unix operating systems and the characters "U+000D" and "U+000A" on Windows operating systems.</li>
</ol>
- </div>
+ </div> -->
<p><strong>Note:</strong> This section is normative.</p>
@@ -5058,7 +4860,7 @@
<li> On a PC/AT US keyboard with a two-handed Dvorak keyboard mapping, the 'Q' key maps to the '5/%' key. The primary function of this key is to generate the character U+0035. Since this character is in general category Nd, the key identifier shall be "5". </li>
<li> On a French PC keyboard with a standard French mapping, the primary function of the '^' key is as a dead key for the circumflex diacritical mark. This corresponds to the combining Unicode character U+0302. Since this character is in general category Mn, the key identifier shall be "U+0302". </li>
<li> On a Korean PC keyboard with a standard Korean mapping, the primary function of the 'Ha/En' key is to switch between Hangul and English input. The predefined key identifier list has an appropriate entry for this key, "HangulMode", so this shall be the key identifier. </li>
- <li> On some models of PDAs, the primary function of the key with a picture of a calendar on it is to launch the calendaring program. Since there is no Unicode character that corresponds to this function, and there is no appropriate entry in the predefined key identifier list, an new identifier may be devised, such as "Calendar".
+ <li> On some models of PDAs, the primary function of the key with a picture of a calendar on it is to launch the calendaring program. Since there is no Unicode character that corresponds to this function, and there is no appropriate entry in the predefined key identifier list, a new identifier may be devised, such as "Calendar".
</li>
</ul>
@@ -5720,7 +5522,7 @@
<p>Browser support for keyboards has traditionally relied on two ad-hoc attributes, <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code>. The values for these attributes, and the availability of the attribute, is inconsistent across platforms, keyboard languages and layouts, User Agents, versions, and even event types. A significant amount of legacy content, including script libraries, relies upon detecting the User Agent and acting accordingly, and any changes to <code class="attr-name">keyCode</code>, or <code class="attr-name">charCode</code> risk breaking as much content as they fix or enable. Additionally, these attributes are not suitable for international usage, or accessibility concerns. Therefore, this specification does not normatively define the <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code> attributes, relying instead only on the more robust key identifiers, which can be used safely and consistently in any User Agent which conforms to this specification. However, for the purpose of documenting the current state of these attributes and their relation to equivalent key identifiers, this specification contains the following table, which is to be used as an informative reference only, and does not document the full range of values for <code class="attr-name">keyCode</code>, and <code class="attr-name">charCode</code>.</p>
<table id="tbl-keyIdentifiers-keyCode-charCode">
- <caption>Key Identifiers Set with keyCode and charCode Equivalents for Major Browsers ('keycode' labelled <em>key</em>, 'charcode' labelled <em>char</em>)</caption>
+ <caption><strong>Key Identifiers Set with keyCode and charCode Equivalents for Major Browsers</strong><br/>(<code>keycode</code> labeled <em>key</em>, <code>charcode</code> labeled <em>char</em>)</caption>
<tr><th rowspan="3">Character String</th><th rowspan="3">Key Name</th><th rowspan="3">Unicode Codepoint</th><th rowspan="3">Description</th><th colspan="6">Internet Explorer 7</th><th colspan="6">Firefox 3</th><th colspan="6">Safari 3.1</th><th colspan="6">Opera 9.5</th></tr>
<tr><th colspan="2">keydown</th><th colspan="2">keypress</th><th colspan="2">keyup</th><th colspan="2">keydown</th><th colspan="2">keypress</th><th colspan="2">keyup</th><th colspan="2">keydown</th><th colspan="2">keypress</th><th colspan="2">keyup</th><th colspan="2">keydown</th><th colspan="2">keypress</th><th colspan="2">keyup</th></tr>
<tr class="smallRow"><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th><th>key</th><th>char</th></tr>
@@ -5960,31 +5762,26 @@
</div>
</div>
<!-- div1 KeySet -->
- <div id="changes" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
+
<div class="div1">
<h1 id="changes-Changes" class="adiv1">Appendix B: Changes</h1>
- <dl>
- <dt><em>Editors</em>:</dt>
- <dd>Doug Schepers, W3C</dd>
- <dd><a href="http://bjoern.hoehrmann.de/">Björn Höhrmann</a> Invited Expert (until December 2007)</dd>
- <dd>Philippe Le Hégaret, W3C (until November 2003)</dd>
- </dl>
<div class="div2">
<h2 id="changes-DOMEvents2to3Changes" class="adiv2">B.1 Changes between DOM Level 2 Events and DOM Level 3 Events</h2>
<p>Numerous clarifications to the interfaces and event types have been made. The <code>HTMLEvents</code> module is no longer defined in this document. The event types <code>focus</code> and <code>blur</code> have been added to the <a href="#events-Events-UIEvent"><code>UIEvents</code></a> module, the event type <code>dblclick</code> has been added to the <a href="#events-Events-MouseEvent"><code>MouseEvents</code></a> module. This new specification provides a better separation between the DOM event flow, the event types, and the DOM interfaces.</p>
+ <p>This specification has been reordered significantly from the earlier W3C Note form, and from the structure of DOM2 Events, in order to clarify the material. New diagrams have been put in place to represent hierarchies and events flows more clearly.</p>
<div class="div3">
<h3 id="changes-DOMEvents2to3Changes-flow" class="adiv3">B.1.1 Changes to DOM Level 2 event flow</h3>
- <p>This new specification introduced one new concept in the event flow:</p>
+ <p>This new specification introduced the following new concepts in the event flow:</p>
<ul>
<li>ordering of event listeners: event listeners are now ordered while ordering was unspecified in DOM Level 2 Events.</li>
+ <li>the event flow now includes the <code>defaultView</code> (or <code>window</code>), to reflect existing implementations.</li>
</ul>
</div>
<!-- div3 DOMEvents2to3Changes-flow -->
- <div class="div3" id="changes-DOMEvents2to3Changes-event-types">
- <h3 class="adiv3">B.1.2 Changes to DOM Level 2 event types</h3>
+ <div class="div3">
+ <h3 class="adiv3" id="changes-DOMEvents2to3Changes-event-types">B.1.2 Changes to DOM Level 2 event types</h3>
<p>Lots of clarifications have been made on the event types. The conformance is now explicitly defined against the event types, and not only in terms of interfaces required by the event types. Support for namespaces and the features <code>"BasicEvents"</code>, <code>"TextEvents"</code>, <code>"KeyboardEvents"</code>, and <code>"MutationNameEvents"</code> have been introduced.</p>
+ <p>In the most recent drafts of this specification, <code>"MutationEvents"</code> and <code>"MutationNameEvents"</code> have been deprecated.</p>
</div>
<!-- div3 DOMEvents2to3Changes-event-types -->
<div class="div3">
@@ -6018,16 +5815,9 @@
<!-- div2 DOMEvents2to3Changes -->
</div>
<!-- div1 Changes -->
- <div id="security-considerations" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
+
<div class="div1">
<h1 id="security-considerations-Security" class="adiv1">Appendix C: Security Considerations</h1>
- <dl>
- <dt><em>Editor</em>:</dt>
- <dd>Doug Schepers, W3C</dd>
- <dd><a href="http://bjoern.hoehrmann.de/">Björn Höhrmann</a> Invited Expert (until December 2007)</dd>
- </dl>
<p class="first">This appendix discusses security considerations for DOM Level 3 Events implementations. The discussion is limited to security issues that arise directly from implementation of the event model, APIs and events defined in this specification. Implementations typically support other features like scripting languages, other APIs and additional events not defined in this document; these features constitute an unknown factor and are out of scope of this document. Implementers should consult the specifications of such features for their respective security considerations.</p>
<p>Many of the event types defined in this specification are dispatched in response to user actions. This allows malicious event listeners to gain access to information users would typically consider confidential, e.g., typos they might have made when filling out a form, if they reconsider their answer to a multiple choice question shortly before submitting a form, their typing rate or primary input mechanism. In the worst case, malicious event listeners are able to capture all user interactions and submit them to a third party through means, while not defined in DOM Level 3 Events, generally available in DOM implementations, such as the XMLHTTPRequest interface.</p>
<p>In DOM implementations that support facilities to load external data, events like the <code>error</code> event can provide access to sensitive information about the environment of the computer system or network; an example would be a malicious HTML document that attempts to embed a resource on the local network or the localhost on different ports; an embedded DOM application could then listen for <code>error</code> and <code>load</code> events to determine which other computers in a network are accessible from the local system or which ports are open on the system to prepare further attacks.</p>
@@ -6035,9 +5825,8 @@
<p>The <a href="#events-Events-DocumentEvent-canDispatch"><code>DocumentEvent.canDispatch()</code></a> method allows DOM applications to retrieve information about which event types the implementation supports, including event types not defined in this specification. Which event types a DOM Level 3 Events implementation supports can depend on configuration settings or on additional software modules available to the implementation.</p>
</div>
<!-- div1 Security -->
- <div id="idl-definitions" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
+
+
<div class="div1">
<h1 id="idl-definitions-idl" class="adiv1">Appendix D: IDL Definitions</h1>
<p class="first">This appendix contains the complete OMG IDL [<cite><a class="noxref normative" href="#references-OMGIDL">OMG IDL</a></cite>] for the Level 3 Document Object Model Events definitions.</p>
@@ -6201,6 +5990,7 @@
readonly attribute DOMString <a class="noxref" href="#events-Events-KeyboardEvent-keyIdentifier">keyIdentifier</a>;
readonly attribute unsigned long <a class="noxref" href="#events-Events-KeyboardEvent-keylocation">keyLocation</a>;
+ <!-- readonly attribute boolean <a class="noxref" href="#events-Events-KeyboardEvent-inputMode">inputMode</a>; -->
readonly attribute boolean <a class="noxref" href="#events-Events-KeyboardEvent-ctrlKey">ctrlKey</a>;
readonly attribute boolean <a class="noxref" href="#events-Events-KeyboardEvent-shiftKey">shiftKey</a>;
readonly attribute boolean <a class="noxref" href="#events-Events-KeyboardEvent-altKey">altKey</a>;
@@ -6229,6 +6019,7 @@
readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-screenY">screenY</a>;
readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-clientX">clientX</a>;
readonly attribute long <a class="noxref" href="#events-Events-MouseEvent-clientY">clientY</a>;
+ <!-- readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-inputMode">inputMode</a>; -->
readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-ctrlKey">ctrlKey</a>;
readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-shiftKey">shiftKey</a>;
readonly attribute boolean <a class="noxref" href="#events-Events-MouseEvent-altKey">altKey</a>;
@@ -6371,9 +6162,6 @@
</div>
</div>
<!-- div1 idl -->
- <div id="java-binding" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
<div class="div1">
<h1 id="java-binding-java-binding" class="adiv1">Appendix E: Java Language Binding</h1>
<p class="first">This appendix contains the complete Java [<cite><a class="noxref normative" href="#references-Java">Java</a></cite>] bindings for the Level 3 Document Object Model Events.</p>
@@ -6824,9 +6612,6 @@
</div>
</div>
<!-- div1 java-binding -->
- <div id="ecma-script-binding" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
<div class="div1">
<h1 id="ecma-script-binding-ecma-binding" class="adiv1">Appendix F: ECMAScript Language Binding</h1>
<p class="first">This appendix contains the complete ECMAScript [<cite><a class="noxref normative" href="#references-ECMAScript">ECMAScript</a></cite>] binding for the Level 3 Document Object Model Events definitions.</p>
@@ -7535,15 +7320,18 @@
<!-- ecma-block -->
</div>
<!-- div1 ecma-binding -->
- <div id="acknowledgements" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
<div class="div1">
<h1 id="acknowledgements-contributors" class="adiv1">Appendix G: Acknowledgements</h1>
<p class="first">Many people contributed to the DOM specifications (Level 1, 2 or 3), including participants of the DOM Working Group and the DOM Interest Group. We especially thank the following:</p>
<p>Andrew Watson (Object Management Group), Andy Heninger (IBM), Angel Diaz (IBM), Arnaud Le Hors (W3C and IBM), Ashok Malhotra (IBM and Microsoft), Ben Chang (Oracle), Bill Smith (Sun), Bill Shea (Merrill Lynch), Bob Sutor (IBM), Chris Lovett (Microsoft), Chris Wilson (Microsoft), David Brownell (Sun), David Ezell (Hewlett-Packard Company), David Singer (IBM), Dimitris Dimitriadis (Improve AB and invited expert), Don Park (invited), Elena Litani (IBM), Eric Vasilik (Microsoft), Gavin Nicol (INSO), Ian Jacobs (W3C), James Clark (invited), James Davidson (Sun), Jared Sorensen (Novell), Jeroen van Rotterdam (X-Hive Corporation), Joe Kesselman (IBM), Joe Lapp (webMethods), Joe Marini (Macromedia), Johnny Stenback (Netscape/AOL), Jon Ferraiolo (Adobe), Jonathan Marsh (Microsoft), Jonathan Robie (Texcel Research and Software AG), Kim Adamson-Sharpe (SoftQuad Software Inc.), Lauren Wood (SoftQuad Software Inc., <em>former Chair</em>), Laurence Cable (Sun), Mark Davis (IBM), Mark Scardina (Oracle), Martin Dürst (W3C), Mary Brady (NIST), Mick Goulish (Software AG), Mike Champion (Arbortext and Software AG), Miles Sabin (Cromwell Media), Patti Lutsky (Arbortext), Paul Grosso (Arbortext), Peter Sharpe (SoftQuad Software Inc.), Phil Karlton (Netscape), Philippe Le Hégaret (W3C, <em>W3C Team Contact and former Chair</em>), Ramesh Lekshmynarayanan (Merrill Lynch), Ray Whitmer (iMall, Excite@Home, and Netscape/AOL, <em>Chair</em>), Rezaur Rahman (Intel), Rich Rollman (Microsoft), Rick Gessner (Netscape), Rick Jelliffe (invited), Rob Relyea (Microsoft), Scott Isaacs (Microsoft), Sharon Adler (INSO), Steve Byrne (JavaSoft), Tim Bray (invited), Tim Yu (Oracle), Tom Pixley (Netscape/AOL), Vidur Apparao (Netscape), Vinod Anupam (Lucent).</p>
<p>After publication of this document as Working Group Note in November 2003, the participants of the WebAPI Working Group resumed development of this document:</p>
- <p>Anne van Kesteren (Opera Software), Arun Ranganathan (AOL), Björn Höhrmann, Charles McCathieNevile (Opera Software, <em>Co-Chair</em>), Christophe Jolif (ILOG), Dean Jackson (W3C, <em>W3C Team Contact</em>), Doug Schepers (Vectoreal), Gorm Haug Eriksen (Opera Software), Ian Davis (Talis Information Limited), Ian Hickson (Google), John Robinson (AOL), Jonas Sicking (Mozilla Foundation), Luca Mascaro (HTML Writers Guild), Maciej Stachowiak (Apple Computer), Marc Hadley (Sun Microsystems), Michael Shenfield (Research In Motion), Robin Berjon, (Expway, <em>Co-Chair</em>) , Scott Hayman (Research In Motion), Stéphane Sire (IntuiLab), T.V. Raman (Google),</p>
+ <p>Anne van Kesteren (Opera Software), Arun Ranganathan (AOL), Björn Höhrmann, Charles McCathieNevile (Opera Software, <em>Co-Chair</em>), Christophe Jolif (ILOG), Dean Jackson (W3C, <em>W3C Team Contact</em>), Doug Schepers (Vectoreal), Gorm Haug Eriksen (Opera Software), Ian Davis (Talis Information Limited), Ian Hickson (Google), John Robinson (AOL), Jonas Sicking (Mozilla Foundation), Luca Mascaro (HTML Writers Guild), Maciej Stachowiak (Apple Computer), Marc Hadley (Sun Microsystems), Michael Shenfield (Research In Motion), Robin Berjon, (Expway, <em>Co-Chair</em>) , Scott Hayman (Research In Motion), Stéphane Sire (IntuiLab), T.V. Raman (Google)</p>
+
+
+ <p>In the WebApps Working Group, the following people were active participants in the process of refining and revising the DOM3 Events Specification:</p>
+ <p>Daniel Danilatos (Google), Travis Leithead (Microsoft), Cameron McCormack (Invited Expert), Carmelo Montanez (NIST), Olli Pettay (Mozilla), Jacob Rossi (Microsoft)</p>
+
+
<p>Thanks to all those who have helped to improve this specification by sending suggestions and corrections (Please, keep bugging us with your issues!).</p>
<p>Many thanks to Brad Pettit, Dylan Schiemann, David Flanagan, Steven Pemberton, Curt Arnold, Al Gilman, Misha Wolf, Sigurd Lerstad, Michael B. Allen, Alexander J. Vincent, Martin Dürst, Ken Rehor, and, Cameron McCormack, for their review and comments of this document.</p>
<p>Special thanks to the <a class="normative" href="http://www.w3.org/DOM/Test">DOM Conformance Test Suites</a> contributors: Fred Drake, Mary Brady (NIST), Rick Rivello (NIST), Robert Clary (Netscape), Neil Delima (IBM), with a special mention to Curt Arnold.</p>
@@ -7558,14 +7346,11 @@
</div>
- <div id="references" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
<div class="div1" id="references-References">
<h1 id="references-role-references" class="references">References</h1>
<p class="first">For the latest version of any W3C specification please consult the list of <a class="normative" href="http://www.w3.org/TR">W3C Technical Reports</a> available at http://www.w3.org/TR.</p>
- <div class="div2" id="references-References-Normative">
- <h2 class="adiv2">I.1 Normative References</h2>
+ <div class="div2">
+ <h2 class="adiv2" id="references-References-Normative">H.1 Normative References</h2>
<dl>
<dt>
<strong>[<a name="references-DOM2Core" id="references-DOM2Core">DOM Level 2 Core</a>]</strong>
@@ -7642,9 +7427,6 @@
<!-- div2 References-Informative -->
</div>
<!-- div1 References -->
- <div id="def-index" class="noprint" style="text-align: right">
- <p style="font-family: monospace;font-size:small">January 2008</p>
- </div>
<div class="div1" id="def-index-Index">
<h1 id="def-index-role-index" class="index">Index</h1>
<table summary="the table contains all keywords used in this document">