--- a/html/DOM3-Events.html Thu Aug 05 03:07:58 2010 +0900
+++ b/html/DOM3-Events.html Wed Aug 18 17:57:15 2010 +0900
@@ -213,13 +213,13 @@
</li>
<li><a href="#events-mutationevents">5.2.8 Mutation Events</a>
<ul class="toc">
- <li><a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code> event</a></li>
- <li><a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code> event</a></li>
- <li><a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code> event</a></li>
- <li><a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code> event</a></li>
- <li><a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code> event</a></li>
<li><a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code> event</a></li>
<li><a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code> event</a></li>
+ <li><a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code> event</a></li>
+ <li><a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code> event</a></li>
+ <li><a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code> event</a></li>
+ <li><a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code> event</a></li>
+ <li><a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code> event</a></li>
</ul>
</li>
<li><a href="#events-mutationnameevents">5.2.9 Mutation Name Event Types</a>
@@ -232,7 +232,7 @@
</li>
</ul>
</li>
- <li><a href="#keyset">6. Keyboard events and key values</a>
+ <li><a href="#keys">6. Keyboard events and key values</a>
<ul class="toc">
<li><a href="#keyboard-input">6.1 Keyboard Input</a>
<ul class="toc">
@@ -245,20 +245,20 @@
</li>
</ul>
</li>
- <li><a href="#keyset-keyvalues">6.2 Key Values</a>
+ <li><a href="#keys-keyvalues">6.2 Key Values</a>
<ul class="toc">
- <li><a href="#keyset-unicode">6.2.1 Key Values and Unicode</a></li>
- <li><a href="#keyset-Modifiers">6.2.2 Modifier keys</a></li>
- <li><a href="#keyset-DeadKeys">6.2.3 Dead keys</a></li>
- <li><a href="#keyset-IME">6.2.4 Input Method Editors</a>
+ <li><a href="#keys-unicode">6.2.1 Key Values and Unicode</a></li>
+ <li><a href="#keys-Modifiers">6.2.2 Modifier keys</a></li>
+ <li><a href="#keys-DeadKeys">6.2.3 Dead keys</a></li>
+ <li><a href="#keys-IME">6.2.4 Input Method Editors</a>
<ul class="toc">
- <li><a href="#keyset-IME_keys">6.2.4.1 Input Method Editor mode keys</a></li>
+ <li><a href="#keys-IME_keys">6.2.4.1 Input Method Editor mode keys</a></li>
</ul>
</li>
- <li><a href="#keyset-cancelable_keys">6.2.5 Default actions and cancelable keyboard events</a></li>
- <li><a href="#keyset-Guide">6.2.6 Guidelines for selecting and defining key values</a></li>
+ <li><a href="#keys-cancelable_keys">6.2.5 Default actions and cancelable keyboard events</a></li>
+ <li><a href="#keys-Guide">6.2.6 Guidelines for selecting and defining key values</a></li>
<li><a href="#key-values">6.2.7 Key Values Set</a></li>
- <li><a href="#keyset-keyCode-charCode">6.2.8 Key values, keyCode, and charCode</a></li>
+ <li><a href="#keys-keyCode-charCode">6.2.8 Key values, keyCode, and charCode</a></li>
</ul>
</li>
</ul>
@@ -330,12 +330,12 @@
[<a href="ref-RFC2119">RFC2119</a>].
However, for readability, these words do not necessarily appear in uppercase in this specification.</p>
<p>This specification is to be understood in the context of the DOM Level 3 Core specification [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>] and the general considerations for DOM implementations apply. For example, behavior in exceptional circumstances (such as when a <code>null</code> argument is passed when <code>null</code> was not expected) is discussed under <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-17189187"><em>DOMException</em></a>, and handling of <a class="def" href="#glossary-namespaceURI">namespace URIs</a> is discussed in <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations"><em>XML Namespaces</em></a>. For additional information about <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance"><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>]. A <a class="def" href="#glossary-user-agent">user agents</a> is not required to conform to the entirety of another specification in order to conform to this specification, but it must conform to the specific parts of any other specification which are called out in this specification (e.g. a conforming DOM3 Events <a class="def" href="#glossary-user-agent">user agent</a> must support the <code>DOMString</code> data type as defined in DOM3 Core, but need not support every method or data type defined in DOM3 Core in order to conform to DOM3 Events).</p>
- <p>This specification defines several classes of conformance for different <a class="def" href="#glossary-user-agent">user agents</a>, specifications, and authors:</p>
+ <p>This specification defines several classes of conformance for different <a class="def" href="#glossary-user-agent">user agents</a>, specifications, and content authors:</p>
<dl>
<dt id="conf-interactive-ua">Web browsers and other dynamic or interactive <a class="def" href="#glossary-user-agent">user agents</a></dt>
<dd>
- <p>A dynamic or interactive <a class="def" href="#glossary-user-agent">user agent</a>, referred to here as a "browser" (be it a Web browser, AT (Accessibility Technology) application, or other similar program), conforms to DOM Level 3 Events if it supports the Core module defined in [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>], the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism, all the interfaces and events with their associated methods, attributes, and semantics defined in this specification which are not marked as <a class="def" href="#glossary-deprecated">deprecated</a>, and the complete set of <a class="def" href="#glossary-character-value">character values</a> and <a class="def" href="#glossary-key-name">key names</a> in the <a href="#key-values">Key Values Set</a> (subject to platform availability), as well as all other normative requirements defined in this specification. A conforming browser must <a class="def" href="#glossary-dispatch">dispatch</a> events appropriate to the given <a href="#events-Events-EventTarget">EventTarget</a> when the conditions defined for that <a class="def" href="#glossary-event-type">event type</a> have been met.</p>
+ <p>A dynamic or interactive <a class="def" href="#glossary-user-agent">user agent</a>, referred to here as a "browser" (be it a Web browser, AT (Accessibility Technology) application, or other similar program), conforms to DOM Level 3 Events if it supports the Core module defined in [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>], the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism, all the interfaces and events with their associated methods, attributes, and semantics defined in this specification which are not marked as <a class="def" href="#glossary-deprecated">deprecated</a>, and the complete set of <a class="def" href="#glossary-character-value">character values</a> and <a class="def" href="#glossary-key-value">key values</a> in the <a href="#key-values">Key Values Set</a> (subject to platform availability), as well as all other normative requirements defined in this specification. A conforming browser must <a class="def" href="#glossary-dispatch">dispatch</a> events appropriate to the given <a href="#events-EventTarget">EventTarget</a> when the conditions defined for that <a class="def" href="#glossary-event-type">event type</a> have been met.</p>
<p><span id="conform-arch">A browser conforms specifically to the DOM Level 3 Events Architecture if it implements the <a href="#dom-event-architecture">DOM Event Architecture</a> and <a href="#event-interfaces">Basic Event Interfaces</a>, regardless of its support for any other event interfaces or <a class="def" href="#glossary-event-type">event types</a> defined in this specification.</span> <span id="conform-module">A browser conforms specifically to the DOM Level 3 Events Module if it implements the interfaces and its related <a class="def" href="#glossary-event-type">event types</a> specified in the <a href="#events-module">Events Module</a>, and to each event interface if it implements that interface and its related <a class="def" href="#glossary-event-type">event types</a>.</span></p>
<p><span id="conform-script">A conforming browser must support scripting, declarative interactivity, or some other means of detecting and dispatching events in the manner described by this specification, and with the attributes specified for that <a class="def" href="#glossary-event-type">event type</a>.</span> <span id="conform-declarative">A declarative browser may still conform to this specification if it does not directly support or expose the methods defined for the DOM Level 3 Events interfaces, but it should provide compatible functionality by other means.</span></p>
<p>In addition to meeting all other conformance criteria, a conforming browser may implement features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a>, for backwards compatibility with existing content, but such implementation is discouraged.</p>
@@ -347,12 +347,12 @@
<dt id="conf-author-tools">Authoring tools</dt>
<dd>
- <p>An authoring tool conforms to DOM Level 3 Events if it produces content which uses the <a class="def" href="#glossary-event-type">event types</a> and <a href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. An authoring tool must not claim conformance to DOM Level 3 Events for content it produces which uses features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!-- or <a class="def" href="#glossary-obsolete">obsolete</a> --> in this specification. A conforming authoring tool should provide to the author a means to use all <a class="def" href="#glossary-event-type">event types</a> and interfaces appropriate to all <a class="def" href="#glossary-host-language">host languages</a> in the content document being produced.</p>
+ <p>A content authoring tool conforms to DOM Level 3 Events if it produces content which uses the <a class="def" href="#glossary-event-type">event types</a> and <a href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. A content authoring tool must not claim conformance to DOM Level 3 Events for content it produces which uses features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!-- or <a class="def" href="#glossary-obsolete">obsolete</a> --> in this specification. A conforming content authoring tool should provide to the content author a means to use all <a class="def" href="#glossary-event-type">event types</a> and interfaces appropriate to all <a class="def" href="#glossary-host-language">host languages</a> in the content document being produced.</p>
</dd>
- <dt id="conf-authors">Authors and content</dt>
+ <dt id="conf-authors">Content authors and content</dt>
<dd>
- <p>An author creates conforming DOM Level 3 Events content if that content uses the <a class="def" href="#glossary-event-type">event types</a> and <a href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. An author should not use features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!-- or <a class="def" href="#glossary-obsolete">obsolete</a> -->, but should rely instead upon replacement mechanisms defined in this specification and elsewhere. Conforming content must use the semantics of the interfaces and <a class="def" href="#glossary-event-type">event types</a> as described in this specification, and must follow best practices as described in accessibility and internationalization guideline specifications. <i class="issue" id="issue-guidelines"><strong>Issue:</strong> define specific guideline specifications.</i></p>
+ <p>A content author creates conforming DOM Level 3 Events content if that content uses the <a class="def" href="#glossary-event-type">event types</a> and <a href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. A content author should not use features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a><!-- or <a class="def" href="#glossary-obsolete">obsolete</a> -->, but should rely instead upon replacement mechanisms defined in this specification and elsewhere. Conforming content must use the semantics of the interfaces and <a class="def" href="#glossary-event-type">event types</a> as described in this specification, and must follow best practices as described in accessibility and internationalization guideline specifications. <i class="issue" id="issue-guidelines"><strong>Issue:</strong> define specific guideline specifications.</i></p>
</dd>
<dt id="conf-specs">Specifications and host languages</dt>
@@ -366,8 +366,8 @@
<h3><a id="feature-detection" href="#feature-detection">1.3 Feature Detection</a></h3>
<p><em>This section is normative</em></p>
- <p>A conforming DOM Level 3 Events <a class="def" href="#glossary-user-agent">user agent</a> must implement the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method to allow authors to detect for support of features defined in this specification. Refer to <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures"><em>DOM Features</em></a> in [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>] for additional information on feature strings.</p>
- <p class="note" id="_0"><strong>Note:</strong> The <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method has been of limited utility to authors in some instances, because of imprecision in conformance criteria in some specifications, and insufficient granularity of feature strings, leading to implementations misrepresenting the degree of support for a class of features. This specification seeks to remedy that in the context of <a class="def" href="#glossary-user-agent">user agents</a> conforming to DOM Level 3 Events by providing discrete feature strings and clear guidelines for the circumstances under which a <a class="def" href="#glossary-user-agent">user agent</a> must or must not report in a positive manner when queried for support of the feature which that feature string represents.</p>
+ <p>A conforming DOM Level 3 Events <a class="def" href="#glossary-user-agent">user agent</a> must implement the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method to allow content authors to detect for support of features defined in this specification. Refer to <a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures"><em>DOM Features</em></a> in [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>] for additional information on feature strings.</p>
+ <p class="note" id="_0"><strong>Note:</strong> The <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method has been of limited utility to content authors in some instances, because of imprecision in conformance criteria in some specifications, and insufficient granularity of feature strings, leading to implementations misrepresenting the degree of support for a class of features. This specification seeks to remedy that in the context of <a class="def" href="#glossary-user-agent">user agents</a> conforming to DOM Level 3 Events by providing discrete feature strings and clear guidelines for the circumstances under which a <a class="def" href="#glossary-user-agent">user agent</a> must or must not report in a positive manner when queried for support of the feature which that feature string represents.</p>
<p>DOM Level 3 Events introduces compositional feature strings, which are base feature strings combined with extended feature strings, a new mechanism for testing support for each specific feature, rather than relying on modules-level feature strings. A <a class="def" href="#glossary-user-agent">user agent</a> conforming to DOM Level 3 Events must also implement the following feature string convention for describing DOM3 Events feature support:</p>
<ul>
<li id="base-feature-string">The primary base feature string for DOM Level 3 Events shall be "<code>Events</code>", with the optional version string "<code>3.0</code>", indicating that the <a class="def" href="#glossary-user-agent">user agent</a> supports the <a href="#conform-arch">DOM Level 3 Events Architecture</a> in the manner described in the appropriate conformance section.
@@ -378,7 +378,7 @@
</li>
<li id="extended-feature-string">The extended feature string for each event type defined in DOM Level 3 Events shall be the base feature string "<code>Events</code>", followed by the period character ("."), followed by the name of that event type, with the optional version string "<code>3.0</code>", indicating that the <a class="def" href="#glossary-user-agent">user agent</a> supports that specific event type in the manner described in the appropriate <a href="#conform-module">conformance section</a>. For example, the feature string for the <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event would be "<code>Events.textInput</code>", with the optional version string "<code>3.0</code>".
<ul>
- <li><span class="assert must">Because this specification does not retroactively define extended feature strings for DOM Level 2 Events, using the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method with extended feature strings with a version string "<code>2.0</code>" must return false.</span><span class="warning" id="_42"><strong>Warning!</strong> Because this mechanism for discrete feature strings was not defined in earlier DOM Events specifications, older user agents which support those specifications but not this one may report false negatives in terms of supporting particular features. For example, a browser which supports the the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type as defined in DOM Level 2 Events, but does not support this specification, is likely to return <code>false</code> to the method call <code>document.implementation.hasFeature("Events.click", "")</code>. The author should not take this for definitive proof that the implementation does not support the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, but rather that other means of testing are required in that instance. This method is best used as a means to detect positive results, not negative ones. However, it is expected that this will prove of sufficient utility in many cases to justify its use.</span></li>
+ <li><span class="assert must">Because this specification does not retroactively define extended feature strings for DOM Level 2 Events, using the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method with extended feature strings with a version string "<code>2.0</code>" must return false.</span><span class="warning" id="_42"><strong>Warning!</strong> Because this mechanism for discrete feature strings was not defined in earlier DOM Events specifications, older user agents which support those specifications but not this one may report false negatives in terms of supporting particular features. For example, a browser which supports the the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type as defined in DOM Level 2 Events, but does not support this specification, is likely to return <code>false</code> to the method call <code>document.implementation.hasFeature("Events.click", "")</code>. The content author should not take this for definitive proof that the implementation does not support the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, but rather that other means of testing are required in that instance. This method is best used as a means to detect positive results, not negative ones. However, it is expected that this will prove of sufficient utility in many cases to justify its use.</span></li>
<li><span class="assert must">A <a class="def" href="#glossary-user-agent">user agent</a> which supports an event type in a manner conforming to DOM Level 2 Events but not conforming to DOM Level 3 Events must not report a positive result to that extended feature string, regardless of the value of the version string.</span></li>
<li><span class="assert must">A specification or <a class="def" href="#glossary-host-language">host language</a> which <a href="#conf-specs">conforms</a> to DOM Level 3 Events, and which extends this specification in a manner consistent with the <a href="#conf-extend">extension conformance criteria</a>, may define extended feature strings for event types defined in that specification. These extended feature strings may be used with the feature string "<code>Events</code>".<!-- These extended feature strings may be used with the <a href="#base-feature-string">base feature string</a> of that specification, or with the feature string "<code>Events</code>"; for example, support for the SVG <code>zoom</code> event type might be tested using the method call <code>document.implementation.hasFeature("Events.zoom", "")</code> or the hypothetical <code>document.implementation.hasFeature("SVG.events.zoom", "")</code>. --></span>
<p class="example" id="example-zoom"><strong>Example:</strong> Support for the SVG <code>zoom</code> event type might be tested using the method call <code>document.implementation.hasFeature("Events.zoom", "")</code></p>
@@ -388,7 +388,7 @@
</li>
</ul>
</li>
- <li>For backwards compatibility, each interface defined in DOM Level 3 Events also has a feature string, which may act as a base feature string or as an extended feature string. If used as a base feature string, it must follow the conventions of the <a href="#base-feature-string">primary base feature string</a> (e.g., "<code>KeyboardEvent</code>", with the optional version string "<code>3.0</code>"); if used as an extended feature string, it must follow the conventions of the <a href="#extended-feature-string">extended feature strings for event types</a> (e.g., "<code>Events.KeyboardEvent</code>", with the optional version string "<code>3.0</code>"). In either case, the <a class="def" href="#glossary-user-agent">user agent</a> must only report a positive result if it supports that specific interface and all associated event types in the manner described in the appropriate <a href="#conform-module">conformance section</a>. <span class="warning" id="_2"><strong>Warning!</strong> because this is not as specific as testing for a specific event type and may thus be less likely to be accurate, authors are encouraged to use the feature strings for event types rather than interfaces.</span></li>
+ <li>For backwards compatibility, each interface defined in DOM Level 3 Events also has a feature string, which may act as a base feature string or as an extended feature string. If used as a base feature string, it must follow the conventions of the <a href="#base-feature-string">primary base feature string</a> (e.g., "<code>KeyboardEvent</code>", with the optional version string "<code>3.0</code>"); if used as an extended feature string, it must follow the conventions of the <a href="#extended-feature-string">extended feature strings for event types</a> (e.g., "<code>Events.KeyboardEvent</code>", with the optional version string "<code>3.0</code>"). In either case, the <a class="def" href="#glossary-user-agent">user agent</a> must only report a positive result if it supports that specific interface and all associated event types in the manner described in the appropriate <a href="#conform-module">conformance section</a>. <span class="warning" id="_2"><strong>Warning!</strong> because this is not as specific as testing for a specific event type and may thus be less likely to be accurate, content authors are encouraged to use the feature strings for event types rather than interfaces.</span></li>
</ul>
<p class="warning" id="_3"><strong>Warning!</strong> This specification does not provide a means to guarantee that any given element of a <a class="def" href="#glossary-host-language">host language</a> is capable of generating or dispatching an event of any given <a class="def" href="#glossary-event-type">event type</a> (e.g., an HTML <code>'img'</code> element may not dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event), or what the attributes of that event will be beyond those defined in this specification (e.g., the host language may add attributes to the event object). A <a class="def" href="#glossary-host-language">host language</a> may provide a different means to do so, including its own relevant feature strings.</p>
</div>
@@ -415,7 +415,7 @@
<p class="issue"><strong>Issue:</strong> This is an open issue.</p>
</div>
<p>Feedback on features at risk, new features, and open issues is especially appreciated.</p>
- <p>In addition, certain terms are used in this specification with particular meanings. The term "implementation" applies to a browser, authoring tool, or other <a class="def" href="#glossary-user-agent">user agent</a> that implements this specification, while an author is a person who writes script or code that takes advantage of the interfaces, methods, attributes, events, and other features described in this specification in order to make Web applications, and a user is the person who uses those Web applications in an implementation.</p>
+ <p>In addition, certain terms are used in this specification with particular meanings. The term "implementation" applies to a browser, content authoring tool, or other <a class="def" href="#glossary-user-agent">user agent</a> that implements this specification, while a content author is a person who writes script or code that takes advantage of the interfaces, methods, attributes, events, and other features described in this specification in order to make Web applications, and a user is the person who uses those Web applications in an implementation.</p>
</div>
<!-- div3 Conformance -->
</div>
@@ -433,7 +433,7 @@
<dd>An event which is defined to initiate an <a class="def" href="#glossary-activation-behavior">activation behavior</a>. Refer to <a href="#event-flow-activation">Activation triggers and behavior</a> for more details.</dd>
<dt id="glossary-author"><dfn>author</dfn></dt>
- <dd>In the context of this specification, an <em>author</em> is a person who writes script or other executable content that uses the interfaces, events, and event flow defined in this specification. See <a href="#conf-authors">Authors and content</a> conformance category for more details.</dd>
+ <dd>In the context of this specification, an <em>author</em>, <em>content author</em>, or <em>script author</em> is a person who writes script or other executable content that uses the interfaces, events, and event flow defined in this specification. See <a href="#conf-authors">Content authors and content</a> conformance category for more details.</dd>
<dt id="glossary-bubbling-phase"><dfn>bubbling phase</dfn></dt>
<dd>The process by which an <a class="def" href="#glossary-event">event</a> can be handled by one of the target ancestors after being handled by the <a class="def" href="#glossary-proximal-event-target">proximal event target</a>. See the description of the <a href="#bubble-phase">bubble phase</a> in the context of event flow for more details.</dd>
@@ -442,7 +442,7 @@
<dd>The process by which an <a class="def" href="#glossary-event">event</a> can be handled by one of the target ancestors before being handled by the <a class="def" href="#glossary-proximal-event-target">proximal event target</a>. See the description of the <a href="#capture-phase">capture phase</a> in the context of event flow for more details.</dd>
<dt id="glossary-character-value"><dfn>character value</dfn></dt>
- <dd>In the context of key values, a character value is a string representing a single Unicode character, such as a letter or symbol.
+ <dd>In the context of key values, a character value is a string representing one or more Unicode characters, such as a letter or symbol, or a set of letters.
<span class="note" id="note_character-value-escapes"><strong>Note:</strong> in source code, some key values, such as non-graphic characters, may be represented using the character escape syntax of the programming language in use.</span>
</dd>
<!-- <dd>In the context of key values, a character value is a string representing a single Unicode character, such as a letter or symbol, as a UTF-16 character escape (e.g. <code class="value">U+0041</code> for the Latin Capital Letter A key, <code class="value charrep">A</code>.). <i class="issue" id="issue-character_value"><strong>Issue:</strong> this may not be the best way to represent a character value, see notes in key values. Also, is "character value" the best term?</i></dd> -->
@@ -457,11 +457,11 @@
<dd>The <code>defaultView</code> is an object which implements 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-delta"><dfn>delta</dfn></dt>
- <dd>The distance an input device using the <a href="#events-wheelevents">WheelEvent</a> interface (such as a mouse wheel) has rotated around its axis. The value of a <a class="def" href="#glossary-delta">delta</a> shall be a integer indicating a distance, measured as the number of <a class="def" href="#glossary-roll">rolls</a> the wheel has been <a class="def" href="#events-Events-WheelEvent-rotation">rotated</a>. A positive value shall indicate that the wheel has been <a class="def" href="#events-Events-WheelEvent-rotation">rotated</a> towards the user on vertically-aligned devices or in a right-hand manner on horizontally-aligned devices, and a negative value shall indicate that the wheel has been <a class="def" 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. The default value of a delta attribute shall be <code>0</code>.
+ <dd>The distance an input device using the <a href="#events-wheelevents">WheelEvent</a> interface (such as a mouse wheel) has rotated around its axis. The value of a <a class="def" href="#glossary-delta">delta</a> shall be a integer indicating a distance, measured as the number of <a class="def" href="#glossary-roll">rolls</a> the wheel has been <a class="def" href="#events-WheelEvent-rotation">rotated</a>. A positive value shall indicate that the wheel has been <a class="def" href="#events-WheelEvent-rotation">rotated</a> towards the user on vertically-aligned devices or in a right-hand manner on horizontally-aligned devices, and a negative value shall indicate that the wheel has been <a class="def" href="#events-WheelEvent-rotation">rotated</a> away from the user on vertically-aligned devices or in a left-hand manner on horizontally aligned devices. The default value of a delta attribute shall be <code>0</code>.
</dd>
<dt id="glossary-deprecated"><dfn>deprecated</dfn></dt>
- <dd>Features marked as deprecated are included in the specification as reference to older implementations or specifications, but are optional and discouraged. Only features which have existing or in-progress replacements shall be deprecated in this specification. Implementations which do not already include support for the feature may implement deprecated features for reasons of backwards compatibility with existing content, but authors creating content should not use deprecated features, unless there is no other way to solve a use case. Other specifications which reference this specification should not use deprecated features, but should point instead to the replacements of which the feature is deprecated in favor. Features marked as deprecated in this specification are expected to be dropped from future specifications.</dd>
+ <dd>Features marked as deprecated are included in the specification as reference to older implementations or specifications, but are optional and discouraged. Only features which have existing or in-progress replacements shall be deprecated in this specification. Implementations which do not already include support for the feature may implement deprecated features for reasons of backwards compatibility with existing content, but content authors creating content should not use deprecated features, unless there is no other way to solve a use case. Other specifications which reference this specification should not use deprecated features, but should point instead to the replacements of which the feature is deprecated in favor. Features marked as deprecated in this specification are expected to be dropped from future specifications.</dd>
<dt id="glossary-dispatch"><dfn>dispatch</dfn></dt>
<dd>To create an event with attributes and methods appropriate to its type and context, and propagate it through the DOM tree in the specified manner. Interchangeable with the term "<a href="#glossary-fire">fire</a>", e.g. "fire a 'click' event" or "dispatch a 'load' event".</dd>
@@ -470,7 +470,7 @@
<dd>An object instantiating the <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#i-Document" title="Document Object Model Core"><code>Document</code> interface</a> [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>], representing the entire HTML or XML text document. Conceptually, it is the root of the document tree, and provides the primary access to the document's data.</dd>
<dt id="glossary-DOM-application"><dfn>DOM application</dfn></dt>
- <dd>A DOM application is script or code, written by an author or automatically generated, which takes advantage of the interfaces, methods, attributes, events, and other features described in this specification in order to make dynamic or interactive content, such as Web applications, exposed to users in a <a class="def" href="#glossary-user-agent">user agent</a>.</dd>
+ <dd>A DOM application is script or code, written by a content author or automatically generated, which takes advantage of the interfaces, methods, attributes, events, and other features described in this specification in order to make dynamic or interactive content, such as Web applications, exposed to users in a <a class="def" href="#glossary-user-agent">user agent</a>.</dd>
<dt id="glossary-DOM-Level-0"><dfn>DOM Level 0</dfn></dt>
<dd>The term "DOM Level 0" refers to a mix of HTML document functionalities, often not formally specified but traditionally supported as de facto standards, implemented originally by Netscape Navigator version 3.0 or Microsoft Internet Explorer version 3.0. In many cases, attributes or methods have been included for reasons of backward compatibility with "DOM Level 0".</dd>
@@ -504,12 +504,10 @@
<dt id="glossary-ime"><dfn>IME</dfn></dt>
<dt id="glossary-input-method-editor"><dfn>input method editor</dfn></dt>
- <dd>An <em>input method editor</em> (IME), also known as a <em>front end processor</em>, is an application that performs the conversion between keystrokes and ideographs or other characters, usually by user-guided dictionary lookup, often used in East Asian languages (e.g. Chinese, Japanese, Korean). An <a class="def" href="#glossary-ime">IME</a> may also be used for dictionary-based word completion, such as on mobile devices. See <a href="#keyset-IME">Input Method Editors</a> for treatment of IMEs in this specification. See also <a class="def" href="#glossary-text-composition-system">text composition system</a>.</dd>
-
- <dt id="glossary-key-name"><dfn>key name</dfn></dt>
- <dd>In the context of key values, a key name is a multi-character string (such as <code class="value">'Enter'</code>, <code class="value">'Tab'</code>, or <code class="value">'MediaNextTrack'</code>) which indicates a key. Control keys, function keys, modifier keys, <a class="def" href="#glossary-dead-key">dead keys</a>, and others may only have a key name, without an equivalent <a class="def" href="#glossary-character-value">character value</a>.
-
- such as <code class="value">'Enter'</code> or <code>tab</code>, for control or <a class="def" href="#glossary-character-value">character value</a>, or certain symbols).</dd>
+ <dd>An <em>input method editor</em> (IME), also known as a <em>front end processor</em>, is an application that performs the conversion between keystrokes and ideographs or other characters, usually by user-guided dictionary lookup, often used in East Asian languages (e.g. Chinese, Japanese, Korean). An <a class="def" href="#glossary-ime">IME</a> may also be used for dictionary-based word completion, such as on mobile devices. See <a href="#keys-IME">Input Method Editors</a> for treatment of IMEs in this specification. See also <a class="def" href="#glossary-text-composition-system">text composition system</a>.</dd>
+
+ <dt id="glossary-key-value"><dfn>key value</dfn></dt>
+ <dd>A key value is <a class="def" href="#glossary-character-value">character value</a> or multi-character string (such as <code class="value">'Enter'</code>, <code class="value">'Tab'</code>, or <code class="value">'MediaNextTrack'</code>) associated with a key in a particular state. Control keys, function keys, modifier keys, <a class="def" href="#glossary-dead-key">dead keys</a>, and others keys always have a key value, whether or not it has a <a class="def" href="#glossary-character-value">character value</a>.</dd>
<dt id="glossary-localname"><dfn>local name</dfn></dt>
<dd>See local name in [<cite><a class="informative" href="#references-Namespaces10">XML Namespaces 1.0</a></cite>].</dd>
@@ -530,12 +528,12 @@
<dd>QWERTY (pronounced "ˈkwɜrti") is a common keyboard layout, so named because the first five character keys on the top row of letter keys are Q, W, E, R, T, and Y. There are many other popular keyboard layouts (including the Dvorak layout), most designed for localization or ergonomics.</dd>
<dt id="glossary-roll"><dfn>roll</dfn></dt>
- <dd>A unit of <a class="def" href="#events-Events-WheelEvent-rotation">rotation</a> for an input device using the <a href="#events-wheelevents">WheelEvent</a> interface. On some devices this may be a finite physical step. On devices with smooth <a class="def" href="#events-Events-WheelEvent-rotation">rotation</a>, a <a class="def" href="#glossary-roll">roll</a> becomes the smallest reported amount of <a class="def" href="#events-Events-WheelEvent-rotation">rotation</a>.</dd>
+ <dd>A unit of <a class="def" href="#events-WheelEvent-rotation">rotation</a> for an input device using the <a href="#events-wheelevents">WheelEvent</a> interface. On some devices this may be a finite physical step. On devices with smooth <a class="def" href="#events-WheelEvent-rotation">rotation</a>, a <a class="def" href="#glossary-roll">roll</a> becomes the smallest reported amount of <a class="def" href="#events-WheelEvent-rotation">rotation</a>.</dd>
<dt id="glossary-root-element"><dfn>root element</dfn></dt>
<dd>The first element node of a document, of which all other elements are children; the document element.</dd>
- <dt id="events-Events-WheelEvent-rotation"><dfn>rotation</dfn></dt>
+ <dt id="events-WheelEvent-rotation"><dfn>rotation</dfn></dt>
<dd>An indication of incremental change on an input device using the <a href="#events-wheelevents">WheelEvent</a> interface. On some devices this may be a literal rotation of a wheel, while on others, it may be movement along a flat surface, or pressure on a particular button.</dd>
<dt id="glossary-text-composition-system"><dfn>text composition system</dfn></dt>
@@ -557,7 +555,7 @@
<dd>A Unicode code point is a unique hexadecimal number signifying a character by its index in the Unicode codespace (or library of characters). In the context of key values, a Unicode code point is expressed as a string in the format "\u" followed by a hexadecimal character index in the range <code>0000</code> to <code>10FFFF</code>, using at least four digits. See also <a class="def charrep" href="#glossary-character-value">character value</a>.</dd>
<dt id="glossary-user-agent"><dfn>user agent</dfn></dt>
- <dd>A program, such as a browser or authoring tool, normally running on a client machine, which acts on a user's behalf in retrieving, interpreting, executing, presenting, or creating content conforming to a specification. Users may act on the content using different user agents at different times, for different purposes. See the <a href="#conf-interactive-ua">Web browsers and other dynamic or interactive user agents</a> and <a href="#conf-author-tools">Authoring tools</a> conformance categories for more details.</dd>
+ <dd>A program, such as a browser or content authoring tool, normally running on a client machine, which acts on a user's behalf in retrieving, interpreting, executing, presenting, or creating content conforming to a specification. Users may act on the content using different user agents at different times, for different purposes. See the <a href="#conf-interactive-ua">Web browsers and other dynamic or interactive user agents</a> and <a href="#conf-author-tools">Authoring tools</a> conformance categories for more details.</dd>
</dl>
</div>
@@ -568,7 +566,7 @@
<div>
<h3><a id="event-flow" href="#event-flow">3.1 Event dispatch and DOM event flow</a></h3>
- <p>This section defines the event <a class="def" href="#glossary-dispatch">dispatch</a> mechanism of the event model defined in this specification. <span class="assert may">Applications may dispatch event objects using the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method</span>, and <span class="assert must">implementations must dispatch event objects as if through this method.</span> The behavior of this method depends on the <em>event flow</em> associated with the underlying object. An event flow describes how event objects <em>propagate</em> through a data structure. As an example, when an event object is dispatched to an element in an XML document, the object propagates through parts of the document, as determined by the DOM event flow which is defined at the end of this section.</p>
+ <p>This section defines the event <a class="def" href="#glossary-dispatch">dispatch</a> mechanism of the event model defined in this specification. <span class="assert may">Applications may dispatch event objects using the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method</span>, and <span class="assert must">implementations must dispatch event objects as if through this method.</span> The behavior of this method depends on the <em>event flow</em> associated with the underlying object. An event flow describes how event objects <em>propagate</em> through a data structure. As an example, when an event object is dispatched to an element in an XML document, the object propagates through parts of the document, as determined by the DOM event flow which is defined at the end of this section.</p>
<div class="figure" style="text-align: center">
<object type="image/svg+xml" data="images/eventflow.svg" width="520" height="560">
<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" />
@@ -609,10 +607,10 @@
</li>
</ul>
<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>
+ <span class="assert must">An implementation shall trigger a listener by invoking the <a href="#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 class="def" href="#glossary-default-action">default actions</a> prior to the event dispatch.</p>
- <p>In the production of the <a class="def" href="#glossary-propagation-path">propagation path</a>, if the <a class="def" href="#glossary-defaultView">defaultView</a> implements the <a href="#events-Events-EventTarget">EventTarget</a> interface, the event propagates from <a class="def" href="#glossary-defaultView">defaultView</a> to the <code>document</code> object during the <a class="def" href="#glossary-capture-phase">capture phase</a>, and from the <code>document</code> object to the <a class="def" href="#glossary-defaultView">defaultView</a> during the <a class="def" href="#glossary-bubbling-phase">bubble phase</a>.
+ <p>In the production of the <a class="def" href="#glossary-propagation-path">propagation path</a>, if the <a class="def" href="#glossary-defaultView">defaultView</a> implements the <a href="#events-EventTarget">EventTarget</a> interface, the event propagates from <a class="def" href="#glossary-defaultView">defaultView</a> to the <code>document</code> object during the <a class="def" href="#glossary-capture-phase">capture phase</a>, and from the <code>document</code> object to the <a class="def" href="#glossary-defaultView">defaultView</a> during the <a class="def" href="#glossary-bubbling-phase">bubble phase</a>.
<span class="note" id="_4"><strong>Note:</strong> for legacy reasons, the <a class="eventtype" href="#event-type-load"><code>load</code></a> event does not propagate to the <a class="def" href="#glossary-defaultView">defaultView</a> in HTML implementations.</span></p>
<p>The model defined above must be applied regardless of the specific event flow associated with an event target. Each event flow must define how the propagation path shall be determined and which event phases are supported. The <em>DOM event flow</em> is an application of this model: the propagation path for a <code>Node</code> object shall be determined by its <code>Node.parentNode</code> chain, and if applicable, the document's containing <a class="def" href="#glossary-defaultView">defaultView</a>; all events accomplish the capture and target phases; whether an event accomplishes the bubble phase shall be defined individually for each <a class="def" href="#glossary-event-type">event type</a>. An alternate application of this model can be found in [<cite><a class="informative" href="#references-DOMLS">DOM3 Load and Save</a></cite>].</p>
<p>Implementations of the DOM event model must be reentrant. Event listeners may perform actions that cause additional events to be dispatched. Such events are handled in a synchronous manner, the event propagation that causes the event listener to be triggered must resume only after the event dispatch of the new event is completed.</p>
@@ -626,7 +624,7 @@
<span class="issue"><strong>Issue:</strong> 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 class="def" href="#glossary-default-action">default action</a> can be prevented from occuring, or, if the <a class="def" href="#glossary-default-action">default action</a> is carried out before the dispatch, its effect may be reversed. Whether an event object is cancelable shall be indicated by the <a href="#events-event-type-canCancel"><code>Event.cancelable</code></a> attribute. Event listeners can cancel <a class="def" href="#glossary-default-action">default actions</a> of cancelable event objects by invoking the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method, and determine whether an event has been canceled through the <a href="#events-event-type-defaultPrevented"><code>Event.defaultPrevented</code></a> attribute while the object is being dispatched, or from the return value of the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method for event objects dispatched by the <a class="def" href="#glossary-DOM-application">DOM application</a> itself.</p>
+ <p id="events-dt-cancelable-event">Some event objects are <em>cancelable</em>, meaning the <a class="def" href="#glossary-default-action">default action</a> can be prevented from occuring, or, if the <a class="def" href="#glossary-default-action">default action</a> is carried out before the dispatch, its effect may be reversed. Whether an event object is cancelable shall be indicated by the <a href="#events-event-type-canCancel"><code>Event.cancelable</code></a> attribute. Event listeners can cancel <a class="def" href="#glossary-default-action">default actions</a> of cancelable event objects by invoking the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method, and determine whether an event has been canceled through the <a href="#events-event-type-defaultPrevented"><code>Event.defaultPrevented</code></a> attribute while the object is being dispatched, or from the return value of the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method for event objects dispatched by the <a class="def" href="#glossary-DOM-application">DOM application</a> itself.</p>
<p>This specification does not offer features to programatically query if an event object has any <a class="def" href="#glossary-default-action">default action</a> associated with it, or to associate new <a class="def" href="#glossary-default-action">default actions</a> to an event object. Other specifications may define what default actions, if any, are associated with certain event objects. Further, implementations may associate <a class="def" href="#glossary-default-action">default actions</a> with events as necessary and appropriate for that implementation. As an example, one implementation may scroll a document view by a certain amount as <a class="def" href="#glossary-default-action">default action</a> of a mouse wheel event, while another implementation may instead zoom the document as its <a class="def" href="#glossary-default-action">default action</a> for a mouse wheel event.</p>
</div>
<!-- div2 sync-async -->
@@ -646,7 +644,7 @@
<div>
<h3><a id="trusted-events" href="#trusted-events">3.4 Trusted events</a></h3>
- <p>Events which are generated by the user agent, either as a result of user interaction, or as a direct result of changes to the DOM, are trusted by the user agent with privileges that are not afforded to events generated by script through the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> method, modified using the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method, or dispatched via the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method. The <a href="#events-event-type-trusted"><code>trusted</code></a> attribute of trusted events has a value of <code>true</code>, while untrusted events have a <a href="#events-event-type-trusted"><code>trusted</code></a> attribute value of <code>false</code>.</p>
+ <p>Events which are generated by the user agent, either as a result of user interaction, or as a direct result of changes to the DOM, are trusted by the user agent with privileges that are not afforded to events generated by script through the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> method, modified using the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method, or dispatched via the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method. The <a href="#events-event-type-trusted"><code>trusted</code></a> attribute of trusted events has a value of <code>true</code>, while untrusted events have a <a href="#events-event-type-trusted"><code>trusted</code></a> attribute value of <code>false</code>.</p>
<p>Most untrusted events should not trigger <a class="def" href="#glossary-default-action">default actions</a>, with the exception of <a class="eventtype" href="#event-type-click"><code>click</code></a> or <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> events which have been synthesized and are managed by the <a class="def" href="#glossary-user-agent">user agents</a> event as the <a class="def" href="#glossary-default-action">default action</a> of an <a class="def" href="#glossary-activation-trigger">activation trigger</a> (see <a href="#event-flow-activation">Activation triggers and behavior</a> for more details); these <a class="def" href="#glossary-user-agent">user-agent</a>-managed synthesized events have a have a <a href="#events-event-type-trusted"><code>trusted</code></a> attribute value of <code>false</code>, but still initiate any <a class="def" href="#glossary-default-action">default actions</a>. All other untrusted events must behave as if the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method had been called on that event.</p>
<p>For security reasons, a <a class="def" href="#glossary-host-language">host language</a> should not define events which are not cancelable (see <a href="#event-flow-default-cancel">Default actions and cancelable events</a>), but also have <a class="def" href="#glossary-default-action">default actions</a>, since these <a class="def" href="#glossary-default-action">default actions</a> may be initiated by untrusted events.</p>
</div>
@@ -656,19 +654,19 @@
<p>Certain <a class="def" href="#glossary-proximal-event-target">proximal event targets</a> (such as a link or button element) may have associated <a class="def" href="#glossary-activation-behavior">activation behavior</a> (such a following a link) that implementations perform in response to an <em><a class="def" href="#glossary-activation-trigger">activation trigger</a></em> (such as clicking a link).</p>
<p>A <a class="def" href="#glossary-host-language">host language</a> should indicate which, if any, elements have activation behavior, describe appropriate <a class="def" href="#glossary-activation-trigger">activation triggers</a>, and define the result of that activation behavior. An implementation which supports a <a class="def" href="#glossary-host-language">host language</a> should initiate these <a class="def" href="#glossary-activation-behavior">activation behavior</a> when the associated <a class="def" href="#glossary-activation-trigger">activation trigger</a> occurs.</p>
- <p class="example" id="example-activation"><strong>Example:</strong> Both HTML and SVG have an <code class="element">a</code> element which indicates a link. Relevant <a class="def" href="#glossary-activation-trigger">activation triggers</a> for an <code class="element">a</code> element are a <a class="eventtype" href="#event-type-click"><code>click</code></a> event on the text or image content of the <code class="element">a</code> element, or a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event with a <a href="#events-Events-KeyboardEvent-key">key</a> attribute value of <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> key when the <code class="element">a</code> element has focus. The activation behavior for an <code class="element">a</code> element is normally to change the content of the window to the content of the new document, in the case of external links, or to reposition the current document relative to the new anchor, in the case of internal links.</p>
+ <p class="example" id="example-activation"><strong>Example:</strong> Both HTML and SVG have an <code class="element">a</code> element which indicates a link. Relevant <a class="def" href="#glossary-activation-trigger">activation triggers</a> for an <code class="element">a</code> element are a <a class="eventtype" href="#event-type-click"><code>click</code></a> event on the text or image content of the <code class="element">a</code> element, or a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event with a <a href="#events-KeyboardEvent-key">key</a> attribute value of <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> key when the <code class="element">a</code> element has focus. The activation behavior for an <code class="element">a</code> element is normally to change the content of the window to the content of the new document, in the case of external links, or to reposition the current document relative to the new anchor, in the case of internal links.</p>
<p>An <a class="def" href="#glossary-activation-trigger">activation trigger</a> is a user action or an event which indicates to the implementation that an activation behavior should be initiated. User-initiated <a class="def" href="#glossary-activation-trigger">activation triggers</a> include clicking a mouse button on an activatable element, pressing the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> key when an activatable element has focus, or pressing a key that is somehow linked to an activatable element (a "hotkey" or "access key") even when that element does not have focus. Event-based <a class="def" href="#glossary-activation-trigger">activation triggers</a> may include timer-based events that activate an element at a certain clock time or after a certain time period has elapsed, progress events after a certain action has been completed, or many other condition-based or state-based events.</p>
- <p>In some cases, a <a class="def" href="#glossary-host-language">host language</a> may define attributes or even attribute values which add to or change the native <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a> of an element. For example, ARIA [<cite><a class="informative" href="#ref-ARIA">ARIA</a></cite>] defines values for the <code class="attr">role</code> attribute that add semantics to the element to which it is applied, for purposes of enhanced accessibility. In such cases, if the <a class="def" href="#glossary-host-language">host language</a> does not explicitly define the <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a>, the author must provide the mechanics of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> (via an event listener) or <a class="def" href="#glossary-activation-behavior">activation behavior</a> (such as calling an ECMAScript function) for that element when applying that attributes or attribute value.</p>
+ <p>In some cases, a <a class="def" href="#glossary-host-language">host language</a> may define attributes or even attribute values which add to or change the native <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a> of an element. For example, ARIA [<cite><a class="informative" href="#ref-ARIA">ARIA</a></cite>] defines values for the <code class="attr">role</code> attribute that add semantics to the element to which it is applied, for purposes of enhanced accessibility. In such cases, if the <a class="def" href="#glossary-host-language">host language</a> does not explicitly define the <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a>, the content author must provide the mechanics of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> (via an event listener) or <a class="def" href="#glossary-activation-behavior">activation behavior</a> (such as calling an ECMAScript function) for that element when applying that attributes or attribute value.</p>
<h4><a id="click-synthesis" href="#click-synthesis">3.5.1 Activation event synthesis</a></h4>
- <p>If the instance of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> is not an event of <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> (that is, when it does not result from a user activating a button or link using a mouse or equivalent pointing device), the implementation must synthesize and dispatch an event of <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> as one of the <a class="def" href="#glossary-default-action">default actions</a> of that <a class="def" href="#glossary-activation-trigger">activation trigger</a>; the value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> must be set to the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> (normally, the currently focused element), and the event must simulate a <em>left click</em> (i.e. the <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> attribute value must be <code>0</code>, and the <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attribute value must be <code>1</code>). Other context information of such a simulated <a class="eventtype" href="#event-type-click"><code>click</code></a> event is implementation dependent, but for historical purposes, the interface for the <a class="eventtype" href="#event-type-click"><code>click</code></a> event must be the <a href="#events-Events-MouseEvent"><code>MouseEvent interface</code></a>, regardless of the actual device used to activate the element. Preventing the <a class="def" href="#glossary-default-action">default action</a> of the <a class="def" href="#glossary-activation-trigger">activation trigger</a>, such as with the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a>, must stop the initiation of the <a class="def" href="#glossary-activation-behavior">activation behavior</a>.</p>
+ <p>If the instance of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> is not an event of <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> (that is, when it does not result from a user activating a button or link using a mouse or equivalent pointing device), the implementation must synthesize and dispatch an event of <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> as one of the <a class="def" href="#glossary-default-action">default actions</a> of that <a class="def" href="#glossary-activation-trigger">activation trigger</a>; the value of the <code class="attribute-name"><a href="#events-event-type-target">Event.target</a></code> must be set to the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> (normally, the currently focused element), and the event must simulate a <em>left click</em> (i.e. the <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> attribute value must be <code>0</code>, and the <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attribute value must be <code>1</code>). Other context information of such a simulated <a class="eventtype" href="#event-type-click"><code>click</code></a> event is implementation dependent, but for historical purposes, the interface for the <a class="eventtype" href="#event-type-click"><code>click</code></a> event must be the <a href="#events-MouseEvent"><code>MouseEvent interface</code></a>, regardless of the actual device used to activate the element. Preventing the <a class="def" href="#glossary-default-action">default action</a> of the <a class="def" href="#glossary-activation-trigger">activation trigger</a>, such as with the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a>, must stop the initiation of the <a class="def" href="#glossary-activation-behavior">activation behavior</a>.</p>
<p class="example" id="example-activation-click"><strong>Example:</strong> When a user activates a hyperlink using a keyboard, such as by focusing the hyperlink element and pressing the <a href="#key-Enter"><code class="value keyname">'Enter'</code></a> or <a href="#key-Space"><code class="value keyname">'Space'</code></a> key, a <a class="eventtype" href="#event-type-click"><code>click</code></a> event would be dispatched as the <a class="def" href="#glossary-default-action">default action</a> of the respective <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event.</p>
<p>Implementations must dispatch the synthesized <a class="eventtype" href="#event-type-click"><code>click</code></a> event as described above even if they do not normally dispatch such an event (e.g. when activation is requested by a voice command, since this specification does not address <a class="def" href="#glossary-event-type">event types</a> for voice input).</p>
<p class="note" id="application-dependent-activation"><strong>Note:</strong> The activation of an event target is device dependent, but is also application dependent, e.g. a link in a document can be activated using a mouse click or a mouse double click.</p>
<p>Implementations which support the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> should also dispatch a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event as a <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-click"><code>click</code></a> event which is associated with an <a class="def" href="#glossary-activation-trigger">activation trigger</a>. However, such implementations should only initiate the associated <a class="def" href="#glossary-activation-behavior">activation behavior</a> once for any given occurrence of an <a class="def" href="#glossary-activation-trigger">activation trigger</a>.</p>
<p class="example" id="example-activation-DOMActivate"><strong>Example:</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> is required to be supported for XForms [<cite><a class="informative" href="#ref-xforms">XFORMS</a></cite>], which is intended for implementation within a <a class="def" href="#glossary-host-language">host language</a>. In a scenario where a plugin or script-based implementation of XForms is intended for installation in a native implementation of this specification which does not support the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a>, the XForms <a class="def" href="#glossary-user-agent">user agent</a> must synthesize and dispatch its own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> events based on the appropriate <a class="def" href="#glossary-activation-trigger">activation triggers</a>. Thus, when a <a class="eventtype" href="#event-type-click"><code>click</code></a> event is dispatched by the DOM Level 3 Events <a class="def" href="#glossary-user-agent">user agent</a>, the XForms <a class="def" href="#glossary-user-agent">user agent</a> must determine whether to synthesize a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event with the same relevant properties as a <a class="def" href="#glossary-default-action">default action</a> of that <a class="eventtype" href="#event-type-click"><code>click</code></a> event; appropriate cues may be whether the <a class="eventtype" href="#event-type-click"><code>click</code></a> event is <a href="#trusted-events">trusted</a>, or whether its <a class="def" href="#glossary-proximal-event-target">proximal event target</a> has a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event listener registered.</p>
- <p class="note" id="authors-activation"><strong>Note:</strong> Authors should not rely upon the interoperable support of <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> in many <a class="def" href="#glossary-user-agent">user agents</a>. Thus, authors may use the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> whenever they wish to make or react to an <a class="def" href="#glossary-activation-trigger">activation trigger</a>, but should use the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> for more accessible behavior instead, due to wider implementation.</p>
+ <p class="note" id="authors-activation"><strong>Note:</strong> Content authors should not rely upon the interoperable support of <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> in many <a class="def" href="#glossary-user-agent">user agents</a>. Thus, content authors may use the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> whenever they wish to make or react to an <a class="def" href="#glossary-activation-trigger">activation trigger</a>, but should use the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> for more accessible behavior instead, due to wider implementation.</p>
<p class="warning" id="activation-deprecated"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> is deprecated in this specification.</p>
@@ -735,10 +733,10 @@
<dl>
- <dt><strong>Interface <em><a id="events-Events-Event">Event</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-Event">Event</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
<dd>
- <p>The <code>Event</code> interface is used to provide contextual information about an event to the listener processing the event. An object which implements the <code>Event</code> interface shall be passed as the parameter to an <a href="#events-Events-EventListener"><code>EventListener</code></a>. The object passed to the event listener may also implement derived interfaces that provide access to information directly relating to the type of event they represent.</p>
- <p>To create an instance of the <code>Event</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> method call.</p>
+ <p>The <code>Event</code> interface is used to provide contextual information about an event to the listener processing the event. An object which implements the <code>Event</code> interface shall be passed as the parameter to an <a href="#events-EventListener"><code>EventListener</code></a>. The object passed to the event listener may also implement derived interfaces that provide access to information directly relating to the type of event they represent.</p>
+ <p>To create an instance of the <code>Event</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -747,7 +745,7 @@
<dd>
<pre class="idl" id="idl-interface-Event"><code>
// Introduced in DOM Level 2:
-interface <a href="#events-Events-Event">Event</a> {
+interface <a href="#events-Event">Event</a> {
// PhaseType
const unsigned short <a href="#events-CAPTURING_PHASE">CAPTURING_PHASE</a> = 1;
@@ -755,8 +753,8 @@
const unsigned short <a href="#events-BUBBLING_PHASE">BUBBLING_PHASE</a> = 3;
readonly attribute DOMString <a href="#events-event-type-type">type</a>;
- readonly attribute <a href="#events-Events-EventTarget">EventTarget</a> <a href="#events-event-type-target">target</a>;
- readonly attribute <a href="#events-Events-EventTarget">EventTarget</a> <a href="#events-event-type-currentTarget">currentTarget</a>;
+ readonly attribute <a href="#events-EventTarget">EventTarget</a> <a href="#events-event-type-target">target</a>;
+ readonly attribute <a href="#events-EventTarget">EventTarget</a> <a href="#events-event-type-currentTarget">currentTarget</a>;
readonly attribute unsigned short <a href="#events-event-type-eventPhase">eventPhase</a>;
readonly attribute boolean <a href="#events-event-type-canBubble">bubbles</a>;
readonly attribute boolean <a href="#events-event-type-canCancel">cancelable</a>;
@@ -806,8 +804,8 @@
<dt><code class="attribute-name"><a id="events-event-type-canCancel">cancelable</a></code> of type <code>boolean</code>, readonly</dt>
<dd><p>Used to indicate whether or not an event can have its <a class="def" href="#glossary-default-action">default action</a> prevented (see also <a href="#event-flow-default-cancel">Default actions and cancelable events</a>). If the <a class="def" href="#glossary-default-action">default action</a> can be prevented the value shall be <code>true</code>, otherwise the value shall be <code>false</code>.</p></dd>
- <dt><code class="attribute-name"><a id="events-event-type-currentTarget">currentTarget</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
- <dd><p>Used to indicate the <a href="#events-Events-EventTarget"><code>EventTarget</code></a> whose <a href="#events-Events-EventListener"><code>EventListeners</code></a> are currently being processed. This is particularly useful during the capture and bubbling phases. When used with the <a href="#event-flow">Event dispatch and DOM event flow</a>, this attribute contains the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> or a target ancestor.</p></dd>
+ <dt><code class="attribute-name"><a id="events-event-type-currentTarget">currentTarget</a></code> of type <a href="#events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
+ <dd><p>Used to indicate the <a href="#events-EventTarget"><code>EventTarget</code></a> whose <a href="#events-EventListener"><code>EventListeners</code></a> are currently being processed. This is particularly useful during the capture and bubbling phases. When used with the <a href="#event-flow">Event dispatch and DOM event flow</a>, this attribute contains the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> or a target ancestor.</p></dd>
<dt><code class="attribute-name"><a id="events-event-type-defaultPrevented">defaultPrevented</a></code> of type <code>boolean</code>, readonly, introduced in <strong class="version">DOM Level 3</strong></dt>
<dd><p>Used to indicate whether <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> has been called for this event.</p></dd>
@@ -818,14 +816,14 @@
<dt><code class="attribute-name"><a id="events-event-type-eventPhase">eventPhase</a></code> of type <code>unsigned short</code>, readonly</dt>
<dd><p>Used to indicate which phase of event flow is currently being accomplished.</p></dd>
- <dt><code class="attribute-name"><a id="events-event-type-target">target</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-event-type-target">target</a></code> of type <a href="#events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
<dd><p>Used to indicate the <a class="def" href="#glossary-event-target">event target</a>. This attribute contains the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> when used with the <a href="#event-flow">Event dispatch and DOM event flow</a>.</p></dd>
<dt><code class="attribute-name"><a id="events-event-type-timeStamp">timeStamp</a></code> of type <code>DOMTimeStamp</code>, readonly</dt>
<dd><p>Used to specify the time at which the event was created in milliseconds relative to 1970-01-01T00:00:00Z. Due to the fact that some systems may not provide this information the value of <code>timeStamp</code> may be not available for all events. When not available, the value shall be <code>0</code>.</p></dd>
<dt><code class="attribute-name"><a id="events-event-type-type">type</a></code> of type <code>DOMString</code>, readonly</dt>
- <dd><p>The name of the event type. The name must be a <code>DOMString</code>. <a href="#conf-specs">Specifications that define events</a>, <a href="#conf-authors">authors</a>, and <a href="#conf-author-tools">authoring tools</a> must use case-sensitive event type names that do not contain whitespace characters.</p></dd>
+ <dd><p>The name of the event type. The name must be a <code>DOMString</code>. <a href="#conf-specs">Specifications that define events</a>, <a href="#conf-authors">content authors</a>, and <a href="#conf-author-tools">authoring tools</a> must use case-sensitive event type names that do not contain whitespace characters.</p></dd>
</dl>
</dd>
@@ -840,7 +838,7 @@
</dt>
<dd>
<div class="method">
- <p>Initializes attributes of an <code>Event</code> created through the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent</code></a> method. This method may only be called before the <code>Event</code> has been dispatched via the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method. If the method is called several times before invoking <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent</code></a>, only the final invocation takes precedence. This method has no effect if called after the event has been dispatched. If called from a subclass of the <code>Event</code> interface only the values specified in this method are modified, all other attributes are left unchanged.</p>
+ <p>Initializes attributes of an <code>Event</code> created through the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent</code></a> method. This method may only be called before the <code>Event</code> has been dispatched via the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method. If the method is called several times before invoking <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent</code></a>, only the final invocation takes precedence. This method has no effect if called after the event has been dispatched. If called from a subclass of the <code>Event</code> interface only the values specified in this method are modified, all other attributes are left unchanged.</p>
<p>This method sets the <a href="#events-event-type-type"><code>Event.type</code></a> attribute to <code>eventTypeArg</code>.</p>
<p class="warning" id="warning-initEvent-untrusted"><strong>Warning!</strong> For security reasons, events modified using <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>. See <a href="#trusted-events">trusted events</a> for more details.</p>
@@ -919,10 +917,10 @@
<h3><a id="interface-CustomEvent" href="#interface-CustomEvent">4.2 Interface CustomEvent</a></h3>
<dl>
- <dt><strong>Interface <em><a id="events-Events-CustomEvent">CustomEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-CustomEvent">CustomEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
<dd>
- <p>The <a href="#events-Events-CustomEvent"><code>CustomEvent</code></a> interface is the recommended interface for application-specific event types. Unlike the <a href="#events-Events-Event"><code>Event</code></a> interface, it allows applications to provide contextual information about the event type. Application-specific event types should use a prefix string on the event type name to avoid clashes with future general-purpose event types.</p>
- <p>To create an instance of the <code>CustomEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("CustomEvent")</code></a> method call.</p>
+ <p>The <a href="#events-CustomEvent"><code>CustomEvent</code></a> interface is the recommended interface for application-specific event types. Unlike the <a href="#events-Event"><code>Event</code></a> interface, it allows applications to provide contextual information about the event type. Application-specific event types should use a prefix string on the event type name to avoid clashes with future general-purpose event types.</p>
+ <p>To create an instance of the <code>CustomEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("CustomEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -932,8 +930,8 @@
<pre class="idl" id="idl-interface-CustomEvent"><code>
// Introduced in DOM Level 3:
-interface <a href="#events-Events-CustomEvent">CustomEvent</a> : <a href="#events-Events-Event">Event</a> {
- readonly attribute DOMObject <a href="#events-Events-CustomEvent-detail">detail</a>;
+interface <a href="#events-CustomEvent">CustomEvent</a> : <a href="#events-Event">Event</a> {
+ readonly attribute DOMObject <a href="#events-CustomEvent-detail">detail</a>;
void <a href="#events-event-type-initCustomEvent">initCustomEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
@@ -945,8 +943,8 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-CustomEvent-detail">detail</a></code> of type <code>DOMObject</code>, readonly</dt>
- <dd><p>Specifies some detail information about the <a href="#events-Events-Event"><code>Event</code></a>.</p></dd>
+ <dt><code class="attribute-name"><a id="events-CustomEvent-detail">detail</a></code> of type <code>DOMObject</code>, readonly</dt>
+ <dd><p>Specifies some detail information about the <a href="#events-Event"><code>Event</code></a>.</p></dd>
</dl>
</dd>
@@ -975,7 +973,7 @@
<dd><p>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">detailArg</code> of type <code>DOMObject</code></dt>
- <dd><p>Specifies <a href="#events-Events-CustomEvent-detail"><code>CustomEvent.detail</code></a>. This value may be <code>null</code>.</p></dd>
+ <dd><p>Specifies <a href="#events-CustomEvent-detail"><code>CustomEvent.detail</code></a>. This value may be <code>null</code>.</p></dd>
</dl>
</div>
</div>
@@ -996,16 +994,16 @@
<h3><a id="interface-EventTarget" href="#interface-EventTarget">4.3 Interface EventTarget</a></h3>
<dl>
- <dt><strong>Interface <em><a id="events-Events-EventTarget">EventTarget</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-EventTarget">EventTarget</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
<dd>
<p>The <code>EventTarget</code> interface must be implemented by all the objects which could be <a class="def" href="#glossary-event-target">event targets</a> in an implementation which supports an event flow. The interface allows registration and removal of event listeners, and dispatch of events to an event target.</p>
- <p class="note" id="EventTarget-trusted"><strong>Note:</strong> Though an event listener can be registered for any <a class="def" href="#glossary-event-target">event target</a> node, the user agent only dispatches UA-generated (trusted) events on node types that are defined as proximal event target types for that specific event type (see the <a href="#event-types-list">List of DOM3 Event Types</a>); for example, a <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a> event type registered on a text node will never be fired by the user agent, though an author could dispatch an event of that type on the text node via script.</p>
+ <p class="note" id="EventTarget-trusted"><strong>Note:</strong> Though an event listener can be registered for any <a class="def" href="#glossary-event-target">event target</a> node, the user agent only dispatches UA-generated (trusted) events on node types that are defined as proximal event target types for that specific event type (see the <a href="#event-types-list">List of DOM3 Event Types</a>); for example, a <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a> event type registered on a text node will never be fired by the user agent, though a content author could dispatch an event of that type on the text node via script.</p>
<p>When used with the DOM event flow, this interface must be implemented by all <a class="def" href="#glossary-proximal-event-target">proximal event targets</a> and target ancestors, i.e. all DOM <code>Nodes</code> of the tree support this interface when the implementation conforms to DOM Level 3 Events and, therefore, this interface can be obtained by using binding-specific casting methods on an instance of the <code>Node</code> interface.</p>
- <p>Invoking <code>addEventListener</code> repeatedly on the same <code>EventTarget</code> with the same values for the parameters <code>type</code>, <code>listener</code>, and <code>useCapture</code> has no effect. Doing so does not cause the <a href="#events-Events-EventListener"><code>EventListener</code></a> to be called more than once and does not cause a change in the triggering order.</p>
-
- <p class="note" id="EventTarget-onfoo"><strong>Note:</strong> In addition to the <a href="#events-Events-EventTarget-addEventListener">EventTarget.addEventListener</a> method, some <a class="def" href="#glossary-host-language">host languages</a> may allow an author to register event listeners by the use of attributes, e.g. <em><code>onclick="handleClick()"</code></em>. Because the details of this are often language-specific, this type of event listener registration is not defined in this specification, but in general, any event type may be used as an attribute in this way by adding the prefix <em><code>on-</code></em> to the event type name, and events so dispatched should behave consistently with the event registration and propagation defined in this specification, with the same interfaces, properties, and methods.</p>
+ <p>Invoking <code>addEventListener</code> repeatedly on the same <code>EventTarget</code> with the same values for the parameters <code>type</code>, <code>listener</code>, and <code>useCapture</code> has no effect. Doing so does not cause the <a href="#events-EventListener"><code>EventListener</code></a> to be called more than once and does not cause a change in the triggering order.</p>
+
+ <p class="note" id="EventTarget-onfoo"><strong>Note:</strong> In addition to the <a href="#events-EventTarget-addEventListener">EventTarget.addEventListener</a> method, some <a class="def" href="#glossary-host-language">host languages</a> may allow a content author to register event listeners by the use of attributes, e.g. <em><code>onclick="handleClick()"</code></em>. Because the details of this are often language-specific, this type of event listener registration is not defined in this specification, but in general, any event type may be used as an attribute in this way by adding the prefix <em><code>on-</code></em> to the event type name, and events so dispatched should behave consistently with the event registration and propagation defined in this specification, with the same interfaces, properties, and methods.</p>
<dl>
<dt>
<br />
@@ -1014,16 +1012,16 @@
<dd>
<pre class="idl" id="idl-interface-"><code>
// Introduced in DOM Level 2:
-interface <a href="#events-Events-EventTarget">EventTarget</a> {
- void <a href="#events-Events-EventTarget-addEventListener">addEventListener</a>(in DOMString type,
- in <a href="#events-Events-EventListener">EventListener</a> listener,
+interface <a href="#events-EventTarget">EventTarget</a> {
+ void <a href="#events-EventTarget-addEventListener">addEventListener</a>(in DOMString type,
+ in <a href="#events-EventListener">EventListener</a> listener,
in boolean useCapture);
- void <a href="#events-Events-EventTarget-removeEventListener">removeEventListener</a>(in DOMString type,
- in <a href="#events-Events-EventListener">EventListener</a> listener,
+ void <a href="#events-EventTarget-removeEventListener">removeEventListener</a>(in DOMString type,
+ in <a href="#events-EventListener">EventListener</a> listener,
in boolean useCapture);
// Modified in DOM Level 3:
- boolean <a href="#events-Events-EventTarget-dispatchEvent">dispatchEvent</a>(in <a href="#events-Events-Event">Event</a> evt)
- raises(<a href="#events-Events-EventException">EventException</a>,
+ boolean <a href="#events-EventTarget-dispatchEvent">dispatchEvent</a>(in <a href="#events-Event">Event</a> evt)
+ raises(<a href="#events-EventException">EventException</a>,
DOMException);
};
@@ -1035,7 +1033,7 @@
<dl>
<dt>
<code class="method-name">
- <a id="events-Events-EventTarget-addEventListener">addEventListener</a>
+ <a id="events-EventTarget-addEventListener">addEventListener</a>
</code>
</dt>
<dd>
@@ -1047,8 +1045,8 @@
<dt><code class="parameter-name">type</code> of type <code>DOMString</code></dt>
<dd><p>Specifies the <a href="#events-event-type-type"><code>Event.type</code></a> associated with the event for which the user is registering.</p></dd>
- <dt><code class="parameter-name">listener</code> of type <a href="#events-Events-EventListener"><code>EventListener</code></a></dt>
- <dd><p>The <code>listener</code> parameter takes an object implemented by the user which implements the <a href="#events-Events-EventListener"><code>EventListener</code></a> interface and contains the method to be called when the event occurs.</p></dd>
+ <dt><code class="parameter-name">listener</code> of type <a href="#events-EventListener"><code>EventListener</code></a></dt>
+ <dd><p>The <code>listener</code> parameter takes an object implemented by the user which implements the <a href="#events-EventListener"><code>EventListener</code></a> interface and contains the method to be called when the event occurs.</p></dd>
<dt><a id="addEventListener_useCapture"><code class="parameter-name">useCapture</code></a> of type <code>boolean</code></dt>
<dd><p>If true, <code>useCapture</code> indicates that the user wishes to add the event listener for the <a class="def" href="#glossary-capture-phase">capture phase</a> and <a class="def" href="#glossary-target-phase">target</a> only, i.e. this event listener will not be triggered during the <a class="def" href="#glossary-bubbling-phase">bubbling</a> phase. If <code>false</code>, the event listener must only be triggered during the <a class="def" href="#glossary-target-phase">target</a> and <a class="def" href="#glossary-bubbling-phase">bubbling</a> phases.</p></dd>
@@ -1063,16 +1061,16 @@
<!-- method -->
</dd>
- <dt><code class="method-name"><a id="events-Events-EventTarget-dispatchEvent">dispatchEvent</a></code> modified in <strong class="version">DOM Level 3</strong></dt>
+ <dt><code class="method-name"><a id="events-EventTarget-dispatchEvent">dispatchEvent</a></code> modified in <strong class="version">DOM Level 3</strong></dt>
<dd>
<div class="method">Dispatches an event into the implementation's event model. The <a class="def" href="#glossary-event-target">event target</a> of the event shall be the <code>EventTarget</code> object on which <code>dispatchEvent</code> is called.
- <p class="warning" id="warning-dispatchEvent-untrusted"><strong>Warning!</strong> For security reasons, events dispatched using <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>. See <a href="#trusted-events">trusted events</a> for more details.</p>
+ <p class="warning" id="warning-dispatchEvent-untrusted"><strong>Warning!</strong> For security reasons, events dispatched using <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>. See <a href="#trusted-events">trusted events</a> for more details.</p>
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
<dl>
- <dt><code class="parameter-name">evt</code> of type <a href="#events-Events-Event"><code>Event</code></a></dt>
+ <dt><code class="parameter-name">evt</code> of type <a href="#events-Event"><code>Event</code></a></dt>
<dd><p>The event to be dispatched.</p></dd>
</dl>
</div>
@@ -1080,28 +1078,28 @@
<!-- parameters -->
<div class="return"><strong>Return Value</strong><div class="returntable"><table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr><td><p><code>boolean</code></p></td><td><p>Indicates whether any of the listeners which handled the event called <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a>. If <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> was called the returned value shall be <code>false</code>, else it shall be <code>true</code>.</p></td></tr></table></div></div>
<!-- return -->
- <div class="exceptions"><strong>Exceptions</strong><div class="exceptiontable"><table summary="Layout table: the first cell contains the type of the exception, the second contains the specific error code and a short description" border="0"><tr><td><p><a href="#events-Events-EventException"><code>EventException</code></a></p></td><td><p>UNSPECIFIED_EVENT_TYPE_ERR: Raised if the <a href="#events-event-type-type"><code>Event.type</code></a> was not specified by initializing the event before <code>dispatchEvent</code> was called. Specification of the <a href="#events-event-type-type"><code>Event.type</code></a> as <code>null</code> or an empty string must also trigger this exception.</p><p>DISPATCH_REQUEST_ERR: Raised if the <a href="#events-Events-Event"><code>Event</code></a> object is already being dispatched.</p></td></tr><tr><td><p><code>DOMException</code></p></td><td><p>NOT_SUPPORTED_ERR: Raised if the <a href="#events-Events-Event"><code>Event</code></a> object has not been created using <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent()</code></a>.</p><p>INVALID_CHARACTER_ERR: Raised if <a href="#events-event-type-type"><code>Event.type</code></a> is not a <code>DOMString</code> as conforming to the restrictions in <a href="#events-event-type-type"><code>Event.type</code></a>.</p></td></tr></table></div></div>
+ <div class="exceptions"><strong>Exceptions</strong><div class="exceptiontable"><table summary="Layout table: the first cell contains the type of the exception, the second contains the specific error code and a short description" border="0"><tr><td><p><a href="#events-EventException"><code>EventException</code></a></p></td><td><p>UNSPECIFIED_EVENT_TYPE_ERR: Raised if the <a href="#events-event-type-type"><code>Event.type</code></a> was not specified by initializing the event before <code>dispatchEvent</code> was called. Specification of the <a href="#events-event-type-type"><code>Event.type</code></a> as <code>null</code> or an empty string must also trigger this exception.</p><p>DISPATCH_REQUEST_ERR: Raised if the <a href="#events-Event"><code>Event</code></a> object is already being dispatched.</p></td></tr><tr><td><p><code>DOMException</code></p></td><td><p>NOT_SUPPORTED_ERR: Raised if the <a href="#events-Event"><code>Event</code></a> object has not been created using <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent()</code></a>.</p><p>INVALID_CHARACTER_ERR: Raised if <a href="#events-event-type-type"><code>Event.type</code></a> is not a <code>DOMString</code> as conforming to the restrictions in <a href="#events-event-type-type"><code>Event.type</code></a>.</p></td></tr></table></div></div>
<!-- exceptions --></div>
<!-- method -->
</dd>
<dt>
<code class="method-name">
- <a id="events-Events-EventTarget-removeEventListener">removeEventListener</a>
+ <a id="events-EventTarget-removeEventListener">removeEventListener</a>
</code>
</dt>
<dd>
- <div class="method">Removes an event listener. Calling <code>removeEventListener</code> with arguments which do not identify any currently registered <a href="#events-Events-EventListener"><code>EventListener</code></a> on the <code>EventTarget</code> has no effect.
+ <div class="method">Removes an event listener. Calling <code>removeEventListener</code> with arguments which do not identify any currently registered <a href="#events-EventListener"><code>EventListener</code></a> on the <code>EventTarget</code> has no effect.
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
<dl>
<dt><code class="parameter-name">type</code> of type <code>DOMString</code></dt>
<dd><p>Specifies the <a href="#events-event-type-type"><code>Event.type</code></a> for which the user registered the event listener.</p></dd>
- <dt><code class="parameter-name">listener</code> of type <a href="#events-Events-EventListener"><code>EventListener</code></a></dt>
- <dd><p>The <a href="#events-Events-EventListener"><code>EventListener</code></a> to be removed.</p></dd>
+ <dt><code class="parameter-name">listener</code> of type <a href="#events-EventListener"><code>EventListener</code></a></dt>
+ <dd><p>The <a href="#events-EventListener"><code>EventListener</code></a> to be removed.</p></dd>
<dt><code class="parameter-name">useCapture</code> of type <code>boolean</code></dt>
- <dd><p>Specifies whether the <a href="#events-Events-EventListener"><code>EventListener</code></a> being removed was registered for the capture phase or not. If a listener was registered twice, once for the capture and target phases and once for the target and bubbling phases, each must be removed separately. Removal of an event listener registered for the capture and target phases does not affect the same event listener registered for the target and bubbling phases, and vice versa.</p></dd>
+ <dd><p>Specifies whether the <a href="#events-EventListener"><code>EventListener</code></a> being removed was registered for the capture phase or not. If a listener was registered twice, once for the capture and target phases and once for the target and bubbling phases, each must be removed separately. Removal of an event listener registered for the capture and target phases does not affect the same event listener registered for the target and bubbling phases, and vice versa.</p></dd>
</dl>
</div>
</div>
@@ -1122,9 +1120,9 @@
<h3><a id="interface-EventListener" href="#interface-EventListener">4.4 Interface EventListener</a></h3>
<dl>
- <dt><strong>Interface <em><a id="events-Events-EventListener">EventListener</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-EventListener">EventListener</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
<dd>
- <p>The <code>EventListener</code> interface is the primary way for handling events. Users shall implement the <code>EventListener</code> interface and register their event listener on an <a href="#events-Events-EventTarget"><code>EventTarget</code></a>. The users should also remove their <code>EventListener</code> from its <a href="#events-Events-EventTarget"><code>EventTarget</code></a> after they have completed using the listener.</p>
+ <p>The <code>EventListener</code> interface is the primary way for handling events. Users shall implement the <code>EventListener</code> interface and register their event listener on an <a href="#events-EventTarget"><code>EventTarget</code></a>. The users should also remove their <code>EventListener</code> from its <a href="#events-EventTarget"><code>EventTarget</code></a> after they have completed using the listener.</p>
<p>
<span class="assert must">Copying a <code>Node</code>, with methods such as <code>Node.cloneNode</code> or <code>Range.cloneContents</code>, must not copy the event listeners attached to it.</span>
<span class="assert must">Event listeners must be attached to the newly created <code>Node</code> afterwards if so desired.</span>
@@ -1140,8 +1138,8 @@
<dd>
<pre class="idl" id="idl-interface-EventListener"><code>
// Introduced in DOM Level 2:
-interface <a href="#events-Events-EventListener">EventListener</a> {
- void <a href="#events-Events-EventListener-handleEvent">handleEvent</a>(in <a href="#events-Events-Event">Event</a> evt);
+interface <a href="#events-EventListener">EventListener</a> {
+ void <a href="#events-EventListener-handleEvent">handleEvent</a>(in <a href="#events-Event">Event</a> evt);
};
</code></pre>
</dd>
@@ -1151,7 +1149,7 @@
<dl>
<dt>
<code class="method-name">
- <a id="events-Events-EventListener-handleEvent">handleEvent</a>
+ <a id="events-EventListener-handleEvent">handleEvent</a>
</code>
</dt>
<dd>
@@ -1161,8 +1159,8 @@
<strong>Parameters</strong>
<div class="paramtable">
<dl>
- <dt><code class="parameter-name">evt</code> of type <a href="#events-Events-Event"><code>Event</code></a></dt>
- <dd><p>The <a href="#events-Events-Event"><code>Event</code></a> contains contextual information about the <a class="def" href="#glossary-event">event</a>.</p></dd>
+ <dt><code class="parameter-name">evt</code> of type <a href="#events-Event"><code>Event</code></a></dt>
+ <dd><p>The <a href="#events-Event"><code>Event</code></a> contains contextual information about the <a class="def" href="#glossary-event">event</a>.</p></dd>
</dl>
</div>
</div>
@@ -1178,9 +1176,9 @@
</dl>
</dd>
- <dt><strong>Exception <em><a id="events-Events-EventException">EventException</a></em></strong> introduced in <strong class="version">DOM Level 2</strong></dt>
+ <dt><strong>Exception <em><a id="events-EventException">EventException</a></em></strong> introduced in <strong class="version">DOM Level 2</strong></dt>
<dd>
- <p>Event operations may throw an <a href="#events-Events-EventException"><code>EventException</code></a> as specified in their method descriptions.</p>
+ <p>Event operations may throw an <a href="#events-EventException"><code>EventException</code></a> as specified in their method descriptions.</p>
<dl>
<dt>
<br />
@@ -1189,7 +1187,7 @@
<dd>
<pre class="idl" id="idl-interface-EventException"><code>
// Introduced in DOM Level 2:
-exception <a href="#events-Events-EventException">EventException</a> {
+exception <a href="#events-EventException">EventException</a> {
unsigned short code;
};
@@ -1201,7 +1199,7 @@
</dd>
<dt>
- <strong>Definition group <em><a id="events-Events-EventException-EventExceptionCode">EventExceptionCode</a></em></strong>
+ <strong>Definition group <em><a id="events-EventException-EventExceptionCode">EventExceptionCode</a></em></strong>
</dt>
<dd>
<p>An integer indicating the type of error generated.</p>
@@ -1210,7 +1208,7 @@
<dd>
<dl>
<dt><a id="events-DISPATCH_REQUEST_ERR"><code class="constant-name">DISPATCH_REQUEST_ERR</code></a>, introduced in <strong class="version">DOM Level 3</strong>.</dt>
- <dd>If the <a href="#events-Events-Event"><code>Event</code></a> object is already dispatched in the tree.</dd>
+ <dd>If the <a href="#events-Event"><code>Event</code></a> object is already dispatched in the tree.</dd>
<dt><a id="events-UNSPECIFIED_EVENT_TYPE_ERR"><code class="constant-name">UNSPECIFIED_EVENT_TYPE_ERR</code></a></dt>
<dd>If the <a href="#events-event-type-type"><code>Event.type</code></a> was not specified by initializing the event before the method was called. Specification of the <a href="#events-event-type-type"><code>Event.type</code></a> as <code>null</code> or an empty string must also trigger this exception.</dd>
@@ -1228,9 +1226,9 @@
<h3><a id="interface-DocumentEvent" href="#interface-DocumentEvent">4.5 Interface DocumentEvent</a></h3>
<dl>
- <dt><strong>Interface <em><a id="events-Events-DocumentEvent">DocumentEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-DocumentEvent">DocumentEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
<dd>
- <p>The <code>DocumentEvent</code> interface provides a mechanism by which the user can create an <a href="#events-Events-Event"><code>Event</code></a> object of a type supported by the implementation. If the feature "Events" is supported by the <code>Document</code> object, the <code>DocumentEvent</code> interface must be implemented on the same object. Language-specific type casting may be required.</p>
+ <p>The <code>DocumentEvent</code> interface provides a mechanism by which the user can create an <a href="#events-Event"><code>Event</code></a> object of a type supported by the implementation. If the feature "Events" is supported by the <code>Document</code> object, the <code>DocumentEvent</code> interface must be implemented on the same object. Language-specific type casting may be required.</p>
<dl>
<dt>
<br />
@@ -1239,9 +1237,9 @@
<dd>
<pre class="idl" id="idl-interface-DocumentEvent"><code>
// Introduced in DOM Level 2:
-interface <a href="#events-Events-DocumentEvent">DocumentEvent</a> {
+interface <a href="#events-DocumentEvent">DocumentEvent</a> {
// Modified in DOM Level 3:
- <a href="#events-Events-Event">Event</a> <a href="#events-Events-DocumentEvent-createEvent">createEvent</a>(in DOMString eventInterface)
+ <a href="#events-Event">Event</a> <a href="#events-DocumentEvent-createEvent">createEvent</a>(in DOMString eventInterface)
raises(DOMException);
};
</code></pre>
@@ -1252,7 +1250,7 @@
<dl>
<dt>
<code class="method-name">
- <a id="events-Events-DocumentEvent-createEvent">createEvent</a>
+ <a id="events-DocumentEvent-createEvent">createEvent</a>
</code>
</dt>
<dd>
@@ -1263,10 +1261,10 @@
<dl>
<dt><code class="parameter-name">eventInterface</code> of type <code>DOMString</code></dt>
<dd>
- <p>The <code>eventInterface</code> parameter specifies the name of the DOM Events interface to be supported by the created event object, e.g. <code>"Event"</code>, <code>"MouseEvent"</code>, <code>"MutationEvent"</code>, and so on. If the <a href="#events-Events-Event"><code>Event</code></a> is to be dispatched via the <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method, the appropriate event initialization method must be called after creation in order to initialize the <a class="noxref" href="#events-Events-Event"><code>Event</code></a>'s values.</p>
- <p class="example" id="example-createEvent"><strong>Example:</strong> An author wishing to synthesize some kind of <a href="#events-Events-UIEvent"><code>UIEvent</code></a> would invoke <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("UIEvent")</code></a>. The <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method could then be called on the newly created <a class="noxref" href="#events-Events-UIEvent"><code>UIEvent</code></a> object to set the specific type of user interface event to be dispatched, <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> for example, and set its context information, e.g. <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a>.</p>
- <p>For backward compatibility reason, <code>"UIEvents"</code>, <code>"MouseEvents"</code>, <code>"MutationEvents"</code>, and <code>"HTMLEvents"</code> feature names are valid values for the parameter <code>eventInterface</code> and represent respectively the interfaces <a href="#events-Events-UIEvent"><code>UIEvent</code></a>, <a href="#events-Events-MouseEvent"><code>MouseEvent</code></a>, <a href="#events-Events-MutationEvent"><code>MutationEvent</code></a>, and <a href="#interface-Event"><code>Event</code></a>, and the characters <code>'a'..'z'</code> are considered equivalent to the characters <code>'A'..'Z'</code>.</p>
- <p>If the parameter does not match an event interface name supported by the implementation, the implementation must raise a <code>NOT_SUPPORTED_ERR</code> <code>DOMException</code></p><p class="warning" id="warning-createEvent-untrusted"><strong>Warning!</strong> For security reasons, events generated using <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>. See <a href="#trusted-events">trusted events</a> for more details.</p>
+ <p>The <code>eventInterface</code> parameter specifies the name of the DOM Events interface to be supported by the created event object, e.g. <code>"Event"</code>, <code>"MouseEvent"</code>, <code>"MutationEvent"</code>, and so on. If the <a href="#events-Event"><code>Event</code></a> is to be dispatched via the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method, the appropriate event initialization method must be called after creation in order to initialize the <a class="noxref" href="#events-Event"><code>Event</code></a>'s values.</p>
+ <p class="example" id="example-createEvent"><strong>Example:</strong> A content author wishing to synthesize some kind of <a href="#events-UIEvent"><code>UIEvent</code></a> would invoke <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("UIEvent")</code></a>. The <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method could then be called on the newly created <a class="noxref" href="#events-UIEvent"><code>UIEvent</code></a> object to set the specific type of user interface event to be dispatched, <a class="eventtype" href="#event-type-scroll"><code>scroll</code></a> for example, and set its context information, e.g. <a href="#events-UIEvent-detail"><code>UIEvent.detail</code></a>.</p>
+ <p>For backward compatibility reason, <code>"UIEvents"</code>, <code>"MouseEvents"</code>, <code>"MutationEvents"</code>, and <code>"HTMLEvents"</code> feature names are valid values for the parameter <code>eventInterface</code> and represent respectively the interfaces <a href="#events-UIEvent"><code>UIEvent</code></a>, <a href="#events-MouseEvent"><code>MouseEvent</code></a>, <a href="#events-MutationEvent"><code>MutationEvent</code></a>, and <a href="#interface-Event"><code>Event</code></a>, and the characters <code>'a'..'z'</code> are considered equivalent to the characters <code>'A'..'Z'</code>.</p>
+ <p>If the parameter does not match an event interface name supported by the implementation, the implementation must raise a <code>NOT_SUPPORTED_ERR</code> <code>DOMException</code></p><p class="warning" id="warning-createEvent-untrusted"><strong>Warning!</strong> For security reasons, events generated using <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("Event")</code></a> must have a <code class="attribute-name"><a href="#events-event-type-trusted">trusted</a></code> attribute value of <code>false</code>. See <a href="#trusted-events">trusted events</a> for more details.</p>
</dd>
</dl>
</div>
@@ -1275,14 +1273,14 @@
<div class="return">
<strong>Return Value</strong>
<div class="returntable">
- <table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr><td><p><a href="#events-Events-Event"><code>Event</code></a></p></td><td><p>The newly created event object.</p></td></tr></table>
+ <table summary="Layout table: the first cell contains the type of the return value, the second contains a short description" border="0"><tr><td><p><a href="#events-Event"><code>Event</code></a></p></td><td><p>The newly created event object.</p></td></tr></table>
</div>
</div>
<!-- return -->
<div class="exceptions">
<strong>Exceptions</strong>
<div class="exceptiontable">
- <table summary="Layout table: the first cell contains the type of the exception, the second contains the specific error code and a short description" border="0"><tr><td><p><code>DOMException</code></p></td><td><p>NOT_SUPPORTED_ERR: Raised if the implementation does not support the <a href="#events-Events-Event"><code>Event</code></a> interface requested.</p></td></tr></table>
+ <table summary="Layout table: the first cell contains the type of the exception, the second contains the specific error code and a short description" border="0"><tr><td><p><code>DOMException</code></p></td><td><p>NOT_SUPPORTED_ERR: Raised if the implementation does not support the <a href="#events-Event"><code>Event</code></a> interface requested.</p></td></tr></table>
</div>
</div>
<!-- exceptions -->
@@ -1296,8 +1294,8 @@
</dl>
<h4><a id="event-creation" href="#event-creation">4.5.1 Event creation</a></h4>
- <p>In most cases, the events dispatched by the DOM Events implementation are also created by the implementation. However, it is possible to simulate events, such as mouse events, by creating the <a href="#events-Events-Event"><code>Event</code></a> objects and dispatch them using the DOM Events implementation.</p>
- <p>Creating <a href="#events-Events-Event"><code>Event</code></a> objects that are known to the DOM Events implementation is done using <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent()</code></a>. The author must then initialize the <a href="#events-Events-Event"><code>Event</code></a> object by directly setting the <a href="#events-Events-Event"><code>Event</code></a>'s property values, by using the generic <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method, or by using any existing event initialization method for that interface, before invoking <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a>. The <a href="#events-Events-Event"><code>Event</code></a> objects created must be known by the DOM Events implementation; otherwise an event exception shall be thrown.</p>
+ <p>In most cases, the events dispatched by the DOM Events implementation are also created by the implementation. However, it is possible to simulate events, such as mouse events, by creating the <a href="#events-Event"><code>Event</code></a> objects and dispatch them using the DOM Events implementation.</p>
+ <p>Creating <a href="#events-Event"><code>Event</code></a> objects that are known to the DOM Events implementation is done using <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent()</code></a>. The content author must then initialize the <a href="#events-Event"><code>Event</code></a> object by directly setting the <a href="#events-Event"><code>Event</code></a>'s property values, by using the generic <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method, or by using any existing event initialization method for that interface, before invoking <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a>. The <a href="#events-Event"><code>Event</code></a> objects created must be known by the DOM Events implementation; otherwise an event exception shall be thrown.</p>
<p class="example" id="example-create-event">
<strong>Example:</strong>
<i class="note" id="_6"><strong>To Do:</strong> Create examples of creating and dispatching an event.</i>
@@ -1337,7 +1335,7 @@
<td>Sync</td>
<td>No</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ <td><a href="#events-Event"><code>Event</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1348,7 +1346,7 @@
<td>Sync</td>
<td>No</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+ <td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1359,7 +1357,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>Yes</td>
<td><a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event</td>
</tr>
@@ -1370,7 +1368,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td>
+ <td><a href="#events-CompositionEvent"><code>CompositionEvent</code></a></td>
<td>Yes</td>
<td>Launch <a class="def" href="#glossary-text-composition-system">text composition system</a></td>
</tr>
@@ -1381,7 +1379,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td>
+ <td><a href="#events-CompositionEvent"><code>CompositionEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1392,7 +1390,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td>
+ <td><a href="#events-CompositionEvent"><code>CompositionEvent</code></a></td>
<td>No</td>
<td><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event</td>
</tr>
@@ -1403,7 +1401,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1414,7 +1412,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ <td><a href="#events-UIEvent"><code>UIEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1425,7 +1423,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
+ <td><a href="#events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1436,7 +1434,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ <td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1447,7 +1445,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>ProcessingInstruction</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ <td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1458,7 +1456,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
+ <td><a href="#events-MutationNameEvent"><code>MutationNameEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1469,7 +1467,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+ <td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1480,7 +1478,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+ <td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1491,7 +1489,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ <td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1502,7 +1500,7 @@
<td>Sync</td>
<td>No</td>
<td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ <td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1513,7 +1511,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ <td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1524,7 +1522,7 @@
<td>Sync</td>
<td>No</td>
<td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ <td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1535,7 +1533,7 @@
<td>Sync</td>
<td>Yes</td>
<td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>DocumentFragment</code>, <code>Element</code>, <code>Attr</code></td>
- <td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td>
+ <td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1546,7 +1544,7 @@
<td>Async</td>
<td>No</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ <td><a href="#events-Event"><code>Event</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1557,7 +1555,7 @@
<td>Sync</td>
<td>No</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+ <td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1568,7 +1566,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+ <td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1579,7 +1577,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td>
+ <td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1590,7 +1588,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
+ <td><a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
<td>Yes</td>
<td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td>
</tr>
@@ -1601,7 +1599,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
+ <td><a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
<td>Yes</td>
<td>Varies: <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event; launch <a class="def" href="#glossary-text-composition-system">text composition system</a>; <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focus"><code>focus</code></a> events; <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event; other event</td>
</tr>
@@ -1612,7 +1610,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
+ <td><a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1623,7 +1621,7 @@
<td>Async</td>
<td>No</td>
<td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ <td><a href="#events-Event"><code>Event</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1634,7 +1632,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1645,7 +1643,7 @@
<td>Sync</td>
<td>No</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1656,7 +1654,7 @@
<td>Sync</td>
<td>No</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1667,7 +1665,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1678,7 +1676,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1689,7 +1687,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1700,7 +1698,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td>
+ <td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1711,7 +1709,7 @@
<td>Sync</td>
<td>No</td>
<td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ <td><a href="#events-UIEvent"><code>UIEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1722,7 +1720,7 @@
<td>Async</td>
<td>No</td>
<td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td>
+ <td><a href="#events-UIEvent"><code>UIEvent</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1733,7 +1731,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ <td><a href="#events-Event"><code>Event</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1744,7 +1742,7 @@
<td>Sync</td>
<td>Yes</td>
<td><code>Element</code></td>
- <td><a href="#events-Events-TextEvent"><code>TextEvent</code></a></td>
+ <td><a href="#events-TextEvent"><code>TextEvent</code></a></td>
<td>Yes</td>
<td>none</td>
</tr>
@@ -1755,7 +1753,7 @@
<td>Sync</td>
<td>No</td>
<td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-Event"><code>Event</code></a></td>
+ <td><a href="#events-Event"><code>Event</code></a></td>
<td>No</td>
<td>none</td>
</tr>
@@ -1766,7 +1764,7 @@
<td>Async</td>
<td>Yes</td>
<td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td>
- <td><a href="#events-Events-WheelEvent"><code>WheelEvent</code></a></td>
+ <td><a href="#events-WheelEvent"><code>WheelEvent</code></a></td>
<td>Yes</td>
<td>Scroll (or zoom) the document</td>
</tr>
@@ -1787,10 +1785,10 @@
<p>This module defines the feature UIEvents 3.0 and depends on the features Events 3.0 and Views 2.0.</p>
<p>The User Interface event module contains basic event types associated with user interfaces and document manipulation.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-UIEvent">UIEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-UIEvent">UIEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
<dd>
<p>The <code>UIEvent</code> interface provides specific contextual information associated with User Interface events.</p>
- <p>To create an instance of the <code>UIEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("UIEvent")</code></a> method call.</p>
+ <p>To create an instance of the <code>UIEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("UIEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -1799,9 +1797,9 @@
<dd>
<pre class="idl" id="idl-interface-UIEvent"><code>
// Introduced in DOM Level 2:
-interface <a href="#events-Events-UIEvent">UIEvent</a> : <a href="#events-Events-Event">Event</a> {
- readonly attribute views::AbstractView <a href="#events-Events-UIEvent-view">view</a>;
- readonly attribute long <a href="#events-Events-UIEvent-detail">detail</a>;
+interface <a href="#events-UIEvent">UIEvent</a> : <a href="#events-Event">Event</a> {
+ readonly attribute views::AbstractView <a href="#events-UIEvent-view">view</a>;
+ readonly attribute long <a href="#events-UIEvent-detail">detail</a>;
void <a href="#events-event-type-initUIEvent">initUIEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
@@ -1814,10 +1812,10 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-UIEvent-detail">detail</a></code> of type <code>long</code>, readonly</dt>
- <dd><p>Specifies some detail information about the <a href="#events-Events-Event"><code>Event</code></a>, depending on the type of event.</p></dd>
-
- <dt><code class="attribute-name"><a id="events-Events-UIEvent-view">view</a></code> of type <code>views::AbstractView</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-UIEvent-detail">detail</a></code> of type <code>long</code>, readonly</dt>
+ <dd><p>Specifies some detail information about the <a href="#events-Event"><code>Event</code></a>, depending on the type of event.</p></dd>
+
+ <dt><code class="attribute-name"><a id="events-UIEvent-view">view</a></code> of type <code>views::AbstractView</code>, readonly</dt>
<dd><p>The <code>view</code> attribute identifies the <code>AbstractView</code> from which the event was generated.</p></dd>
</dl>
@@ -1848,10 +1846,10 @@
<dd><p>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">viewArg</code> of type <code>views::AbstractView</code></dt>
- <dd><p>Specifies <a href="#events-Events-UIEvent-view"><code>UIEvent.view</code></a>. This value may be <code>null</code>.</p></dd>
+ <dd><p>Specifies <a href="#events-UIEvent-view"><code>UIEvent.view</code></a>. This value may be <code>null</code>.</p></dd>
<dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-UIEvent-detail"><code>UIEvent.detail</code></a>.</p></dd>
</dl>
</div>
</div>
@@ -1867,7 +1865,7 @@
</dl>
</dd>
</dl>
- <p>The User Interface event types are listed below. Some of these events use the <a href="#events-Events-UIEvent"><code>UIEvent</code></a> interface if generated from a user interface, but the <a href="#events-Events-Event"><code>Event</code></a> interface otherwise, as detailed in each event.</p>
+ <p>The User Interface event types are listed below. Some of these events use the <a href="#events-UIEvent"><code>UIEvent</code></a> interface if generated from a user interface, but the <a href="#events-Event"><code>Event</code></a> interface otherwise, as detailed in each event.</p>
<!-- DOMActivate -->
<div class="event-definition assert must">
@@ -1878,7 +1876,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMActivate</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -1888,15 +1886,15 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
</table>
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a button, link, or other state-changing element is activated. Refer to <a href="#event-flow-activation">Activation triggers and behavior</a> for more details.</p>
<p class="warning" id="DOMActivate-deprecated"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor of the related <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a>. Other specifications may define and maintain their own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> for backwards compatibility.</p>
- <p class="note" id="DOMActivate-click"><strong>Note:</strong> While <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> and <a class="eventtype" href="#event-type-click"><code>click</code></a> are not completely equivalent, implemented behavior for the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> has developed to encompass the most critical accessibility aspects for which the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> was designed, and is more widely implemented. Authors are encouraged to use the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> rather than the related <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> or <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> <a class="def" href="#glossary-event-type">event type</a> to ensure maximum accessibility.</p>
+ <p class="note" id="DOMActivate-click"><strong>Note:</strong> While <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> and <a class="eventtype" href="#event-type-click"><code>click</code></a> are not completely equivalent, implemented behavior for the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> has developed to encompass the most critical accessibility aspects for which the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a> was designed, and is more widely implemented. Content authors are encouraged to use the <a class="eventtype" href="#event-type-click"><code>click</code></a> <a class="def" href="#glossary-event-type">event type</a> rather than the related <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> or <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> <a class="def" href="#glossary-event-type">event type</a> to ensure maximum accessibility.</p>
The activate event occurs when an element is activated, for instance, thru a mouse click or a keypress. A numerical argument is provided to give an indication of the type of activation that occurs: 1 for a simple activation (e.g. a simple click or Enter), 2 for hyperactivation (for instance a double click or Shift Enter).
@@ -1914,7 +1912,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>load</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Event"><code>Event</code></a> otherwise.</td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
@@ -1924,8 +1922,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -1943,7 +1941,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMContentLoaded</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Event"><code>Event</code></a> otherwise.</td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
@@ -1953,8 +1951,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -1975,7 +1973,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>unload</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Event"><code>Event</code></a> otherwise.</td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
@@ -1985,8 +1983,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2006,7 +2004,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>abort</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Event"><code>Event</code></a> otherwise.</td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2016,8 +2014,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2037,7 +2035,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>error</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Event"><code>Event</code></a> otherwise.</td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2047,8 +2045,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2068,7 +2066,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>select</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Events-Event"><code>Event</code></a> otherwise.</td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a> if generated from a user interface, <a href="#events-Event"><code>Event</code></a> otherwise.</td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2078,8 +2076,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2087,9 +2085,9 @@
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a user selects some text. This event is dispatched after the selection has occurred.</p>
- <p>This specification does not provide contextual information to access the selected text. Where applicable, a <a class="def" href="#glossary-host-language">host language</a> should define rules for how a user may select content (with consideration for international language conventions), at what point the <a class="eventtype" href="#event-type-select"><code>select</code></a> event is dispatched, and how an author may access the user-selected content.</p>
+ <p>This specification does not provide contextual information to access the selected text. Where applicable, a <a class="def" href="#glossary-host-language">host language</a> should define rules for how a user may select content (with consideration for international language conventions), at what point the <a class="eventtype" href="#event-type-select"><code>select</code></a> event is dispatched, and how a content author may access the user-selected content.</p>
- <p class="note" id="note-get-select"><strong>Note:</strong> In order to access to user-selected content, authors should use native capabilities of the <a class="def" href="#glossary-host-language">host languages</a>, such as the <code>Document.getSelection()</code> method of HTML's <a href="http://dev.w3.org/html5/spec/editing.html#selection" title="7 User Interaction — HTML 5">text selection APIs</a> [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>].</p>
+ <p class="note" id="note-get-select"><strong>Note:</strong> In order to access to user-selected content, content authors should use native capabilities of the <a class="def" href="#glossary-host-language">host languages</a>, such as the <code>Document.getSelection()</code> method of HTML's <a href="http://dev.w3.org/html5/spec/editing.html#selection" title="7 User Interaction — HTML 5">text selection APIs</a> [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>].</p>
<p class="note" id="note-select-na"><strong>Note:</strong> The <a class="eventtype" href="#event-type-select"><code>select</code></a> event may not be available for all elements in all languages. For example, in [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>], <a class="eventtype" href="#event-type-select"><code>select</code></a> events may only be dispatched on only form <code>input</code> and <code>textarea</code> elements. Implementations may dispatch <a class="eventtype" href="#event-type-select"><code>select</code></a> events in any context deemed appropriate, including text selections outside of form controls, or image or markup selections such as in SVG.</p>
@@ -2107,7 +2105,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>resize</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
@@ -2117,8 +2115,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2129,8 +2127,8 @@
<p class="note" id="note-resize-multiple"><strong>Note:</strong> Some <a class="def" href="#glossary-user-agent">user agents</a> may have an optional mode in which the document is reflowed dynamically while the window is resized; in this mode, <a class="eventtype" href="#event-type-resize"><code>resize</code></a> events may be dispatched continuously while the resizing operation is in progress.</p>
<p>Once the user has finished resizing, in a system- and implementation-determined manner such as the release of the pointer button or after a sufficiently long pause, or once any instant resizing (e.g. from a window maximize button or a script effect) has been executed, the <a class="def" href="#glossary-user-agent">user agent</a> must perform any relevant layout recalculations or other actions caused by the resizing, and must subsequently dispatch a single <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event that reflects the final state of the <a class="def" href="#glossary-event-target">event target</a>. In the case where multiple <a class="eventtype" href="#event-type-resize"><code>resize</code></a> events have been triggered as the result of the same action, even for different <a class="def" href="#glossary-event-target">event target</a>, the <a class="def" href="#glossary-user-agent">user agent</a> must dispatch each <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event only after the previous <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event has completed its <a class="def" href="#glossary-propagation-path">propagation path</a> or been canceled.</p>
<p class="issue" id="issue-resize-queue"><strong>Issue:</strong> There is no current interoperability here. See <a href="http://www.w3.org/2008/webapps/track/issues/113" title="ISSUE-113 - Web Applications Working Group Tracker">ISSUE-113</a>.</p>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> should dispatch the <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event before the document is re-rendered, to provide the author an opportunity to adjust the content to suit the new size.</p>
- <p class="issue" id="issue-resize-repaint"><strong>Issue:</strong> Firing the event between reflow and repaint may be difficult in some UAs (see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=227495#c30">Mozilla Bug #227495</a>), but it seems the behavior most authors would want. Should we keep this, or change it to fire after repaint?</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> should dispatch the <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event before the document is re-rendered, to provide the content author an opportunity to adjust the content to suit the new size.</p>
+ <p class="issue" id="issue-resize-repaint"><strong>Issue:</strong> Firing the event between reflow and repaint may be difficult in some UAs (see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=227495#c30">Mozilla Bug #227495</a>), but it seems the behavior most content authors would want. Should we keep this, or change it to fire after repaint?</p>
<!-- <p class="example" id="example-resize"><strong>Example:</strong> </p> -->
<p>The <a class="def" href="#glossary-defaultView"><code>defaultView</code></a> object should always be resizable. A <a class="def" href="#glossary-host-language">host language</a> should define which elements, if any, are resizable, and under what conditions (e.g. specific elements like <code class="element">iframe</code>, or elements with particular characteristics like width and height).</p>
<p class="note" id="note-resize-zoom"><strong>Note:</strong> The <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event is distinct from the SVG <code class="eventtype">zoom</code> event types, though both may occur at the same time, or as the consequence of the same user action. In particular, browser "font zooming" or "page zooming" should not necessarily trigger a <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event.</p>
@@ -2148,7 +2146,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>scroll</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-UIEvent"><code>UIEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-UIEvent"><code>UIEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
@@ -2158,8 +2156,8 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2181,10 +2179,10 @@
<p class="note" id="note-focus-uaag"><strong>Note:</strong> This interface and its associated event types and <a href="#events-focusevent-event-order">event order</a> were designed in accordance to the concepts and guidelines defined in <a href="http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100308/">User Agent Accessibility Guidelines 2.0</a> [<a href="#references-UAAG2">UAAG 2.0</a>], with particular attention on the <a href="http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100308/#gl-focus-mechanism">focus mechanism</a> and the terms defined in the <a href="http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100308/#def-focus">glossary entry for focus</a>.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-FocusEvent">FocusEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-FocusEvent">FocusEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
<dd>
<p>The <code>FocusEvent</code> interface provides specific contextual information associated with Focus events.</p>
- <p>To create an instance of the <code>FocusEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("FocusEvent")</code></a> method call.</p>
+ <p>To create an instance of the <code>FocusEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("FocusEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -2193,14 +2191,14 @@
<dd>
<pre class="idl" id="idl-interface-FocusEvent"><code>
// Introduced in DOM Level 3:
-interface <a href="#events-Events-FocusEvent">FocusEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
- readonly attribute <a href="#events-Events-EventTarget">EventTarget</a> <a href="#events-Events-FocusEvent-relatedTarget">relatedTarget</a>;
+interface <a href="#events-FocusEvent">FocusEvent</a> : <a href="#events-UIEvent">UIEvent</a> {
+ readonly attribute <a href="#events-EventTarget">EventTarget</a> <a href="#events-FocusEvent-relatedTarget">relatedTarget</a>;
void <a href="#events-event-type-initFocusEvent">initFocusEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
in views::AbstractView viewArg,
in long detailArg,
- in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
+ in <a href="#events-EventTarget">EventTarget</a> relatedTargetArg);
};
</code></pre>
</dd>
@@ -2208,9 +2206,9 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-FocusEvent-relatedTarget">relatedTarget</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-FocusEvent-relatedTarget">relatedTarget</a></code> of type <a href="#events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
<dd>
- <p>Used to identify a secondary <a href="#events-Events-EventTarget"><code>EventTarget</code></a> related to a Focus event, depending on the type of event.</p>
+ <p>Used to identify a secondary <a href="#events-EventTarget"><code>EventTarget</code></a> related to a Focus event, depending on the type of event.</p>
<p class="issue" id="issue-relatedTarget-null-document"><strong>Issue:</strong> Should relatedTarget be null when it would point to an element outside the current document? See [<a href="http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0010.html">Comments from Olli Pettay</a>]
For security reasons with nested browsing contexts, when tabbing into or out of a nested context, the relevant EventTarget should be the element containing browsing context (e.g. the <code>iframe</code>), even if that element cannot normally receive focus. Should point to the
@@ -2249,8 +2247,8 @@
<dt><code class="parameter-name">detailArg</code> of type <code>long</code></dt>
<dd><p>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.</p></dd>
- <dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt>
- <dd><p>Specifies <a href="#events-Events-FocusEvent-relatedTarget"><code>FocusEvent.relatedTarget</code></a>. This value may be <code>null</code>.</p>
+ <dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-EventTarget"><code>EventTarget</code></a></dt>
+ <dd><p>Specifies <a href="#events-FocusEvent-relatedTarget"><code>FocusEvent.relatedTarget</code></a>. This value may be <code>null</code>.</p>
</dd>
</dl>
</div>
@@ -2299,7 +2297,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>blur</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2309,9 +2307,9 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> losing focus</li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2330,7 +2328,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusIn</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2340,9 +2338,9 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> receiving focus</li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2362,7 +2360,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMFocusOut</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2372,9 +2370,9 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> losing focus</li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2394,7 +2392,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>focus</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2404,9 +2402,9 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> receiving focus</li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2425,7 +2423,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>focusin</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2435,15 +2433,15 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> receiving focus</li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <a class="def" href="#glossary-event-target">event target</a> losing focus (if any).</li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <a class="def" href="#glossary-event-target">event target</a> losing focus (if any).</li>
</ul>
</td>
</tr>
</table>
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about to receive focus. This event type must be dispatched before the element is given focus. The <a class="def" href="#glossary-event-target">event target</a> must be the element which is about to receive focus. This event type is similar to <a class="eventtype" href="#event-type-focus"><code>focus</code></a>, but is dispatched before focus is shifted, and does bubble.</p>
- <p class="note" id="_9"><strong>Note:</strong> When using this event type, the author may use the event's <code class="attribute-name"><a href="#events-Events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attribute (or a host-language-specific method or means) to get the currently focused element before the focus shifts to the next focus <a class="def" href="#glossary-event-target">event target</a>, thus having optional access to both the element losing focus and the element gaining focus without the use of the <a class="eventtype" href="#event-type-blur"><code>blur</code></a> or <a class="eventtype" href="#event-type-focusout">focusout</a> event types.</p>
+ <p class="note" id="_9"><strong>Note:</strong> When using this event type, the content author may use the event's <code class="attribute-name"><a href="#events-FocusEvent-relatedTarget">FocusEvent.relatedTarget</a></code> attribute (or a host-language-specific method or means) to get the currently focused element before the focus shifts to the next focus <a class="def" href="#glossary-event-target">event target</a>, thus having optional access to both the element losing focus and the element gaining focus without the use of the <a class="eventtype" href="#event-type-blur"><code>blur</code></a> or <a class="eventtype" href="#event-type-focusout">focusout</a> event types.</p>
</dd>
</dl>
</div>
@@ -2457,7 +2455,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>focusout</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-FocusEvent"><code>FocusEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-FocusEvent"><code>FocusEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2467,9 +2465,9 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> losing focus</li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <a class="def" href="#glossary-event-target">event target</a> receiving focus.</li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a>, <code>null</code></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-FocusEvent-relatedTarget"><code class="attribute-name">FocusEvent.relatedTarget</code></a>: <a class="def" href="#glossary-event-target">event target</a> receiving focus.</li>
</ul>
</td>
</tr>
@@ -2489,11 +2487,11 @@
<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="informative" href="#references-HTML40">HTML 4.01</a></cite>] <code>onclick</code>, <code>ondblclick</code>, <code>onmousedown</code>, <code>onmouseup</code>, <code>onmouseover</code>, <code>onmousemove</code>, and <code>onmouseout</code> attributes. This event module is specifically designed for use with pointing input devices, such as a mouse or a trackball.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-MouseEvent">MouseEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="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>To create an instance of the <code>MouseEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("MouseEvent")</code></a> method call.</p>
<p class="note" id="_10"><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 class="def" href="#glossary-DOM-Level-0">DOM Level 0</a> implementations or other proprietary attributes, e.g. <code>pageX</code>).</p>
<dl>
<dt>
@@ -2503,18 +2501,18 @@
<dd>
<pre class="idl" id="idl-interface-MouseEvent"><code>
// Modified in DOM Level 3:
-interface <a href="#events-Events-MouseEvent">MouseEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
- readonly attribute long <a href="#events-Events-MouseEvent-screenX">screenX</a>;
- readonly attribute long <a href="#events-Events-MouseEvent-screenY">screenY</a>;
- readonly attribute long <a href="#events-Events-MouseEvent-clientX">clientX</a>;
- readonly attribute long <a href="#events-Events-MouseEvent-clientY">clientY</a>;
- readonly attribute boolean <a href="#events-Events-MouseEvent-ctrlKey">ctrlKey</a>;
- readonly attribute boolean <a href="#events-Events-MouseEvent-shiftKey">shiftKey</a>;
- readonly attribute boolean <a href="#events-Events-MouseEvent-altKey">altKey</a>;
- readonly attribute boolean <a href="#events-Events-MouseEvent-metaKey">metaKey</a>;
- readonly attribute unsigned short <a href="#events-Events-MouseEvent-button">button</a>;
- readonly attribute unsigned short <a href="#events-Events-MouseEvent-buttons">buttons</a>;
- readonly attribute <a href="#events-Events-EventTarget">EventTarget</a> <a href="#events-Events-MouseEvent-relatedTarget">relatedTarget</a>;
+interface <a href="#events-MouseEvent">MouseEvent</a> : <a href="#events-UIEvent">UIEvent</a> {
+ readonly attribute long <a href="#events-MouseEvent-screenX">screenX</a>;
+ readonly attribute long <a href="#events-MouseEvent-screenY">screenY</a>;
+ readonly attribute long <a href="#events-MouseEvent-clientX">clientX</a>;
+ readonly attribute long <a href="#events-MouseEvent-clientY">clientY</a>;
+ readonly attribute boolean <a href="#events-MouseEvent-ctrlKey">ctrlKey</a>;
+ readonly attribute boolean <a href="#events-MouseEvent-shiftKey">shiftKey</a>;
+ readonly attribute boolean <a href="#events-MouseEvent-altKey">altKey</a>;
+ readonly attribute boolean <a href="#events-MouseEvent-metaKey">metaKey</a>;
+ readonly attribute unsigned short <a href="#events-MouseEvent-button">button</a>;
+ readonly attribute unsigned short <a href="#events-MouseEvent-buttons">buttons</a>;
+ readonly attribute <a href="#events-EventTarget">EventTarget</a> <a href="#events-MouseEvent-relatedTarget">relatedTarget</a>;
void <a href="#events-event-type-initMouseEvent">initMouseEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
@@ -2529,9 +2527,9 @@
in boolean shiftKeyArg,
in boolean metaKeyArg,
in unsigned short buttonArg,
- in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg);
+ in <a href="#events-EventTarget">EventTarget</a> relatedTargetArg);
// Introduced in DOM Level 3:
- boolean <a href="#events-Events-MouseEvent-getModifierState">getModifierState</a>(in DOMString keyArg);
+ boolean <a href="#events-MouseEvent-getModifierState">getModifierState</a>(in DOMString keyArg);
};
</code></pre>
</dd>
@@ -2539,13 +2537,13 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-altKey">altKey</a></code> of type <code>boolean</code>, readonly</dt>
- <dd><p>Refer to the <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a> attribute.</p></dd>
-
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-button">button</a></code> of type <code>unsigned short</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MouseEvent-altKey">altKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dd><p>Refer to the <a href="#events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a> attribute.</p></dd>
+
+ <dt><code class="attribute-name"><a id="events-MouseEvent-button">button</a></code> of type <code>unsigned short</code>, readonly</dt>
<dd>
During mouse events caused by the depression or release of a mouse button, <code>button</code> shall be used to indicate which pointer device button changed state.
- <p>The value of the <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> attribute must be as follows:</p>
+ <p>The value of the <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> attribute must be as follows:</p>
<ul>
<li><code>0</code> must indicate the primary button of the device (in general, the left button or the only button on single-button devices, used to activate a user interface control or select text).</li>
<li><code>1</code> must indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).</li>
@@ -2554,9 +2552,9 @@
<p>Some pointing devices may provide or simulate more buttons, and values higher than <code>2</code> may be used to represent such buttons.</p>
</dd>
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-buttons">buttons</a></code> of type <code>unsigned short</code>, readonly</dt>
- <dd>During mouse events caused by the depression or release of a mouse button, <code>buttons</code> shall be used to indicate which combination of mouse buttons are currently being pressed, expressed as a bitmask. <span class="note" id="_11"><strong>Note:</strong> This should not be confused with the <a href="#events-Events-MouseEvent-button">button</a> attribute.</span>
- <p>The value of the <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attribute must be as follows:</p>
+ <dt><code class="attribute-name"><a id="events-MouseEvent-buttons">buttons</a></code> of type <code>unsigned short</code>, readonly</dt>
+ <dd>During mouse events caused by the depression or release of a mouse button, <code>buttons</code> shall be used to indicate which combination of mouse buttons are currently being pressed, expressed as a bitmask. <span class="note" id="_11"><strong>Note:</strong> This should not be confused with the <a href="#events-MouseEvent-button">button</a> attribute.</span>
+ <p>The value of the <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attribute must be as follows:</p>
<ul>
<li><code>0</code> must indicates no button is currently active.</li>
<li><code>1</code> must indicate the primary button of the device (in general, the left button or the only button on single-button devices, used to activate a user interface control or select text).</li>
@@ -2564,32 +2562,32 @@
<li><code>4</code> must indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).</li>
</ul>
<p>Some pointing devices may provide or simulate more buttons. To represent such buttons, the value must be doubled for each successive button (in the binary series <code>8</code>, <code>16</code>, <code>32</code>, ... ), and the buttons should alternate sides of the device, from left to right. For example, with a 5-button mouse, the primary button (on the left) would have the value <code>1</code>, the secondary button (on the right) would have the value <code>2</code>, the auxiliary button (in the middle) would have the value <code>4</code>, the fourth button (on the left) would have the value <code>8</code>, and the fifth button (on the right) would have the value <code>16</code>.</p>
- <p class="note" id="buttons-mask"><strong>Note:</strong> Because the sum of any set of button values is a unique number, an author can use a bitwise operation to determine how many buttons are currently being pressed and which buttons they are, for an arbitrary number of mouse buttons on a device, e.g. the value <code>3</code> indicates that the left and right button are currently both pressed, while the value <code>5</code> indicates that the left and middle button are currently both pressed.</p>
+ <p class="note" id="buttons-mask"><strong>Note:</strong> Because the sum of any set of button values is a unique number, a content author can use a bitwise operation to determine how many buttons are currently being pressed and which buttons they are, for an arbitrary number of mouse buttons on a device, e.g. the value <code>3</code> indicates that the left and right button are currently both pressed, while the value <code>5</code> indicates that the left and middle button are currently both pressed.</p>
</dd>
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-clientX">clientX</a></code> of type <code>long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MouseEvent-clientX">clientX</a></code> of type <code>long</code>, readonly</dt>
<dd><p>The horizontal coordinate at which the event occurred relative to the viewport associated with the event.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-clientY">clientY</a></code> of type <code>long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MouseEvent-clientY">clientY</a></code> of type <code>long</code>, readonly</dt>
<dd><p>The vertical coordinate at which the event occurred relative to the viewport associated with the event.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-ctrlKey">ctrlKey</a></code> of type <code>boolean</code>, readonly</dt>
- <dd><p>Refer to the <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a> attribute.</p></dd>
-
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-metaKey">metaKey</a></code> of type <code>boolean</code>, readonly</dt>
- <dd><p>Refer to the <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a> attribute.</p></dd>
-
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-relatedTarget">relatedTarget</a></code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
- <dd><p>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.</p></dd>
-
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-screenX">screenX</a></code> of type <code>long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MouseEvent-ctrlKey">ctrlKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dd><p>Refer to the <a href="#events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a> attribute.</p></dd>
+
+ <dt><code class="attribute-name"><a id="events-MouseEvent-metaKey">metaKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dd><p>Refer to the <a href="#events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a> attribute.</p></dd>
+
+ <dt><code class="attribute-name"><a id="events-MouseEvent-relatedTarget">relatedTarget</a></code> of type <a href="#events-EventTarget"><code>EventTarget</code></a>, readonly</dt>
+ <dd><p>Used to identify a secondary <a href="#events-EventTarget"><code>EventTarget</code></a> related to a UI event, depending on the type of event.</p></dd>
+
+ <dt><code class="attribute-name"><a id="events-MouseEvent-screenX">screenX</a></code> of type <code>long</code>, readonly</dt>
<dd><p>The horizontal coordinate at which the event occurred relative to the origin of the screen coordinate system.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-screenY">screenY</a></code> of type <code>long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MouseEvent-screenY">screenY</a></code> of type <code>long</code>, readonly</dt>
<dd><p>The vertical coordinate at which the event occurred relative to the origin of the screen coordinate system.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MouseEvent-shiftKey">shiftKey</a></code> of type <code>boolean</code>, readonly</dt>
- <dd><p>Refer to the <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a> attribute.</p></dd>
+ <dt><code class="attribute-name"><a id="events-MouseEvent-shiftKey">shiftKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dd><p>Refer to the <a href="#events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a> attribute.</p></dd>
</dl>
</dd>
@@ -2597,15 +2595,15 @@
<dt><strong>Methods</strong></dt>
<dd>
<dl>
- <dt><code class="method-name"><a id="events-Events-MouseEvent-getModifierState">getModifierState</a></code> introduced in <strong class="since">DOM Level 3</strong></dt>
+ <dt><code class="method-name"><a id="events-MouseEvent-getModifierState">getModifierState</a></code> introduced in <strong class="since">DOM Level 3</strong></dt>
<dd>
- <div class="method">Queries the state of a modifier using a key value. See also <a href="#keyset-Modifiers">Modifier keys</a>.
+ <div class="method">Queries the state of a modifier using a key value. See also <a href="#keys-Modifiers">Modifier keys</a>.
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
<dl>
<dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt>
- <dd><p>Refer to the <a href="#events-Events-KeyboardEvent-getModifierState"><code>KeyboardEvent.getModifierState()</code></a> method for a description of this parameter.</p></dd>
+ <dd><p>Refer to the <a href="#events-KeyboardEvent-getModifierState"><code>KeyboardEvent.getModifierState()</code></a> method for a description of this parameter.</p></dd>
</dl>
</div>
</div>
@@ -2645,34 +2643,34 @@
<dd><p>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">screenXArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-screenX"><code>MouseEvent.screenX</code></a>.</p></dd>
<dt><code class="parameter-name">screenYArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-screenY"><code>MouseEvent.screenY</code></a>.</p></dd>
<dt><code class="parameter-name">clientXArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-clientX"><code>MouseEvent.clientX</code></a>.</p></dd>
<dt><code class="parameter-name">clientYArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-clientY"><code>MouseEvent.clientY</code></a>.</p></dd>
<dt><code class="parameter-name">ctrlKeyArg</code> of type <code>boolean</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-ctrlKey"><code>MouseEvent.ctrlKey</code></a>.</p></dd>
<dt><code class="parameter-name">altKeyArg</code> of type <code>boolean</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-altKey"><code>MouseEvent.altKey</code></a>.</p></dd>
<dt><code class="parameter-name">shiftKeyArg</code> of type <code>boolean</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-shiftKey"><code>MouseEvent.shiftKey</code></a>.</p></dd>
<dt><code class="parameter-name">metaKeyArg</code> of type <code>boolean</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-metaKey"><code>MouseEvent.metaKey</code></a>.</p></dd>
<dt><code class="parameter-name">buttonArg</code> of type <code>unsigned short</code></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a>.</p></dd>
- <dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt>
- <dd><p>Specifies <a href="#events-Events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a>. This value may be <code>null</code>.</p></dd>
+ <dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-EventTarget"><code>EventTarget</code></a></dt>
+ <dd><p>Specifies <a href="#events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a>. This value may be <code>null</code>.</p></dd>
</dl>
</div>
</div>
@@ -2689,7 +2687,7 @@
</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 <code><a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a></code> event type might not happen if there is a long delay between the two clicks.
- <span class="note" id="_12"><strong>Note:</strong> The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> for a number of clicks greater than 2 is platform-dependent. For example, on the Windows OS, the click-count series seems to be <code>1, 2, 3, 2, 3</code>, while on MacOS, the click-count series seems to be <code>1, 2, 3, 4, 5, ...</code>.</span></p>
+ <span class="note" id="_12"><strong>Note:</strong> The value of <a href="#events-UIEvent-detail"><code>UIEvent.detail</code></a> for a number of clicks greater than 2 is platform-dependent. For example, on the Windows OS, the click-count series seems to be <code>1, 2, 3, 2, 3</code>, while on MacOS, the click-count series seems to be <code>1, 2, 3, 4, 5, ...</code>.</span></p>
<!-- click -->
<h4 class="needswork">
<a id="events-mouseevent-event-order" href="#events-mouseevent-event-order">5.2.3.2 Mouse Event Order</a>
@@ -2751,7 +2749,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>click</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2761,19 +2759,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: 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.</li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: 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.</li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2788,22 +2786,22 @@
<p>In addition to being associated with pointer devices, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type must be dispatched as part of an element activation, as described in <a href="#event-flow-activation">Activation triggers and behavior</a>.</p>
- <p class="note" id="click-activation"><strong>Note:</strong> For maximum accessibility, authors should use the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type when defining activation behavior for custom controls, rather than other pointing-device event types such as <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> or <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, which are more device-specific. Though the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type has its origins in pointer devices (e.g. a mouse), subsequent implementation enhancements have extended it beyond that association, and it should be considered a device-independent event type for element activation.</p>
+ <p class="note" id="click-activation"><strong>Note:</strong> For maximum accessibility, content authors should use the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type when defining activation behavior for custom controls, rather than other pointing-device event types such as <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> or <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, which are more device-specific. Though the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type has its origins in pointer devices (e.g. a mouse), subsequent implementation enhancements have extended it beyond that association, and it should be considered a device-independent event type for element activation.</p>
- <p>The <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type varies based on the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of the event and the value of the <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> or <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attributes. Typical <a class="def" href="#glossary-default-action">default actions</a> of the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type are as follows:</p>
+ <p>The <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type varies based on the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of the event and the value of the <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> or <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attributes. Typical <a class="def" href="#glossary-default-action">default actions</a> of the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type are as follows:</p>
<ul>
- <li><em>Left click</em> (<a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>0</code>, <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>1</code>):
+ <li><em>Left click</em> (<a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>0</code>, <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>1</code>):
<ul>
<li>If the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> has associated activation behavior, the <a class="def" href="#glossary-default-action">default action</a> shall be to execute that activation behavior (see <a href="#event-flow-activation">Activation triggers and behavior</a>).</li>
<li>If the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> is focusable, the <a class="def" href="#glossary-default-action">default action</a> shall be to give that element document focus.</li>
</ul>
</li>
- <li><em>Right click</em> (<a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>1</code>, <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>2</code>):
+ <li><em>Right click</em> (<a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>1</code>, <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>2</code>):
<ul>
<li>The <a class="def" href="#glossary-default-action">default action</a> shall be to provide a context menu of options related to that <a class="def" href="#glossary-proximal-event-target">proximal event target</a>.</li>
</ul>
</li>
- <li><em>Middle click</em> (<a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>2</code>, <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>4</code>):
+ <li><em>Middle click</em> (<a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>2</code>, <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>4</code>):
<ul>
<li>If the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> has associated activation behavior, the <a class="def" href="#glossary-default-action">default action</a> shall be to execute that activation behavior in an alternate fashion (such as opening a link in a new tab or window).</li>
<li>If the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> has no associated activation behavior, the <a class="def" href="#glossary-default-action">default action</a> shall be device- and user-defined, but when associated with a device wheel, is often to activate an alternate scrolling or panning mode.</li>
@@ -2838,7 +2836,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>dblclick</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2848,28 +2846,28 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: indicates the <a href="#events-dt-current-click-count">current click count</a></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: indicates the <a href="#events-dt-current-click-count">current click count</a></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
</table>
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a pointing device button is clicked twice over an element. The definition of a double click depends on the environment configuration, except that the event target must be the same between <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>. This event type must be dispatched after the event type <a class="eventtype" href="#event-type-click"><code>click</code></a> if a click and double click occur simultaneously, and after the event type <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> otherwise.</p>
<p class="note" id="_13"><strong>Note:</strong> Canceling the <a class="eventtype" href="#event-type-click"><code>click</code></a> event must not not affect the firing of a <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event.</p>
- <p>As with the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, the <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event type varies based on the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of the event and the value of the <a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> or <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attributes. Normally, the typical <a class="def" href="#glossary-default-action">default actions</a> of the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event type match those of the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, with the following additional behavior:</p>
+ <p>As with the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, the <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event type varies based on the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of the event and the value of the <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> or <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attributes. Normally, the typical <a class="def" href="#glossary-default-action">default actions</a> of the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> event type match those of the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type, with the following additional behavior:</p>
<ul>
- <li><em>Left click</em> (<a href="#events-Events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>0</code>, <a href="#events-Events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>1</code>):
+ <li><em>Left click</em> (<a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>0</code>, <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> value is <code>1</code>):
<ul>
<li>If the <a class="def" href="#glossary-proximal-event-target">proximal event target</a> is selectable, the <a class="def" href="#glossary-default-action">default action</a> shall be to select part or all of the selectable content; subsequent clicks may select additional selectable portions of that content.</li>
</ul>
@@ -2888,7 +2886,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mousedown</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2898,19 +2896,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one. For example, if no click happened before the mousedown, <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> must contain the value <code>1</code></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one. For example, if no click happened before the mousedown, <a href="#events-UIEvent-detail"><code>UIEvent.detail</code></a> must contain the value <code>1</code></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -2930,7 +2928,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseenter</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2940,19 +2938,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</li>
</ul>
</td>
</tr>
@@ -2972,7 +2970,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseleave</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>No</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -2982,19 +2980,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</li>
</ul>
</td>
</tr>
@@ -3014,7 +3012,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mousemove</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3024,19 +3022,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -3055,7 +3053,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseout</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3065,19 +3063,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is entering, if any.</li>
</ul>
</td>
</tr>
@@ -3098,7 +3096,7 @@
<table summary="This table contains information about the semantics of the given event type" border="0" cellpadding="2" cellspacing="0">
<tbody>
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseover</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3108,19 +3106,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> a pointing device is exiting, if any.</li>
</ul>
</td>
</tr>
@@ -3141,7 +3139,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>mouseup</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MouseEvent"><code>MouseEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3151,19 +3149,19 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one.</li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: indicates the <a href="#events-dt-current-click-count">current click count</a> incremented by one.</li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: value based on the pointer position within the viewport</li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: value based on current button pressed</li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed</li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -3179,12 +3177,12 @@
<h3><a id="events-wheelevents" href="#events-wheelevents">5.2.4 Wheel Event Types</a></h3>
<p>This module defines the feature WheelEvents 3.0 and depends on the feature MouseEvents 3.0.</p>
- <p>Wheels are devices that can be rotated in one or more spatial dimensions, and which may or may not be associated with a pointer device. The coordinate system depends on the environment configuration. As an example, the environment may be configured to associate vertical scrolling with rotation along the y-axis, horizontal scrolling with rotation along the x-axis, and zooming with rotation along the z-axis. The deltax, deltaY, and deltaX attributes of <a href="#events-Events-WheelEvent"><code>WheelEvent</code></a> objects indicate the distance of the rotation, as specified in the <a class="def" href="#glossary-delta">delta</a> definition. <!--The delta attributes of <a href='#events-Events-WheelEvent'><code>WheelEvent</code></a> objects indicate the distance of the rotation. The measurement unit depends on the environment configuration. The sign of the delta value should indicate the direction of the rotation.--></p>
+ <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-WheelEvent"><code>WheelEvent</code></a> objects indicate the distance of the rotation, as specified in the <a class="def" href="#glossary-delta">delta</a> definition. <!--The delta attributes of <a href='#events-WheelEvent'><code>WheelEvent</code></a> objects indicate the distance of the rotation. The measurement unit depends on the environment configuration. The sign of the delta value should indicate the direction of the rotation.--></p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-WheelEvent">WheelEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
+ <dt><strong>Interface <em><a id="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>
+ <p>To create an instance of the <code>WheelEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("WheelEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -3193,17 +3191,17 @@
<dd>
<pre class="idl" id="idl-interface-WheelEvent"><code>
// Introduced in DOM Level 3:
-interface <a href="#events-Events-WheelEvent">WheelEvent</a> : <a href="#events-Events-MouseEvent">MouseEvent</a> {
+interface <a href="#events-WheelEvent">WheelEvent</a> : <a href="#events-MouseEvent">MouseEvent</a> {
// DeltaModeCode
const unsigned long <a href="#events-DOM_DELTA_PIXEL">DOM_DELTA_PIXEL</a> = 0x00;
const unsigned long <a href="#events-DOM_DELTA_LINE">DOM_DELTA_LINE</a> = 0x01;
const unsigned long <a href="#events-DOM_DELTA_PAGE">DOM_DELTA_PAGE</a> = 0x02;
- readonly attribute long <a href="#events-Events-WheelEvent-deltaX">deltaX</a>;
- readonly attribute long <a href="#events-Events-WheelEvent-deltaY">deltaY</a>;
- readonly attribute long <a href="#events-Events-WheelEvent-deltaZ">deltaZ</a>;
- readonly attribute unsigned long <a href="#events-Events-WheelEvent-deltaMode">deltaMode</a>;
+ readonly attribute long <a href="#events-WheelEvent-deltaX">deltaX</a>;
+ readonly attribute long <a href="#events-WheelEvent-deltaY">deltaY</a>;
+ readonly attribute long <a href="#events-WheelEvent-deltaZ">deltaZ</a>;
+ readonly attribute unsigned long <a href="#events-WheelEvent-deltaMode">deltaMode</a>;
void <a href="#events-event-type-initWheelEvent">initWheelEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
@@ -3214,7 +3212,7 @@
in long clientXArg,
in long clientYArg,
in unsigned short buttonArg,
- in <a href="#events-Events-EventTarget">EventTarget</a> relatedTargetArg,
+ in <a href="#events-EventTarget">EventTarget</a> relatedTargetArg,
in DOMString modifiersListArg,
in long deltaXArg,
in long deltaYArg,
@@ -3250,18 +3248,18 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaX">deltaX</a></code> of type <code>long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-WheelEvent-deltaX">deltaX</a></code> of type <code>long</code>, readonly</dt>
<dd><p>The distance the wheel has rotated around the x-axis.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaY">deltaY</a></code> of type <code>long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-WheelEvent-deltaY">deltaY</a></code> of type <code>long</code>, readonly</dt>
<dd><p>The distance the wheel has rotated around the y-axis.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaZ">deltaZ</a></code> of type <code>long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-WheelEvent-deltaZ">deltaZ</a></code> of type <code>long</code>, readonly</dt>
<dd><p>The distance the wheel has rotated around the z-axis.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-WheelEvent-deltaMode">deltaMode</a></code> of type <code>unsigned long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-WheelEvent-deltaMode">deltaMode</a></code> of type <code>unsigned long</code>, readonly</dt>
<dd>
- The <code>deltaMode</code> attribute contains an indication of to indicate the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values. The default value is <a href="#events-DOM_DELTA_PIXEL"><code class="constant-name">DOM_DELTA_PIXEL</code></a> (pixels). The value of <code>deltaMode</code> may be different for each of <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaX">deltaX</a></code>, <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaY">deltaY</a></code>, and <code class="attribute-name"><a href="#events-Events-WheelEvent-deltaZ">deltaZ</a></code>, based on system configuration.<br />
+ The <code>deltaMode</code> attribute contains an indication of to indicate the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values. The default value is <a href="#events-DOM_DELTA_PIXEL"><code class="constant-name">DOM_DELTA_PIXEL</code></a> (pixels). The value of <code>deltaMode</code> may be different for each of <code class="attribute-name"><a href="#events-WheelEvent-deltaX">deltaX</a></code>, <code class="attribute-name"><a href="#events-WheelEvent-deltaY">deltaY</a></code>, and <code class="attribute-name"><a href="#events-WheelEvent-deltaZ">deltaZ</a></code>, based on system configuration.<br />
<!-- <p class="issue"><strong>Issue:</strong> deltaMode is the proposed solution for <a href="http://www.w3.org/2008/webapps/track/issues/9" title="ISSUE-9 - Web Applications Working Group Tracker">ISSUE-9</a>.</p> -->
</dd>
</dl>
@@ -3308,23 +3306,23 @@
<dt><code class="parameter-name">buttonArg</code> of type <code>unsigned short</code></dt>
<dd><p>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.</p></dd>
- <dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt>
+ <dt><code class="parameter-name">relatedTargetArg</code> of type <a href="#events-EventTarget"><code>EventTarget</code></a></dt>
<dd><p>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">modifiersListArg</code> of type <code>DOMString</code></dt>
<dd><p>Refer to the <a href="#events-event-type-initMouseEvent"><code>MouseEvent.initMouseEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">deltaXArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a>.</p></dd>
<dt><code class="parameter-name">deltaYArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a>.</p></dd>
<dt><code class="parameter-name">deltaZArg</code> of type <code>long</code></dt>
- <dd><p>Specifies <a href="#events-Events-WheelEvent-deltaZ"><code>WheelEvent.deltaZ</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-WheelEvent-deltaZ"><code>WheelEvent.deltaZ</code></a>.</p></dd>
<dt><code class="parameter-name">deltaModeArg</code> of type <code>unsigned long</code></dt>
- <dd><p>Specifies <a href="#events-Events-WheelEvent-deltaMode"><code>WheelEvent.deltaMode</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-WheelEvent-deltaMode"><code>WheelEvent.deltaMode</code></a>.</p></dd>
</dl>
</div>
</div>
@@ -3350,7 +3348,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>wheel</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-WheelEvent"><code>WheelEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-WheelEvent"><code>WheelEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Async</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>Element</code></td></tr>
@@ -3360,33 +3358,33 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: if the wheel is associated with a pointing device, the value based on the pointer position on the screen, otherwise <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: if the wheel is associated with a pointing device, the value based on the pointer position on the screen, otherwise <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: if the wheel is associated with a pointing device, the value based on the pointer position within the viewport, otherwise <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: if the wheel is associated with a pointing device, the value based on the pointer position within the viewport, otherwise <code>null</code></li>
- <li><a href="#events-Events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code> <i class="issue" id="issue-wheel-button"><strong>Issue:</strong> in use if the wheel is associated to a pointing device?</i></li>
- <li><a href="#events-Events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed <i class="issue" id="issue-wheel-buttons"><strong>Issue:</strong> in use if the wheel is associated to a pointing device?</i></li>
- <li><a href="#events-Events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> the pointing device is pointing at, if any.</li>
- <li><a href="#events-Events-WheelEvent-deltaX"><code class="attribute-name">WheelEvent.deltaX</code></a>: <code></code></li>
- <li><a href="#events-Events-WheelEvent-deltaY"><code class="attribute-name">WheelEvent.deltaY</code></a>: <code></code></li>
- <li><a href="#events-Events-WheelEvent-deltaZ"><code class="attribute-name">WheelEvent.deltaZ</code></a>: <code></code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: if the wheel is associated with a pointing device, the value based on the pointer position on the screen, otherwise <code>null</code></li>
+ <li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: if the wheel is associated with a pointing device, the value based on the pointer position on the screen, otherwise <code>null</code></li>
+ <li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: if the wheel is associated with a pointing device, the value based on the pointer position within the viewport, otherwise <code>null</code></li>
+ <li><a href="#events-MouseEvent-clientY"><code class="attribute-name">MouseEvent.clientY </code></a>: if the wheel is associated with a pointing device, the value based on the pointer position within the viewport, otherwise <code>null</code></li>
+ <li><a href="#events-MouseEvent-altKey"><code class="attribute-name">MouseEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-ctrlKey"><code class="attribute-name">MouseEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-shiftKey"><code class="attribute-name">MouseEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-metaKey"><code class="attribute-name">MouseEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-MouseEvent-button"><code class="attribute-name">MouseEvent.button</code></a>: <code>null</code> <i class="issue" id="issue-wheel-button"><strong>Issue:</strong> in use if the wheel is associated to a pointing device?</i></li>
+ <li><a href="#events-MouseEvent-buttons"><code class="attribute-name">MouseEvent.buttons</code></a>: value based on all buttons current depressed, <code>0</code> if no buttons pressed <i class="issue" id="issue-wheel-buttons"><strong>Issue:</strong> in use if the wheel is associated to a pointing device?</i></li>
+ <li><a href="#events-MouseEvent-relatedTarget"><code class="attribute-name">MouseEvent.relatedTarget</code></a>: indicates the <a class="def" href="#glossary-event-target">event target</a> the pointing device is pointing at, if any.</li>
+ <li><a href="#events-WheelEvent-deltaX"><code class="attribute-name">WheelEvent.deltaX</code></a>: <code></code></li>
+ <li><a href="#events-WheelEvent-deltaY"><code class="attribute-name">WheelEvent.deltaY</code></a>: <code></code></li>
+ <li><a href="#events-WheelEvent-deltaZ"><code class="attribute-name">WheelEvent.deltaZ</code></a>: <code></code></li>
</ul>
</td>
</tr>
</table>
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a mouse wheel has been rotated around any axis, or when an equivalent input device (such as a mouse-ball, certain tablets or touchpads, etc.) has emulated such an action.</p>
<p>The typical default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event type is to scroll (or in some cases, zoom) the document by the indicated amount. If this event is canceled, the implementation must not scroll or zoom the document (or perform whatever other implementation-specific default action is associated with this event type).</p>
- <p>Due to a lack of early standardization for a mouse-wheel event type, there are several related proprietary events which have been implemented by different <a class="def" href="#glossary-user-agent">user agents</a>, with different names and characteristics. This specification does not attempt to specify these legacy events due to lack of interoperability, but supplies the following equivalency information which may help implementers and authors. A <a class="def" href="#glossary-user-agent">user agent</a> may dispatch an event of one or more of the following event types as a <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event, depending upon the property values of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event and implementation support:</p>
+ <p>Due to a lack of early standardization for a mouse-wheel event type, there are several related proprietary events which have been implemented by different <a class="def" href="#glossary-user-agent">user agents</a>, with different names and characteristics. This specification does not attempt to specify these legacy events due to lack of interoperability, but supplies the following equivalency information which may help implementers and content authors. A <a class="def" href="#glossary-user-agent">user agent</a> may dispatch an event of one or more of the following event types as a <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event, depending upon the property values of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event and implementation support:</p>
<h5 id="mousewheel">
<strong>mousewheel</strong>
</h5>
- <p>Dispatched when <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</p>
+ <p>Dispatched when <a href="#events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</p>
<p><strong>In Microsoft Internet Explorer:</strong></p>
<p><code>mousewheel.wheelDelta = -(WheelEvent.deltaY) / 120</code></p>
<p><strong>In Opera:</strong></p>
@@ -3394,22 +3392,22 @@
<h5 id="DOMMouseScroll">
<strong>DOMMouseScroll</strong>
</h5>
- <p>Dispatched when <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</p>
+ <p>Dispatched when <a href="#events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero.</p>
<p><strong>In Mozilla Firefox:</strong></p>
<p><code>DOMMouseScroll.detail = WheelEvent.deltaY / 3</code></p>
<p><code>DOMMouseScroll.axis = VERTICAL_AXIS</code></p>
- <p>Dispatched when <a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a> is non-zero.</p>
+ <p>Dispatched when <a href="#events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a> is non-zero.</p>
<p><strong>In Mozilla Firefox:</strong></p>
<p><code>DOMMouseScroll.detail = WheelEvent.deltaX / 3</code></p>
<p><code>DOMMouseScroll.axis = HORIZONTAL_AXIS</code></p>
<h5 id="MozMousePixelScroll">
<strong>MozMousePixelScroll</strong>
</h5>
- <p>Dispatched when <a href="#events-Events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero, and <a href="#events-Events-WheelEvent-deltaMode"><code>deltaMode</code></a> is <a href="#events-DOM_DELTA_PIXEL"><code>DOM_DELTA_PIXEL</code></a>.</p>
+ <p>Dispatched when <a href="#events-WheelEvent-deltaY"><code>WheelEvent.deltaY</code></a> is non-zero, and <a href="#events-WheelEvent-deltaMode"><code>deltaMode</code></a> is <a href="#events-DOM_DELTA_PIXEL"><code>DOM_DELTA_PIXEL</code></a>.</p>
<p><strong>In Mozilla Firefox:</strong></p>
<p><code>MozMousePixelScroll.detail = WheelEvent.deltaY / 3</code></p>
<p><code>MozMousePixelScroll.axis = VERTICAL_AXIS</code></p>
- <p>Dispatched when <a href="#events-Events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a> is non-zero, and <a href="#events-Events-WheelEvent-deltaMode"><code>deltaMode</code></a> is <a href="#events-DOM_DELTA_PIXEL"><code>DOM_DELTA_PIXEL</code></a>.</p>
+ <p>Dispatched when <a href="#events-WheelEvent-deltaX"><code>WheelEvent.deltaX</code></a> is non-zero, and <a href="#events-WheelEvent-deltaMode"><code>deltaMode</code></a> is <a href="#events-DOM_DELTA_PIXEL"><code>DOM_DELTA_PIXEL</code></a>.</p>
<p><strong>In Mozilla Firefox:</strong></p>
<p><code>MozMousePixelScroll.detail = WheelEvent.deltaX / 3</code></p>
<p><code>MozMousePixelScroll.axis = HORIZONTAL_AXIS</code></p>
@@ -3425,12 +3423,12 @@
<h3><a id="events-textevents" href="#events-textevents">5.2.5 Text Event Types</a></h3>
<p>This module defines the feature TextEvents 3.0 and depends on the feature UIEvents 3.0.</p>
- <p>The text event module originates from the [<cite><a class="informative" href="#references-HTML40">HTML 4.01</a></cite>] <code>onkeypress</code> attribute. Unlike this attribute, the event type <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> applies only to characters and is designed for use with any text input devices, not just keyboards. Refer to <a href="#keyset">Keyboard events and key values</a> for examples on how text events are used in combination with keyboard events.</p>
+ <p>The text event module originates from the [<cite><a class="informative" href="#references-HTML40">HTML 4.01</a></cite>] <code>onkeypress</code> attribute. Unlike this attribute, the event type <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> applies only to characters and is designed for use with any text input devices, not just keyboards. Refer to <a href="#keys">Keyboard events and key values</a> for examples on how text events are used in combination with keyboard events.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-TextEvent">TextEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-TextEvent">TextEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
<dd>
<p>The <code>TextEvent</code> interface provides specific contextual information associated with Text Events.</p>
- <p>To create an instance of the <code>TextEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("TextEvent")</code></a> method call.</p>
+ <p>To create an instance of the <code>TextEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("TextEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -3439,7 +3437,7 @@
<dd>
<pre class="idl" id="idl-interface-TextEvent"><code>
// Introduced in DOM Level 3:
-interface <a href="#events-Events-TextEvent">TextEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
+interface <a href="#events-TextEvent">TextEvent</a> : <a href="#events-UIEvent">UIEvent</a> {
// InputModeCode
const unsigned long <a href="#events-DOM_INPUT_METHOD_UNKNOWN">DOM_INPUT_METHOD_UNKNOWN</a> = 0x00;
@@ -3453,8 +3451,8 @@
const unsigned long <a href="#events-DOM_INPUT_METHOD_MULTIMODAL">DOM_INPUT_METHOD_MULTIMODAL</a> = 0x08;
const unsigned long <a href="#events-DOM_INPUT_METHOD_SCRIPT">DOM_INPUT_METHOD_SCRIPT</a> = 0x09;
- readonly attribute DOMString <a href="#events-Events-TextEvent-data">data</a>;
- readonly attribute unsigned long <a href="#events-Events-TextEvent-inputMode">inputMode</a>;
+ readonly attribute DOMString <a href="#events-TextEvent-data">data</a>;
+ readonly attribute unsigned long <a href="#events-TextEvent-inputMode">inputMode</a>;
void <a href="#events-event-type-initTextEvent">initTextEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
@@ -3512,10 +3510,10 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-TextEvent-data">data</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-TextEvent-data">data</a></code> of type <code>DOMString</code>, readonly</dt>
<dd><p><code>data</code> holds the value of the characters generated by the character device. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class="normative" href="#references-Unicode">Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <em>NFC</em>, defined in [<cite><a class="normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute cannot be null or contain the empty string.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-TextEvent-inputMode">inputMode</a></code> of type <code>unsigned long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-TextEvent-inputMode">inputMode</a></code> of type <code>unsigned long</code>, readonly</dt>
<dd><p>The <code>inputMode</code> attribute contains an indication of the origin of the text input, as described in <a href="#events-ID-TextEvent-InputModeCode">InputModeCode</a>.</p></dd>
</dl>
@@ -3531,7 +3529,7 @@
</dt>
<dd>
<div class="method">
- <p>Initializes attributes of a <code>TextEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.</p>
+ <p>Initializes attributes of a <code>TextEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.</p>
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
@@ -3549,10 +3547,10 @@
<dd><p>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">dataArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-TextEvent-data"><code>TextEvent.data</code></a>.</p></dd>
<dt><code class="parameter-name">inputModeArg</code> of type <code>unsigned long</code></dt>
- <dd><p>Specifies <a href="#events-Events-TextEvent-inputMode"><code>TextEvent.inputMode</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-TextEvent-inputMode"><code>TextEvent.inputMode</code></a>.</p></dd>
</dl>
</div>
</div>
@@ -3579,7 +3577,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>textInput</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-TextEvent"><code>TextEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-TextEvent"><code>TextEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3589,10 +3587,10 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-TextEvent-data"><code class="attribute-name">TextEvent.data</code></a>: <code></code></li>
- <li><a href="#events-Events-TextEvent-inputMode"><code class="attribute-name">TextEvent.inputMode</code></a>: <code></code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-TextEvent-data"><code class="attribute-name">TextEvent.data</code></a>: <code></code></li>
+ <li><a href="#events-TextEvent-inputMode"><code class="attribute-name">TextEvent.inputMode</code></a>: <code></code></li>
</ul>
</td>
</tr>
@@ -3607,13 +3605,13 @@
<h3><a id="events-keyboardevents" href="#events-keyboardevents">5.2.6 Keyboard Event Types</a></h3>
<p>This module defines the feature KeyboardEvents 3.0 and depends on the feature UIEvents 3.0.</p>
- <p>Keyboard events are device dependent, i.e. they rely on the capabilities of the input devices and how they are mapped in the operating systems. It is therefore highly recommended to rely on <a href="#events-Events-TextEvent">Text event types</a> when dealing with character input. Refer to <a href="#keyset">Keyboard events and key values</a> for more details, including examples on how Keyboard Events are used in combination with Composition Events.</p>
+ <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-TextEvent">Text event types</a> when dealing with character input. Refer to <a href="#keys">Keyboard events and key values</a> for more details, including examples on how Keyboard Events are used in combination with Composition Events.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-KeyboardEvent">KeyboardEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-KeyboardEvent">KeyboardEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
<dd>
<p>The <code>KeyboardEvent</code> interface provides specific contextual information associated with keyboard devices. Each keyboard event references a key using a value. Keyboard events are commonly directed at the element that has the focus.</p>
- <p>The <code>KeyboardEvent</code> interface provides convenient attributes for some common modifiers keys: <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>. These attributes are equivalent to using the method <a href="#events-Events-KeyboardEvent-getModifierState"><code>KeyboardEvent.getModifierState(keyArg)</code></a> with <code class="value">'Control'</code>, <code class="value">'Shift'</code>, <code class="value">'Alt'</code>, or <code class="value">'Meta'</code> respectively.</p>
- <p>To create an instance of the <code>KeyboardEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("KeyboardEvent")</code></a> method call.</p>
+ <p>The <code>KeyboardEvent</code> interface provides convenient attributes for some common modifiers keys: <a href="#events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>. These attributes are equivalent to using the method <a href="#events-KeyboardEvent-getModifierState"><code>KeyboardEvent.getModifierState(keyArg)</code></a> with <code class="value">'Control'</code>, <code class="value">'Shift'</code>, <code class="value">'Alt'</code>, or <code class="value">'Meta'</code> respectively.</p>
+ <p>To create an instance of the <code>KeyboardEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("KeyboardEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -3622,7 +3620,7 @@
<dd>
<pre class="idl" id="idl-interface-KeyboardEvent"><code>
// Introduced in DOM Level 3:
-interface <a href="#events-Events-KeyboardEvent">KeyboardEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
+interface <a href="#events-KeyboardEvent">KeyboardEvent</a> : <a href="#events-UIEvent">UIEvent</a> {
// KeyLocationCode
const unsigned long <a href="#events-DOM_KEY_LOCATION_STANDARD">DOM_KEY_LOCATION_STANDARD</a> = 0x00;
@@ -3632,15 +3630,17 @@
const unsigned long <a href="#events-DOM_KEY_LOCATION_MOBILE">DOM_KEY_LOCATION_MOBILE</a> = 0x04;
const unsigned long <a href="#events-DOM_KEY_LOCATION_JOYSTICK">DOM_KEY_LOCATION_JOYSTICK</a> = 0x05;
- readonly attribute DOMString <a href="#events-Events-KeyboardEvent-key">key</a>;
- readonly attribute unsigned long <a href="#events-Events-KeyboardEvent-location">location</a>;
- readonly attribute boolean <a href="#events-Events-KeyboardEvent-ctrlKey">ctrlKey</a>;
- readonly attribute boolean <a href="#events-Events-KeyboardEvent-shiftKey">shiftKey</a>;
- readonly attribute boolean <a href="#events-Events-KeyboardEvent-altKey">altKey</a>;
- readonly attribute boolean <a href="#events-Events-KeyboardEvent-metaKey">metaKey</a>;
- readonly attribute boolean <a href="#events-Events-KeyboardEvent-repeat">repeat</a>;
- boolean <a href="#events-Events-KeyboardEvent-getModifierState">getModifierState</a>(in DOMString keyArg);
- void <a href="#events-Events-KeyboardEvent-initKeyboardEvent">initKeyboardEvent</a>(in DOMString typeArg,
+ readonly attribute DOMString <a href="#events-KeyboardEvent-char">char</a>;
+ readonly attribute DOMString <a href="#events-KeyboardEvent-key">key</a>;
+ readonly attribute DOMString <a href="#events-KeyboardEvent-keyCode">keyCode</a>;
+ readonly attribute unsigned long <a href="#events-KeyboardEvent-location">location</a>;
+ readonly attribute boolean <a href="#events-KeyboardEvent-ctrlKey">ctrlKey</a>;
+ readonly attribute boolean <a href="#events-KeyboardEvent-shiftKey">shiftKey</a>;
+ readonly attribute boolean <a href="#events-KeyboardEvent-altKey">altKey</a>;
+ readonly attribute boolean <a href="#events-KeyboardEvent-metaKey">metaKey</a>;
+ readonly attribute boolean <a href="#events-KeyboardEvent-repeat">repeat</a>;
+ boolean <a href="#events-KeyboardEvent-getModifierState">getModifierState</a>(in DOMString keyArg);
+ void <a href="#events-KeyboardEvent-initKeyboardEvent">initKeyboardEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
in views::AbstractView viewArg,
@@ -3687,28 +3687,38 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-altKey">altKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-altKey">altKey</a></code> of type <code>boolean</code>, readonly</dt>
<dd><code>true</code> if the alternative (Alt) key modifier is activated.
<p class="note" id="_25"><strong>Note:</strong> The Option key modifier on Macintosh systems must be represented using this key modifier.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-ctrlKey">ctrlKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-ctrlKey">ctrlKey</a></code> of type <code>boolean</code>, readonly</dt>
<dd><p><code>true</code> if the control (Ctrl) key modifier is activated.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-key">key</a></code> of type <code>DOMString</code>, readonly</dt>
- <dd><p><code>key</code> holds the key value of the key pressed. The key values are defined in <a href="#keyset-keyvalues">Key values set</a>. Implementations that are unable to identify a key must use the key value <code class="value">'Unidentified'</code>.</p></dd>
-
- <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-location">location</a></code> of type <code>unsigned long</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-char">char</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dd><p><code>char</code> holds the character value of the key pressed. The value must be a Unicode character string, conforming to the <a href="#key-algorithm">algorithm for determining the key value</a> defined in this specification. For a key associated with a macro to insert multiple characters, the value of the <code>char</code> attribute will hold the entire sequence of characters. For a key which does not have a character representation, the value must be <code>null</code>.</p>
+ <p class="note" id="note-char-charCode"><strong>Note:</strong> the <code>char</code> attribute is not related to the legacy <code>charCode</code> attribute and does not have the same set of values.</p>
+ </dd>
+
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-key">key</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dd><p><code>key</code> holds the key value of the key pressed. If the value is a character, it must match the value of the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute; if the value is a control key which has no printed representation, it must be one of the key values defined in the <a href="#keys-keyvalues">key values set</a>, as determined by the <a href="#key-algorithm">algorithm for determining the key value</a>. Implementations that are unable to identify a key must use the key value <code class="value">'Unidentified'</code>.</p>
+ <p class="note" id="note-key-keyCode"><strong>Note:</strong> the <code>key</code> attribute is not related to the legacy <a href="#events-KeyboardEvent-keyCode"><code>KeyboardEvent.keyCode</code></a> attribute and does not have the same set of values.</p>
+ </dd>
+
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-keyCode">keyCode</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dd><p><code>keyCode</code> holds a system- and implementation-dependent numerical code signifying the unmodified identifier associated with the key pressed. Unlike the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> or <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attributes, the set of possible values are not defined in this specification; typically, these value of the <em>keyCode</em> should represent the decimal codepoint in ASCII [<a href="#ref-rfc20">RFC20</a>][<a href="#ref-US-ASCII">US-ASCII</a>] or Windows 1252 [<a href="#ref-WIN1252">WIN1252</a>], but may be drawn from a different appropriate character set. Implementations that are unable to identify a key must use the key value <code class="value">0</code>.</p></dd>
+
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-location">location</a></code> of type <code>unsigned long</code>, readonly</dt>
<dd><p>The <code>location</code> attribute contains an indication of the location of the key on the device, as described in <a href="#events-ID-KeyboardEvent-KeyLocationCode">Keyboard event types</a>.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-metaKey">metaKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-metaKey">metaKey</a></code> of type <code>boolean</code>, readonly</dt>
<dd><code>true</code> if the meta (Meta) key modifier is activated.
<p class="note" id="_26"><strong>Note:</strong> The Command key modifier on Macintosh systems must be represented using this key modifier.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-shiftKey">shiftKey</a></code> of type <code>boolean</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-shiftKey">shiftKey</a></code> of type <code>boolean</code>, readonly</dt>
<dd><p><code>true</code> if the shift (Shift) key modifier is activated.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-KeyboardEvent-repeat">repeat</a></code> of type <code>boolean</code>, readonly</dt>
- <dd><code>true</code> if the key has been pressed in a sustained manner. Depending on the system configuration, holding down a key results may result in multiple consecutive <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> events, <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> events, and <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> events, for appropriate keys. For mobile devices which have <em>long-key-press</em> behavior, the first key event with a <a href="#events-Events-KeyboardEvent-repeat">repeat</a> attribute value of <code>'true'</code> shall serve as an indication of a <em>long-key-press</em>. The length of time that the key must be pressed in order to begin repeating is configuration-dependent.</dd>
+ <dt><code class="attribute-name"><a id="events-KeyboardEvent-repeat">repeat</a></code> of type <code>boolean</code>, readonly</dt>
+ <dd><code>true</code> if the key has been pressed in a sustained manner. Depending on the system configuration, holding down a key results may result in multiple consecutive <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> events, <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> events, and <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> events, for appropriate keys. For mobile devices which have <em>long-key-press</em> behavior, the first key event with a <a href="#events-KeyboardEvent-repeat">repeat</a> attribute value of <code>'true'</code> shall serve as an indication of a <em>long-key-press</em>. The length of time that the key must be pressed in order to begin repeating is configuration-dependent.</dd>
</dl>
</dd>
@@ -3718,12 +3728,12 @@
<dl>
<dt>
<code class="method-name">
- <a id="events-Events-KeyboardEvent-getModifierState">getModifierState</a>
+ <a id="events-KeyboardEvent-getModifierState">getModifierState</a>
</code>
</dt>
<dd>
<div class="method">
- Queries the state of a modifier using a key value. See also <a href="#keyset-Modifiers">Modifier keys</a>.
+ Queries the state of a modifier using a key value. See also <a href="#keys-Modifiers">Modifier keys</a>.
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
@@ -3742,7 +3752,7 @@
<code class="value">'Shift'</code>, and
<code class="value">'Win'</code>.
User agents may support additional implementation-specific modifier keys depending on the environment.</p>
- <p class="note" id="_27"><strong>Note:</strong> If an application wishes to distinguish between right and left modifiers, this information could be deduced using keyboard events and <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.</p>
+ <p class="note" id="_27"><strong>Note:</strong> If an application wishes to distinguish between right and left modifiers, this information could be deduced using keyboard events and <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.</p>
</dd>
</dl>
</div>
@@ -3757,12 +3767,12 @@
<dt>
<code class="method-name">
- <a id="events-Events-KeyboardEvent-initKeyboardEvent">initKeyboardEvent</a>
+ <a id="events-KeyboardEvent-initKeyboardEvent">initKeyboardEvent</a>
</code>
</dt>
<dd>
<div class="method">
- <p>Initializes attributes of a <code>KeyboardEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.</p>
+ <p>Initializes attributes of a <code>KeyboardEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.</p>
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
@@ -3780,10 +3790,10 @@
<dd><p>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">keyArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>.</p></dd>
<dt><code class="parameter-name">locationArg</code> of type <code>unsigned long</code></dt>
- <dd><p>Specifies <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>.</p></dd>
<dt><code class="parameter-name">modifiersListArg</code> of type <code>DOMString</code></dt>
<dd><p>A <a class="normative" href="http://www.w3.org/TR/2004/REC-xml-20040204/#NT-S"><em>white space</em></a> separated list of modifier key values to be activated on this object. As an example, <code>"Control Alt"</code> must mark the control and alt modifiers as activated.</p></dd>
@@ -3803,7 +3813,7 @@
</dl>
</dd>
</dl>
- <p class="warning" id="keycode-charcode"><strong>Warning!</strong> Legacy keyboard event implementations may include two additional attributes, <code>keyCode</code> and <code>charCode</code>. The <code>keyCode</code> attribute indicates a numeric value associated with a particular key on a computer keyboard, while the <code>charCode</code> attribute indicates the <acronym title="American Standard Code for Information Interchange">ASCII</acronym> value of the character associated with that key (which may or may not be the same as the <code>keyCode</code> value) and is applicable only to keys that produce a <a class="def" href="#glossary-character-value">character value</a>. In practice, <code>keyCode</code> and <code>charCode</code> are inconsistent across platforms and even the same implementation on different operating systems or using different localizations. DOM Level 3 Events does not define behavior for either <code>keyCode</code> or <code>charCode</code>; authors should use <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> instead, in conforming DOM Level 3 Events implementations. <em>For more information, see the informative table in <a href="#keyset-keyCode-charCode">Key values, keyCode, and charCode</a>.</em></p>
+ <p class="warning" id="keycode-charcode"><strong>Warning!</strong> Legacy keyboard event implementations may include two additional attributes, <code>keyCode</code> and <code>charCode</code>. The <code>keyCode</code> attribute indicates a numeric value associated with a particular key on a computer keyboard, while the <code>charCode</code> attribute indicates the <acronym title="American Standard Code for Information Interchange">ASCII</acronym> value of the character associated with that key (which may or may not be the same as the <code>keyCode</code> value) and is applicable only to keys that produce a <a class="def" href="#glossary-character-value">character value</a>. In practice, <code>keyCode</code> and <code>charCode</code> are inconsistent across platforms and even the same implementation on different operating systems or using different localizations. DOM Level 3 Events does not define values for either <code>keyCode</code> or <code>charCode</code>, or behavior for <code>charCode</code>; content authors should use <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> or <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> instead, in conforming DOM Level 3 Events implementations. <em>For more information, see the informative table in <a href="#keys-keyCode-charCode">Key values, keyCode, and charCode</a>.</em></p>
<p>Depending on the character generation device, keyboard events may or may not be generated.</p>
<p class="note" id="note-virtual-keyboards"><strong>Note:</strong> For compatibility with existing content, virtual keyboards, such as software keyboards on screen-based input devices, should produce the normal range of keyboard events, even though they do not possess physical keys.</p>
<p>The keyboard event types are listed below.</p>
@@ -3819,8 +3829,8 @@
<li>If the key is depressed for a sustained period, the following events may repeat at an environment-dependent rate:
<!-- and the key should seek counseling -->
<ul>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (with <a href="#events-Events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>)</li>
- <li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (with <a href="#events-Events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>; only for keys which produce a <a class="def" href="#glossary-character-value">character value</a>)</li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (with <a href="#events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>)</li>
+ <li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (with <a href="#events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>; only for keys which produce a <a class="def" href="#glossary-character-value">character value</a>)</li>
</ul>
</li>
<li>
@@ -3839,8 +3849,8 @@
<li>If a <a class="def" href="#glossary-character-value">character value</a> is produced, <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a></li>
<li>If the key is depressed for a sustained period,<!-- the key should seek counseling, and --> the following events may repeat at an environment-dependent rate:
<ul>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (with <a href="#events-Events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>)</li>
- <li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (with <a href="#events-Events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>; only for keys which produce a <a class="def" href="#glossary-character-value">character value</a>)</li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (with <a href="#events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>)</li>
+ <li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (with <a href="#events-KeyboardEvent-repeat">repeat</a> attribute set to <code class="value">true</code>; only for keys which produce a <a class="def" href="#glossary-character-value">character value</a>)</li>
<li>If a <a class="def" href="#glossary-character-value">character value</a> is produced, <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a></li>
</ul>
</li>
@@ -3863,7 +3873,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keydown</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3873,15 +3883,15 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-KeyboardEvent-key"><code class="attribute-name">KeyboardEvent.key</code></a>: <code></code></li>
- <li><a href="#events-Events-KeyboardEvent-location"><code class="attribute-name">KeyboardEvent.location</code></a>: <code></code></li>
- <li><a href="#events-Events-KeyboardEvent-altKey"><code class="attribute-name">KeyboardEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-shiftKey"><code class="attribute-name">KeyboardEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-ctrlKey"><code class="attribute-name">KeyboardEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-metaKey"><code class="attribute-name">KeyboardEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-repeat"><code class="attribute-name">KeyboardEvent.repeat</code></a>: <code></code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-KeyboardEvent-key"><code class="attribute-name">KeyboardEvent.key</code></a>: <code></code></li>
+ <li><a href="#events-KeyboardEvent-location"><code class="attribute-name">KeyboardEvent.location</code></a>: <code></code></li>
+ <li><a href="#events-KeyboardEvent-altKey"><code class="attribute-name">KeyboardEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-shiftKey"><code class="attribute-name">KeyboardEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-ctrlKey"><code class="attribute-name">KeyboardEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-metaKey"><code class="attribute-name">KeyboardEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-repeat"><code class="attribute-name">KeyboardEvent.repeat</code></a>: <code></code></li>
</ul>
</td>
</tr>
@@ -3889,9 +3899,9 @@
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a key is pressed down. The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This event type shall be generated after the keyboard mapping but before the processing of an <a class="def" href="#glossary-ime">input method editor</a>, normally associated with the dispatching of a <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a>, <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a>, or <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event. This event type must be dispatched before the <a class="eventtype" href="#event-type-compositionstart"><code>keypress</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events event associated with the same key. Whether or not a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> contributes to the generation of a text event is implementation dependent.</p>
<p>The default action of the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event depends upon the key:</p>
<ul>
- <li>if the key is associated with a character, the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a> attribute
+ <li>if the key is associated with a character, the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-TextEvent-data"><code>TextEvent.data</code></a> attribute
<ul>
- <li>if the document's currently focused element can receive text (such as a form input or an editable text block), the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-Events-TextEvent-data"><code>TextEvent.data</code></a> attribute, and the focused element as the value of the <a href="#events-event-type-target">Event.target</a> attribute, and for that character to be appended to the text content of that element</li>
+ <li>if the document's currently focused element can receive text (such as a form input or an editable text block), the default action shall be to dispatch a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event with the character as the value of the <a href="#events-TextEvent-data"><code>TextEvent.data</code></a> attribute, and the focused element as the value of the <a href="#events-event-type-target">Event.target</a> attribute, and for that character to be appended to the text content of that element</li>
</ul>
</li>
<li>if the key is associated with a <a class="def" href="#glossary-text-composition-system">text composition system</a>, the default action shall be to launch that system</li>
@@ -3914,7 +3924,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keypress</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3924,15 +3934,15 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-KeyboardEvent-key"><code class="attribute-name">KeyboardEvent.key</code></a>: <code></code></li>
- <li><a href="#events-Events-KeyboardEvent-location"><code class="attribute-name">KeyboardEvent.location</code></a>: <code></code></li>
- <li><a href="#events-Events-KeyboardEvent-altKey"><code class="attribute-name">KeyboardEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-shiftKey"><code class="attribute-name">KeyboardEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-ctrlKey"><code class="attribute-name">KeyboardEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-metaKey"><code class="attribute-name">KeyboardEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-repeat"><code class="attribute-name">KeyboardEvent.repeat</code></a>: <code></code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-KeyboardEvent-key"><code class="attribute-name">KeyboardEvent.key</code></a>: <code></code></li>
+ <li><a href="#events-KeyboardEvent-location"><code class="attribute-name">KeyboardEvent.location</code></a>: <code></code></li>
+ <li><a href="#events-KeyboardEvent-altKey"><code class="attribute-name">KeyboardEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-shiftKey"><code class="attribute-name">KeyboardEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-ctrlKey"><code class="attribute-name">KeyboardEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-metaKey"><code class="attribute-name">KeyboardEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-repeat"><code class="attribute-name">KeyboardEvent.repeat</code></a>: <code></code></li>
</ul>
</td>
</tr>
@@ -3953,7 +3963,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>keyup</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -3963,14 +3973,14 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-KeyboardEvent-key"><code class="attribute-name">KeyboardEvent.key</code></a>: <code></code></li>
- <li><a href="#events-Events-KeyboardEvent-location"><code class="attribute-name">KeyboardEvent.location</code></a>: <code></code></li>
- <li><a href="#events-Events-KeyboardEvent-altKey"><code class="attribute-name">KeyboardEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-shiftKey"><code class="attribute-name">KeyboardEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-ctrlKey"><code class="attribute-name">KeyboardEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
- <li><a href="#events-Events-KeyboardEvent-metaKey"><code class="attribute-name">KeyboardEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-KeyboardEvent-key"><code class="attribute-name">KeyboardEvent.key</code></a>: <code></code></li>
+ <li><a href="#events-KeyboardEvent-location"><code class="attribute-name">KeyboardEvent.location</code></a>: <code></code></li>
+ <li><a href="#events-KeyboardEvent-altKey"><code class="attribute-name">KeyboardEvent.altKey</code></a>: <code>true</code> if <a href="#key-Alt"><code class="value keyname">'Alt'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-shiftKey"><code class="attribute-name">KeyboardEvent.shiftKey</code></a>: <code>true</code> if <a href="#key-Shift"><code class="value keyname">'Shift'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-ctrlKey"><code class="attribute-name">KeyboardEvent.ctrlKey</code></a>: <code>true</code> if <a href="#key-Control"><code class="value keyname">'Control'</code></a> key is depressed, otherwise <code>false</code></li>
+ <li><a href="#events-KeyboardEvent-metaKey"><code class="attribute-name">KeyboardEvent.metaKey</code></a>: <code>true</code> if <a href="#key-Meta"><code class="value keyname">'Meta'</code></a> key is depressed, otherwise <code>false</code></li>
</ul>
</td>
</tr>
@@ -3986,14 +3996,14 @@
<h3><a id="events-compositionevents" href="#events-compositionevents">5.2.7 Composition Event Types</a></h3>
<p>This module defines the feature CompositionEvents 3.0 and depends on the feature UIEvents 3.0.</p>
- <p>Composition Events provide a means for inputing text in a supplementary or alternate manner than by Keyboard Events, in order to allow the use of characters that may not be commonly available on keyboard. For example, Composition events may be used to add accents to characters despite their absence from standard US keyboards, to build up logograms of many Asian languages from their base components or categories, to select word choices from a combination of key presses on a mobile device keyboard, or to convert voice commands into text using a speech recognition processor. Refer to <a href="#keyset">Keyboard events and key values</a> for examples on how Composition Events are used in combination with keyboard events.</p>
- <p>Conceptually, a composition session consists of one <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event, one or more <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> events, and one <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event, with the value of the <a href="#events-Events-CompositionEvent-data">data</a> attribute persisting between each "stage" of this event chain during each session. While a composition session is active, keyboard events should not be dispatched to the DOM (i.e., the <a class="def" href="#glossary-text-composition-system">text composition system</a> "swallows" the keyboard events), and only <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> events may be dispatched to indicate the composition process.</p>
+ <p>Composition Events provide a means for inputing text in a supplementary or alternate manner than by Keyboard Events, in order to allow the use of characters that may not be commonly available on keyboard. For example, Composition events may be used to add accents to characters despite their absence from standard US keyboards, to build up logograms of many Asian languages from their base components or categories, to select word choices from a combination of key presses on a mobile device keyboard, or to convert voice commands into text using a speech recognition processor. Refer to <a href="#keys">Keyboard events and key values</a> for examples on how Composition Events are used in combination with keyboard events.</p>
+ <p>Conceptually, a composition session consists of one <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event, one or more <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> events, and one <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event, with the value of the <a href="#events-CompositionEvent-data">data</a> attribute persisting between each "stage" of this event chain during each session. While a composition session is active, keyboard events should not be dispatched to the DOM (i.e., the <a class="def" href="#glossary-text-composition-system">text composition system</a> "swallows" the keyboard events), and only <a class="eventtype" href="#event-type-compositionupdate"><code>compositionupdate</code></a> events may be dispatched to indicate the composition process.</p>
<p>Not all <a class="def" href="#glossary-ime">IME</a> systems or devices expose the necessary data to the DOM, so the active composition string (the "Reading Window" or "candidate selection menu option") may not be available through this interface, in which case the selection may be represented by the empty string.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-CompositionEvent">CompositionEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-CompositionEvent">CompositionEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
<dd>
<p>The <code>CompositionEvent</code> interface provides specific contextual information associated with Composition Events.</p>
- <p>To create an instance of the <code>CompositionEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("CompositionEvent")</code></a> method call.</p>
+ <p>To create an instance of the <code>CompositionEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("CompositionEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -4002,8 +4012,8 @@
<dd>
<pre class="idl" id="idl-interface-CompositionEvent"><code>
// Introduced in DOM Level 3:
-interface <a href="#events-Events-CompositionEvent">CompositionEvent</a> : <a href="#events-Events-UIEvent">UIEvent</a> {
- readonly attribute DOMString <a href="#events-Events-CompositionEvent-data">data</a>;
+interface <a href="#events-CompositionEvent">CompositionEvent</a> : <a href="#events-UIEvent">UIEvent</a> {
+ readonly attribute DOMString <a href="#events-CompositionEvent-data">data</a>;
void <a href="#events-event-type-initCompositionEvent">initCompositionEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
@@ -4016,7 +4026,7 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-CompositionEvent-data">data</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-CompositionEvent-data">data</a></code> of type <code>DOMString</code>, readonly</dt>
<dd><p><code>data</code> holds the value of the characters generated by an input method. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class="normative" href="#references-Unicode">Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <em>NFC</em>, defined in [<cite><a class="normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute may be null or contain the empty string.</p></dd>
</dl>
@@ -4031,7 +4041,7 @@
</code>
</dt>
<dd>
- <div class="method">Initializes attributes of a <code>CompositionEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-Events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.
+ <div class="method">Initializes attributes of a <code>CompositionEvent</code> object. This method has the same behavior as <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>. The value of <a href="#events-UIEvent-detail"><code>UIEvent.detail</code></a> remains undefined.
<div class="parameters">
<strong>Parameters</strong>
<div class="paramtable">
@@ -4049,7 +4059,7 @@
<dd><p>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">dataArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.</p></dd>
</dl>
</div>
</div>
@@ -4101,7 +4111,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionstart</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -4111,15 +4121,15 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: <code></code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: <code></code></li>
</ul>
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> is invoked in preparation for composing a passage of text. This event type is device-dependent, and may rely upon the capabilities of the text conversion system and how it is mapped into the operating system. When a keyboard is used to feed an input method editor, this event type is generated after a <code>keydown</code> event, but speech or handwriting recognition systems may send this event type without keyboard events. Some implemenations may populate the <a href="#events-Events-CompositionEvent-data"><code>data</code></a> attribute of the <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event with the text currently selected in the document (for editing and replacement); otherwise, the value of the <a href="#events-Events-CompositionEvent-data"><code>data</code></a> attribute shall be <code>null</code>.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> is invoked in preparation for composing a passage of text. This event type is device-dependent, and may rely upon the capabilities of the text conversion system and how it is mapped into the operating system. When a keyboard is used to feed an input method editor, this event type is generated after a <code>keydown</code> event, but speech or handwriting recognition systems may send this event type without keyboard events. Some implemenations may populate the <a href="#events-CompositionEvent-data"><code>data</code></a> attribute of the <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event with the text currently selected in the document (for editing and replacement); otherwise, the value of the <a href="#events-CompositionEvent-data"><code>data</code></a> attribute shall be <code>null</code>.</p>
<p>This event is dispatched immediately before a <a class="def" href="#glossary-text-composition-system">text composition system</a> is launched. The default action of this event is to launch the appropriate <a class="def" href="#glossary-text-composition-system">text composition system</a>. If this event is canceled, the <a class="def" href="#glossary-text-composition-system">text composition system</a> must not be launched. Note that canceling the <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> <em>event type</em> is distinct from canceling the <a class="def" href="#glossary-text-composition-system">text composition system</a> session (e.g. by hitting a cancel button or closing an <a class="def" href="#glossary-ime">IME</a> window).</p>
<!-- <p>(<i class="issue" id="issue-composition_events"><strong>Issue:</strong> see <a href="http://lists.w3.org/Archives/Public/www-dom/2009JulSep/0143.html" title="Extra notes on composition events from Daniel Danilatos on 2009-08-07 (www-dom@w3.org from July to September 2009)">Extra notes on composition events</a> for more details.</i>)</p> -->
</dd>
@@ -4135,7 +4145,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionupdate</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -4145,15 +4155,15 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: <code></code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: <code></code></li>
</ul>
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> should dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> updates its active text passage with a new character, which is added to the string in <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a>. Note that some <a class="def" href="#glossary-text-composition-system">text composition systems</a> may not expose this information to the DOM, in which case this event will not fire during the composition process. If the composition session is canceled, this event will be fired immediately before the <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event, and the <a href="#events-Events-CompositionEvent-data"><code>CompositionEvent.data</code></a> attribute will be set to <code>null</code>.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> should dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> updates its active text passage with a new character, which is added to the string in <a href="#events-CompositionEvent-data"><code>CompositionEvent.data</code></a>. Note that some <a class="def" href="#glossary-text-composition-system">text composition systems</a> may not expose this information to the DOM, in which case this event will not fire during the composition process. If the composition session is canceled, this event will be fired immediately before the <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event, and the <a href="#events-CompositionEvent-data"><code>CompositionEvent.data</code></a> attribute will be set to <code>null</code>.</p>
</dd>
</dl>
</div>
@@ -4167,7 +4177,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>compositionend</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-CompositionEvent"><code>CompositionEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -4177,15 +4187,15 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
- <li><a href="#events-Events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
- <li><a href="#events-Events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: <code></code></li>
+ <li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code class="attribute-value">defaultView</code></a></li>
+ <li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>null</code></li>
+ <li><a href="#events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: <code></code></li>
</ul>
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> completes the composition of its active text passage, or cancels the composition process. If the result of the <a class="def" href="#glossary-text-composition-system">text composition system</a> is not null and does not contain the empty string, this event type will be followed by a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type with the appropriate <a href="#events-Events-TextEvent-inputMode">inputMode</a> value, such as <a href="#events-DOM_INPUT_METHOD_IME">DOM_INPUT_METHOD_IME</a>, <a href="#events-DOM_INPUT_METHOD_HANDWRITING">DOM_INPUT_METHOD_HANDWRITING</a>, <a href="#events-DOM_INPUT_METHOD_VOICE">DOM_INPUT_METHOD_VOICE</a>, or <a href="#events-DOM_INPUT_METHOD_MULTIMODAL">DOM_INPUT_METHOD_MULTIMODAL</a>.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition system</a> completes the composition of its active text passage, or cancels the composition process. If the result of the <a class="def" href="#glossary-text-composition-system">text composition system</a> is not null and does not contain the empty string, this event type will be followed by a <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type with the appropriate <a href="#events-TextEvent-inputMode">inputMode</a> value, such as <a href="#events-DOM_INPUT_METHOD_IME">DOM_INPUT_METHOD_IME</a>, <a href="#events-DOM_INPUT_METHOD_HANDWRITING">DOM_INPUT_METHOD_HANDWRITING</a>, <a href="#events-DOM_INPUT_METHOD_VOICE">DOM_INPUT_METHOD_VOICE</a>, or <a href="#events-DOM_INPUT_METHOD_MULTIMODAL">DOM_INPUT_METHOD_MULTIMODAL</a>.</p>
<p>This event is dispatched immediately after the <a class="def" href="#glossary-text-composition-system">text composition system</a> is completed (e.g. the <a class="def" href="#glossary-ime">IME</a> closed, minimized, switched out of focus, or otherwise dismissed, with the focus switched back to the <a class="def" href="#glossary-user-agent">user agent</a>). The default action of this event is to dispatch the <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event type as described above.</p>
</dd>
</dl>
@@ -4217,12 +4227,12 @@
<!-- <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 changed. 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>
- <p class="warning" id="_34"><strong>Warning!</strong> The <a href="#events-Events-MutationEvent">MutationEvent interface</a> was introduced in DOM Level 2 Events, but has not yet been completely and interoperably implemented across <a class="def" href="#glossary-user-agent">user agents</a>. 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 reference and completeness of legacy behavior, but <a class="def" href="#glossary-deprecated">deprecates</a> the use of both the <a href="#events-Events-MutationEvent"><code>MutationEvent</code></a> interface and the <a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a> interface.</p>
+ <p class="warning" id="_34"><strong>Warning!</strong> The <a href="#events-MutationEvent">MutationEvent interface</a> was introduced in DOM Level 2 Events, but has not yet been completely and interoperably implemented across <a class="def" href="#glossary-user-agent">user agents</a>. 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 reference and completeness of legacy behavior, but <a class="def" href="#glossary-deprecated">deprecates</a> the use of both the <a href="#events-MutationEvent"><code>MutationEvent</code></a> interface and the <a href="#events-MutationNameEvent"><code>MutationNameEvent</code></a> interface.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-MutationEvent">MutationEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-MutationEvent">MutationEvent</a></em></strong> (introduced in <strong class="since">DOM Level 2</strong>)</dt>
<dd>
<p>The <code>MutationEvent</code> interface provides specific contextual information associated with Mutation events.</p>
- <p>To create an instance of the <code>MutationEvent</code> interface, use the <a href="#events-Events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("MutationEvent")</code></a> method call.</p>
+ <p>To create an instance of the <code>MutationEvent</code> interface, use the <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent("MutationEvent")</code></a> method call.</p>
<dl>
<dt>
<br />
@@ -4231,18 +4241,18 @@
<dd>
<pre class="idl" id="idl-interface-MutationEvent"><code>
// Introduced in DOM Level 2:
-interface <a href="#events-Events-MutationEvent">MutationEvent</a> : <a href="#events-Events-Event">Event</a> {
+interface <a href="#events-MutationEvent">MutationEvent</a> : <a href="#events-Event">Event</a> {
// attrChangeType
const unsigned short <a href="#events-MODIFICATION">MODIFICATION</a> = 1;
const unsigned short <a href="#events-ADDITION">ADDITION</a> = 2;
const unsigned short <a href="#events-REMOVAL">REMOVAL</a> = 3;
- readonly attribute Node <a href="#events-Events-MutationEvent-relatedNode">relatedNode</a>;
- readonly attribute DOMString <a href="#events-Events-MutationEvent-prevValue">prevValue</a>;
- readonly attribute DOMString <a href="#events-Events-MutationEvent-newValue">newValue</a>;
- readonly attribute DOMString <a href="#events-Events-MutationEvent-attrName">attrName</a>;
- readonly attribute unsigned short <a href="#events-Events-MutationEvent-attrChange">attrChange</a>;
+ readonly attribute Node <a href="#events-MutationEvent-relatedNode">relatedNode</a>;
+ readonly attribute DOMString <a href="#events-MutationEvent-prevValue">prevValue</a>;
+ readonly attribute DOMString <a href="#events-MutationEvent-newValue">newValue</a>;
+ readonly attribute DOMString <a href="#events-MutationEvent-attrName">attrName</a>;
+ readonly attribute unsigned short <a href="#events-MutationEvent-attrChange">attrChange</a>;
void <a href="#events-event-type-initMutationEvent">initMutationEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
in boolean cancelableArg,
@@ -4256,7 +4266,7 @@
</dd>
<dt>
- <strong>Definition group <em><a id="events-Events-MutationEvent-attrChangeType">attrChangeType</a></em></strong>
+ <strong>Definition group <em><a id="events-MutationEvent-attrChangeType">attrChangeType</a></em></strong>
</dt>
<dd>
<p>An integer indicating in which way the <code>Attr</code> was changed.</p>
@@ -4281,19 +4291,19 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-MutationEvent-attrChange">attrChange</a></code> of type <code>unsigned short</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MutationEvent-attrChange">attrChange</a></code> of type <code>unsigned short</code>, readonly</dt>
<dd><p><code>attrChange</code> indicates the type of change which triggered the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a> event. The values can be <code>MODIFICATION</code>, <code>ADDITION</code>, or <code>REMOVAL</code>.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MutationEvent-attrName">attrName</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MutationEvent-attrName">attrName</a></code> of type <code>DOMString</code>, readonly</dt>
<dd><p><code>attrName</code> indicates the name of the changed <code>Attr</code> node in a <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a> event.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MutationEvent-newValue">newValue</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MutationEvent-newValue">newValue</a></code> of type <code>DOMString</code>, readonly</dt>
<dd><p><code>newValue</code> indicates the new value of the <code>Attr</code> node in <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a> events, and of the <code>CharacterData</code> node in <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a> events.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MutationEvent-prevValue">prevValue</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MutationEvent-prevValue">prevValue</a></code> of type <code>DOMString</code>, readonly</dt>
<dd><p><code>prevValue</code> indicates the previous value of the <code>Attr</code> node in <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a> events, and of the <code>CharacterData</code> node in <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a> events.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MutationEvent-relatedNode">relatedNode</a></code> of type <code>Node</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MutationEvent-relatedNode">relatedNode</a></code> of type <code>Node</code>, readonly</dt>
<dd><p><code>relatedNode</code> shall be used to identify a secondary node related to a mutation event. For example, if a mutation event is dispatched to a node indicating that its parent has changed, the <code>relatedNode</code> shall be the changed parent. If an event is instead dispatched to a subtree indicating a node was changed within it, the <code>relatedNode</code> shall be the changed node. In the case of the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a> event it indicates the <code>Attr</code> node which was modified, added, or removed.</p></dd>
</dl>
@@ -4324,19 +4334,19 @@
<dd><p>Refer to the <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">relatedNodeArg</code> of type <code>Node</code></dt>
- <dd><p>Specifies <a href="#events-Events-MutationEvent-relatedNode"><code>MutationEvent.relatedNode</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MutationEvent-relatedNode"><code>MutationEvent.relatedNode</code></a>.</p></dd>
<dt><code class="parameter-name">prevValueArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-MutationEvent-prevValue"><code>MutationEvent.prevValue</code></a>. This value may be null.</p></dd>
+ <dd><p>Specifies <a href="#events-MutationEvent-prevValue"><code>MutationEvent.prevValue</code></a>. This value may be null.</p></dd>
<dt><code class="parameter-name">newValueArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-MutationEvent-newValue"><code>MutationEvent.newValue</code></a>. This value may be null.</p></dd>
+ <dd><p>Specifies <a href="#events-MutationEvent-newValue"><code>MutationEvent.newValue</code></a>. This value may be null.</p></dd>
<dt><code class="parameter-name">attrNameArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-MutationEvent-attrName"><code>MutationEvent.attrName</code></a>. This value may be null.</p></dd>
+ <dd><p>Specifies <a href="#events-MutationEvent-attrName"><code>MutationEvent.attrName</code></a>. This value may be null.</p></dd>
<dt><code class="parameter-name">attrChangeArg</code> of type <code>unsigned short</code></dt>
- <dd><p>Specifies <a href="#events-Events-MutationEvent-attrChange"><code>MutationEvent.attrChange</code></a>. This value may be null.</p></dd>
+ <dd><p>Specifies <a href="#events-MutationEvent-attrChange"><code>MutationEvent.attrChange</code></a>. This value may be null.</p></dd>
</dl>
</div>
</div>
@@ -4355,183 +4365,6 @@
</dl>
<p>The mutation event types are listed below.</p>
-<!-- DOMSubtreeModified -->
- <div class="event-definition assert must">
- <dl>
- <dt id="event-type-DOMSubtreeModified"><dfn>
- <a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code></a>
- </dfn></dt>
- <dd>
- <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
- <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMSubtreeModified</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td></tr>
- <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
- <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
- <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>DocumentFragment</code>, <code>Element</code>, <code>Attr</code></td></tr>
- <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
- <tr class="assert must"><th>Default action</th><td>none</td></tr>
- <tr class="assert must"><th>Context info</th>
- <td>
- <ul>
- <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
- </ul>
- </td>
- </tr>
- </table>
-
- <p>This is a general event for notification of all changes to the document. It can be used instead of the more specific mutation and mutation name events listed below. It may be dispatched after a single modification to the document or, at the implementation's discretion, after multiple changes have occurred. The latter use should generally be used to accommodate multiple changes which occur either simultaneously or in rapid succession. The target of this event shall be the lowest common parent of the changes which have taken place. This event must be dispatched after any other events caused by the mutation(s) have occurred.</p>
- <p class="warning" id="_35"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
- </dd>
- </dl>
- </div>
-
-<!-- DOMNodeInserted -->
- <div class="event-definition assert must">
- <dl>
- <dt id="event-type-DOMNodeInserted"><dfn>
- <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a>
- </dfn></dt>
- <dd>
- <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
- <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeInserted</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td></tr>
- <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
- <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
- <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
- <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
- <tr class="assert must"><th>Default action</th><td>none</td></tr>
- <tr class="assert must"><th>Context info</th>
- <td>
- <ul>
- <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: the parent node of the node that has been inserted or, in case of <code>Attr</code> nodes, the <code>ownerElement</code> of the <code>Attr</code> node.</li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
- </ul>
- </td>
- </tr>
- </table>
-
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event type when a node other than an <code>Attr</code> node has been added as a child of another node. A <a class="def" href="#glossary-user-agent">user agent</a> may dispatch this event when an <code>Attr</code> node has been added to an <code>Element</code> node (see <a href="#DOMNodeInserted-attr">note</a> below). This event must be dispatched after the insertion has taken place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event shall be the node being inserted.</p>
- <p class="note" id="DOMNodeInserted-attr"><strong>Note:</strong> for detecting attribute insertion, the <a href="#event-type-DOMAttrModified">DOMAttrModified</a> event type should be used instead.</p>
- <p class="warning" id="_36"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
- </dd>
- </dl>
- </div>
-
-<!-- DOMNodeRemoved -->
- <div class="event-definition assert must">
- <dl>
- <dt id="event-type-DOMNodeRemoved"><dfn>
- <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a>
- </dfn></dt>
- <dd>
- <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
- <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeRemoved</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td></tr>
- <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
- <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
- <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
- <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
- <tr class="assert must"><th>Default action</th><td>none</td></tr>
- <tr class="assert must"><th>Context info</th>
- <td>
- <ul>
- <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: the parent node of the node being removed or, in case of <code>Attr</code> nodes, the <code>ownerElement</code> of the <code>Attr</code> node.</li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
- </ul>
- </td>
- </tr>
- </table>
-
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a node other than an <code>Attr</code> node is being removed from its parent node. A <a class="def" href="#glossary-user-agent">user agent</a> may dispatch this event when an <code>Attr</code> node is being removed from its <code>ownerElement</code> (see <a href="#DOMNodeRemoved-attr">note</a> below). This event must be dispatched before the removal takes place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event shall be the node being removed.</p>
- <p class="note" id="DOMNodeRemoved-attr"><strong>Note:</strong> for detecting attribute removal, the <a href="#event-type-DOMAttrModified">DOMAttrModified</a> event type should be used instead.</p>
- <p class="warning" id="_37"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
- </dd>
- </dl>
- </div>
-
-<!-- DOMNodeRemovedFromDocument -->
- <div class="event-definition assert must">
- <dl>
- <dt id="event-type-DOMNodeRemovedFromDocument"><dfn>
- <a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code></a>
- </dfn></dt>
- <dd>
- <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
- <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeRemovedFromDocument</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td></tr>
- <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
- <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
- <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
- <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
- <tr class="assert must"><th>Default action</th><td>none</td></tr>
- <tr class="assert must"><th>Context info</th>
- <td>
- <ul>
- <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
- </ul>
- </td>
- </tr>
- </table>
-
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a node is being removed from a document, either through direct removal of the node or removal of a subtree in which it is contained; <code>Attr</code> nodes are considered part of an <code>Element</code>'s subtree. This event must be dispatched before the removal takes place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event type shall be the node being removed. If the node is being directly removed, the event type <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a> must occur before this event type.</p>
- <p class="warning" id="_38"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
- </dd>
- </dl>
- </div>
-
-<!-- DOMNodeInsertedIntoDocument -->
- <div class="event-definition assert must">
- <dl>
- <dt id="event-type-DOMNodeInsertedIntoDocument"><dfn>
- <a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code></a>
- </dfn></dt>
- <dd>
- <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
- <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeInsertedIntoDocument</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td></tr>
- <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
- <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
- <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
- <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
- <tr class="assert must"><th>Default action</th><td>none</td></tr>
- <tr class="assert must"><th>Context info</th>
- <td>
- <ul>
- <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
- </ul>
- </td>
- </tr>
- </table>
-
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a node has been inserted into a document, either through direct insertion of the node or insertion of a subtree in which it is contained; <code>Attr</code> nodes are considered part of an <code>Element</code>'s subtree. This event must be dispatched after the insertion has taken place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event shall be the node being inserted. If the node is being directly inserted, the event type <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a> must occur before this event type.</p>
- <p class="warning" id="_39"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
- </dd>
- </dl>
- </div>
-
<!-- DOMAttrModified -->
<div class="event-definition assert must">
<dl>
@@ -4541,7 +4374,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMAttrModified</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -4551,16 +4384,16 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code></code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code></code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: indicates the <code>Attr</code> node that has been modified, added, or removed.</li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: if the <code>Attr</code> node has been added or modified</li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: if the <code>Attr</code> node has been removed or modified</li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code></code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code></code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: indicates the <code>Attr</code> node that has been modified, added, or removed.</li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: if the <code>Attr</code> node has been added or modified</li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: if the <code>Attr</code> node has been removed or modified</li>
</ul>
</td>
</tr>
</table>
-
+
<p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event after an <code>Attr.value</code> has been modified and after an <code>Attr</code> node has been added to or removed from an <code>Element</code>. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event shall be the <code>Element</code> node where the change occurred. It is implementation dependent whether this event type occurs when the children of the <code>Attr</code> node are changed in ways that do not affect the value of <code>Attr.value</code>.</p>
<p class="warning" id="_44"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
</dd>
@@ -4576,7 +4409,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMCharacterDataModified</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationEvent"><code>MutationEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>ProcessingInstruction</code></td></tr>
@@ -4586,11 +4419,11 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
</ul>
</td>
</tr>
@@ -4600,6 +4433,188 @@
</dd>
</dl>
</div>
+
+
+<!-- DOMNodeInserted -->
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="event-type-DOMNodeInserted"><dfn>
+ <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a>
+ </dfn></dt>
+ <dd>
+ <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+ <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeInserted</code></strong></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td></tr>
+ <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+ <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+ <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
+ <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+ <tr class="assert must"><th>Default action</th><td>none</td></tr>
+ <tr class="assert must"><th>Context info</th>
+ <td>
+ <ul>
+ <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: the parent node of the node that has been inserted or, in case of <code>Attr</code> nodes, the <code>ownerElement</code> of the <code>Attr</code> node.</li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ </ul>
+ </td>
+ </tr>
+ </table>
+
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event type when a node other than an <code>Attr</code> node has been added as a child of another node. A <a class="def" href="#glossary-user-agent">user agent</a> may dispatch this event when an <code>Attr</code> node has been added to an <code>Element</code> node (see <a href="#DOMNodeInserted-attr">note</a> below). This event must be dispatched after the insertion has taken place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event shall be the node being inserted.</p>
+ <p class="note" id="DOMNodeInserted-attr"><strong>Note:</strong> for detecting attribute insertion, the <a href="#event-type-DOMAttrModified">DOMAttrModified</a> event type should be used instead.</p>
+ <p class="warning" id="_36"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
+ </dd>
+ </dl>
+ </div>
+
+<!-- DOMNodeInsertedIntoDocument -->
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="event-type-DOMNodeInsertedIntoDocument"><dfn>
+ <a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code></a>
+ </dfn></dt>
+ <dd>
+ <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+ <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeInsertedIntoDocument</code></strong></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td></tr>
+ <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+ <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+ <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
+ <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+ <tr class="assert must"><th>Default action</th><td>none</td></tr>
+ <tr class="assert must"><th>Context info</th>
+ <td>
+ <ul>
+ <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ </ul>
+ </td>
+ </tr>
+ </table>
+
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a node has been inserted into a document, either through direct insertion of the node or insertion of a subtree in which it is contained; a <a class="def" href="#glossary-user-agent">user agent</a> may optionally treat an <code>Attr</code> node as part of an <code>Element</code>'s subtree. This event must be dispatched after the insertion has taken place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event shall be the node being inserted. If the node is being directly inserted, the event type <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a> must occur before this event type.</p>
+ <p class="warning" id="_39"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
+ </dd>
+ </dl>
+ </div>
+
+
+<!-- DOMNodeRemoved -->
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="event-type-DOMNodeRemoved"><dfn>
+ <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a>
+ </dfn></dt>
+ <dd>
+ <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+ <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeRemoved</code></strong></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td></tr>
+ <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+ <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+ <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
+ <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+ <tr class="assert must"><th>Default action</th><td>none</td></tr>
+ <tr class="assert must"><th>Context info</th>
+ <td>
+ <ul>
+ <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: the parent node of the node being removed or, in case of <code>Attr</code> nodes, the <code>ownerElement</code> of the <code>Attr</code> node.</li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ </ul>
+ </td>
+ </tr>
+ </table>
+
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a node other than an <code>Attr</code> node is being removed from its parent node. A <a class="def" href="#glossary-user-agent">user agent</a> may dispatch this event when an <code>Attr</code> node is being removed from its <code>ownerElement</code> (see <a href="#DOMNodeRemoved-attr">note</a> below). This event must be dispatched before the removal takes place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event shall be the node being removed.</p>
+ <p class="note" id="DOMNodeRemoved-attr"><strong>Note:</strong> for reliably detecting attribute removal, the <a href="#event-type-DOMAttrModified">DOMAttrModified</a> event type should be used instead.</p>
+ <p class="warning" id="_37"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
+ </dd>
+ </dl>
+ </div>
+
+<!-- DOMNodeRemovedFromDocument -->
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="event-type-DOMNodeRemovedFromDocument"><dfn>
+ <a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code></a>
+ </dfn></dt>
+ <dd>
+ <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+ <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMNodeRemovedFromDocument</code></strong></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td></tr>
+ <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+ <tr class="assert must"><th>Bubbles</th><td>No</td></tr>
+ <tr class="assert must"><th>Target</th><td><code>Element</code>, <code>Attr</code>, <code>Text</code>, <code>Comment</code>, <code>CDATASection</code>, <code>DocumentType</code>, <code>EntityReference</code>, <code>ProcessingInstruction</code></td></tr>
+ <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+ <tr class="assert must"><th>Default action</th><td>none</td></tr>
+ <tr class="assert must"><th>Context info</th>
+ <td>
+ <ul>
+ <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ </ul>
+ </td>
+ </tr>
+ </table>
+
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> must dispatch this event when a node is being removed from a document, either through direct removal of the node or removal of a subtree in which it is contained; a <a class="def" href="#glossary-user-agent">user agent</a> may optionally treat an <code>Attr</code> node as part of an <code>Element</code>'s subtree. This event must be dispatched before the removal takes place. The <a class="def" href="#glossary-proximal-event-target">proximal event target</a> of this event type shall be the node being removed. If the node is being directly removed, the event type <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a> must occur before this event type.</p>
+ <p class="note" id="DOMNodeRemoved-attr"><strong>Note:</strong> for reliably detecting attribute removal, the <a href="#event-type-DOMAttrModified">DOMAttrModified</a> event type should be used instead.</p>
+ <p class="warning" id="_38"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
+ </dd>
+ </dl>
+ </div>
+
+
+<!-- DOMSubtreeModified -->
+ <div class="event-definition assert must">
+ <dl>
+ <dt id="event-type-DOMSubtreeModified"><dfn>
+ <a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code></a>
+ </dfn></dt>
+ <dd>
+ <table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
+ <tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMSubtreeModified</code></strong></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationEvent"><code>MutationEvent</code></a></td></tr>
+ <tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
+ <tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
+ <tr class="assert must"><th>Target</th><td><a class="def" href="#glossary-defaultView"><code>defaultView</code></a>, <code>Document</code>, <code>DocumentFragment</code>, <code>Element</code>, <code>Attr</code></td></tr>
+ <tr class="assert must"><th>Cancelable</th><td>No</td></tr>
+ <tr class="assert must"><th>Default action</th><td>none</td></tr>
+ <tr class="assert must"><th>Context info</th>
+ <td>
+ <ul>
+ <li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ </ul>
+ </td>
+ </tr>
+ </table>
+
+ <p>This is a general event for notification of all changes to the document. It can be used instead of the more specific mutation and mutation name events listed below. It may be dispatched after a single modification to the document or, at the implementation's discretion, after multiple changes have occurred. The latter use should generally be used to accommodate multiple changes which occur either simultaneously or in rapid succession. The target of this event shall be the lowest common parent of the changes which have taken place. This event must be dispatched after any other events caused by the mutation(s) have occurred.</p>
+ <p class="warning" id="_35"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code></a> event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
+ </dd>
+ </dl>
+ </div>
+
</div>
<!-- div3 Events-eventgroupings-mutationevents -->
<div>
@@ -4608,7 +4623,7 @@
<p>This module defines the feature MutationNameEvents 3.0 and depends on the features MutationEvents 3.0 and Core 3.0.</p>
<p class="warning" id="_46"><strong>Warning!</strong> The <code>MutationNameEvent</code> interface, introduced in an earlier draft of this specification, derives from the <a href="#events-mutationevents"><code>MutationEvent</code></a> interface, which is deprecated in this specification. Thus, this specification describes the mutation name event types for completeness, but <a class="def" href="#glossary-deprecated">deprecates</a> their use.</p>
<dl>
- <dt><strong>Interface <em><a id="events-Events-MutationNameEvent">MutationNameEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
+ <dt><strong>Interface <em><a id="events-MutationNameEvent">MutationNameEvent</a></em></strong> (introduced in <strong class="since">DOM Level 3</strong>)</dt>
<dd>
<p>The <code>MutationNameEvent</code> interface provides specific contextual information associated with Mutation name event types.</p>
<p>To create an instance of the <code>MutationNameEvent</code> interface, use the <code>Document.createEvent("MutationNameEvent")</code> method call.</p>
@@ -4620,9 +4635,9 @@
<dd>
<pre class="idl" id="idl-interface-MutationNameEvent"><code>
// Introduced in DOM Level 3:
-interface <a href="#events-Events-MutationNameEvent">MutationNameEvent</a> : <a href="#events-Events-MutationEvent">MutationEvent</a> {
- readonly attribute DOMString <a href="#events-Events-MutationNameEvent-prevNamespaceURI">prevNamespaceURI</a>;
- readonly attribute DOMString <a href="#events-Events-MutationNameEvent-prevNodeName">prevNodeName</a>;
+interface <a href="#events-MutationNameEvent">MutationNameEvent</a> : <a href="#events-MutationEvent">MutationEvent</a> {
+ readonly attribute DOMString <a href="#events-MutationNameEvent-prevNamespaceURI">prevNamespaceURI</a>;
+ readonly attribute DOMString <a href="#events-MutationNameEvent-prevNodeName">prevNodeName</a>;
// Introduced in DOM Level 3:
void <a href="#events-event-type-initMutationNameEvent">initMutationNameEvent</a>(in DOMString typeArg,
in boolean canBubbleArg,
@@ -4637,10 +4652,10 @@
<dt><strong>Attributes</strong></dt>
<dd>
<dl>
- <dt><code class="attribute-name"><a id="events-Events-MutationNameEvent-prevNamespaceURI">prevNamespaceURI</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MutationNameEvent-prevNamespaceURI">prevNamespaceURI</a></code> of type <code>DOMString</code>, readonly</dt>
<dd><p>The previous value of the <code>relatedNode</code>'s <code>namespaceURI</code>.</p></dd>
- <dt><code class="attribute-name"><a id="events-Events-MutationNameEvent-prevNodeName">prevNodeName</a></code> of type <code>DOMString</code>, readonly</dt>
+ <dt><code class="attribute-name"><a id="events-MutationNameEvent-prevNodeName">prevNodeName</a></code> of type <code>DOMString</code>, readonly</dt>
<dd><p>The previous value of the <code>relatedNode</code>'s <code>nodeName</code>.</p></dd>
</dl>
@@ -4670,10 +4685,10 @@
<dd><p>Refer to the <a href="#events-event-type-initMutationEvent"><code>MutationEvent.initMutationEvent()</code></a> method for a description of this parameter.</p></dd>
<dt><code class="parameter-name">prevNamespaceURIArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-MutationNameEvent-prevNamespaceURI"><code>MutationNameEvent.prevNamespaceURI</code></a>. This value may be <code>null</code>.</p></dd>
+ <dd><p>Specifies <a href="#events-MutationNameEvent-prevNamespaceURI"><code>MutationNameEvent.prevNamespaceURI</code></a>. This value may be <code>null</code>.</p></dd>
<dt><code class="parameter-name">prevNodeNameArg</code> of type <code>DOMString</code></dt>
- <dd><p>Specifies <a href="#events-Events-MutationNameEvent-prevNodeName"><code>MutationNameEvent.prevNodeName</code></a>.</p></dd>
+ <dd><p>Specifies <a href="#events-MutationNameEvent-prevNodeName"><code>MutationNameEvent.prevNodeName</code></a>.</p></dd>
</dl>
</div>
</div>
@@ -4700,7 +4715,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMElementNameChanged</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationNameEvent"><code>MutationNameEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -4710,13 +4725,13 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationNameEvent-prevNamespaceURI"><code class="attribute-name">MutationNameEvent.prevNamespaceURI</code></a>: <code></code></li>
- <li><a href="#events-Events-MutationNameEvent-prevNodeName"><code class="attribute-name">MutationNameEvent.prevNodeName</code></a>: <code></code></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationNameEvent-prevNamespaceURI"><code class="attribute-name">MutationNameEvent.prevNamespaceURI</code></a>: <code></code></li>
+ <li><a href="#events-MutationNameEvent-prevNodeName"><code class="attribute-name">MutationNameEvent.prevNodeName</code></a>: <code></code></li>
</ul>
</td>
</tr>
@@ -4737,7 +4752,7 @@
<dd>
<table border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
<tr class="assert must"><th>Type</th><td class="eventname"><strong><code>DOMAttributeNameChanged</code></strong></td></tr>
- <tr class="assert must"><th>Interface</th><td><a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a></td></tr>
+ <tr class="assert must"><th>Interface</th><td><a href="#events-MutationNameEvent"><code>MutationNameEvent</code></a></td></tr>
<tr class="assert must"><th>Sync / Async</th><td>Sync</td></tr>
<tr class="assert must"><th>Bubbles</th><td>Yes</td></tr>
<tr class="assert must"><th>Target</th><td><code>Element</code></td></tr>
@@ -4747,13 +4762,13 @@
<td>
<ul>
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-event-target">event target</a> <i class="issue"><strong>Issue:</strong> define event target</i></li>
- <li><a href="#events-Events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: the renamed <code>Attr</code> node.</li>
- <li><a href="#events-Events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
- <li><a href="#events-Events-MutationNameEvent-prevNamespaceURI"><code class="attribute-name">MutationNameEvent.prevNamespaceURI</code></a>: <code></code></li>
- <li><a href="#events-Events-MutationNameEvent-prevNodeName"><code class="attribute-name">MutationNameEvent.prevNodeName</code></a>: <code></code></li>
+ <li><a href="#events-MutationEvent-attrName"><code class="attribute-name">MutationEvent.attrName</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-attrChange"><code class="attribute-name">MutationEvent.attrChange</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-relatedNode"><code class="attribute-name">MutationEvent.relatedNode</code></a>: the renamed <code>Attr</code> node.</li>
+ <li><a href="#events-MutationEvent-newValue"><code class="attribute-name">MutationEvent.newValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationEvent-prevValue"><code class="attribute-name">MutationEvent.prevValue</code></a>: <code>null</code></li>
+ <li><a href="#events-MutationNameEvent-prevNamespaceURI"><code class="attribute-name">MutationNameEvent.prevNamespaceURI</code></a>: <code></code></li>
+ <li><a href="#events-MutationNameEvent-prevNodeName"><code class="attribute-name">MutationNameEvent.prevNodeName</code></a>: <code></code></li>
</ul>
</td>
</tr>
@@ -4769,7 +4784,7 @@
</div>
<!-- div1 Events -->
<div>
- <h2><a id="keyset" href="#keyset">6. Keyboard events and key values</a></h2>
+ <h2><a id="keys" href="#keys">6. Keyboard events and key values</a></h2>
<p>This section contains necessary information regarding keyboard events:</p>
<ul>
@@ -4789,7 +4804,7 @@
<li><strong>Mechanical layout:</strong> the dimensions, size, and placement of the physical keys on the keyboard</li>
<li><strong>Functional mapping:</strong> the abstract key-value association of each key.</li>
</ul>
- <p>This specification only defines the functional mapping, in terms of <a href="#keyset-keyvalues">key values</a>, but briefly describes <a href="#key-legends">key legends</a> and <a href="#keyboard-layout">keyboard layout</a> for background.</p>
+ <p>This specification only defines the functional mapping, in terms of <a href="#keys-keyvalues">key values</a>, but briefly describes <a href="#key-legends">key legends</a> and <a href="#keyboard-layout">keyboard layout</a> for background.</p>
<h4><a id="key-legends" href="#key-legends">6.1.1 Key Legends</a></h4>
<p><em>This section is informative</em></p>
@@ -4800,14 +4815,15 @@
<p><em>This section is informative</em></p>
<p>As with the key labels, the physical layout of the keys on the keyboard does not not affect the digital key value for any given key. It is outside the scope of this specification to provide key values based on keyboard layout, particularly since there are so many possible layouts for a keyboard, and since users can change the mapping of keys in their operating system, e.g. by selecting a Dvorak key mapping.</p>
- <p>To illustrate the concept of keyboard layout mappings and its relation with keyboard events and key values, on the same keyboard (a PC/AT US keyboard), pressing the key labeled <code>Q</code> (with no modifier key activated) will produce different key values based on the mapping. With a typical US <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard layout mapping, it will produce <code class="value">'q'</code> (<code class="value">U+0071</code>, Latin Small Letter Q). If the keyboard layout mapping is switched to a French mapping, pressing the same key will produce <code class="value">'a'</code> (<code class="value">U+0041</code>, Latin Capital Letter A). If the keyboard layout mapping is switched to a Serbian (Cyrillic) mapping, pressing the same key will produce <code class="value">'љ'</code> (<code class="value">U+0459</code>, Cyrillic Small Letter LJE).</p>
- <p>However, the physical layout of the keys may be of interest to authors developing games or other applications wherein the location of the keys has an ergonomic relationship as the desired user interface controls, with little or no attention paid to the representational value of the key itself. For example, many games may use the keys <code class="value">'A'</code>, <code class="value">'S'</code>, <code class="value">'D'</code>, and <code class="value">'W'</code> for <code class="value">'left'</code>, <code class="value">'down'</code>, <code class="value">'right'</code>, and <code class="value">'up'</code> respectively. Authors should provide a means for the user to assign such controller keys to a custom setting appropriate to their keyboard configurations. Implementations may provide a means for the user to more comprehensively map the keyboard to their customized keyboard layout, but this is beyond the scope of this specification.</p>
+ <p>To illustrate the concept of keyboard layout mappings and its relation with keyboard events and key values, on the same keyboard (a PC/AT US keyboard), pressing the key labeled <code>Q</code> (with no modifier key activated) will produce different key values based on the mapping. With a typical US <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard layout mapping, it will produce the character <code class="value">'q'</code> (<code class="value">U+0071</code>, Latin Small Letter Q). If the keyboard layout mapping is switched to a French mapping, pressing the same key will produce the character <code class="value">'a'</code> (<code class="value">U+0041</code>, Latin Capital Letter A). If the keyboard layout mapping is switched to a Serbian (Cyrillic) mapping, pressing the same key will produce the character <code class="value">'љ'</code> (<code class="value">U+0459</code>, Cyrillic Small Letter LJE).</p>
+ <p>However, the physical layout of the keys may be of interest to content authors developing games or other applications in which the location of the keys has an ergonomic relationship as the desired user interface controls, with little or no attention paid to the representational value of the key itself. For example, many games may use the keys <code class="value">'A'</code>, <code class="value">'S'</code>, <code class="value">'D'</code>, and <code class="value">'W'</code> for <code class="value">'left'</code>, <code class="value">'down'</code>, <code class="value">'right'</code>, and <code class="value">'up'</code> respectively. Content authors should provide a means for the user to assign such controller keys to a custom setting appropriate to their keyboard configurations. Implementations may provide a means for the user to more comprehensively map the keyboard to their customized keyboard layout, but this is beyond the scope of this specification.</p>
<p class="note" id="_60"><strong>Note:</strong> Key values should not be confused with <em>scan codes</em>, which are the low-level hexadecimal signals produced for each key by the keyboard driver software, and which are mapped at the operating system to a <acronym title="Virtual Key">VK</acronym> ("virtual key"), which in turn may be mapped to the user-defined key configuration. Key values are a high-level abstraction of that final mapping.</p>
+
<h5><a id="keyboard-desktop" href="#keyboard-desktop">6.1.2.1 Desktop and Laptop Keyboards</a></h5>
- <p>In the case where an author wishes to rely on the mechanical layout of a desktop or laptop keyboard, this specification suggests the keyboard configuration specified in ISO/IEC 9995, parts 2 and 3 [<cite><a class="informative" href="#references-ISO-9995-2-3">ISO-9995-2/3</a></cite>], which defines a common layout for primary, secondary, and auxiliary key mappings on a typical alphanumeric keyboard, as a common layout appropriate to some international uses.</p>
- <p class="note" id="_51"><strong>Note:</strong> This keyboard layout is still, in essence, a <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard, and will not match the keyboards or configurations of many users. Authors cannot rely upon any particular configuration, and should create content in an internationalized and localizable manner.</p>
- <div class="figure" style="text-align: center">
+ <p>In the case where a content author wishes to rely on the mechanical layout of a desktop or laptop keyboard, this specification suggests the keyboard configuration specified in ISO/IEC 9995, parts 2 and 3 [<cite><a class="informative" href="#references-ISO-9995-2-3">ISO-9995-2/3</a></cite>], which defines a common layout for primary, secondary, and auxiliary key mappings on a typical alphanumeric keyboard, as a common layout appropriate to some international uses.</p>
+ <p class="note" id="_51"><strong>Note:</strong> This keyboard layout is still, in essence, a <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard, and will not match the keyboards or configurations of many users. Content authors cannot rely upon any particular configuration, and should create content in an internationalized and localizable manner.</p>
+ <div id="figure-keyboard" class="figure" style="text-align: center">
<object type="image/svg+xml" data="images/ISOIEC-9995-3-FCD-2009A.svg" width="900" height="300">
<img src="images/ISOIEC-9995-3-FCD-2009A.png" alt="A graphical depiction of an ISO standard defining layouts of computer keyboards, ISO/IEC 9995, parts 2 and 3" />
</object>
@@ -4817,9 +4833,9 @@
</div>
<h5><a id="keyboard-mobile" href="#keyboard-mobile">6.1.2.2 Mobile Keypads</a></h5>
- <p>In the case where an author wishes to rely on the mechanical layout of a mobile keypad, this specification suggests the keyboard configuration specified in ISO/IEC 9995-8:2006 [<cite><a class="informative" href="#references-ISO-9995-8">ISO-9995-8</a></cite>], which defines a numeric keypad layout and secondary assignment of Unicode characters in the range <abbr title="a-z">\u0061..\u007A</abbr> to the number keys <code>2</code> through <code>9</code>, as a common layout appropriate to some international uses.</p>
- <p class="note" id="_52"><strong>Note:</strong> This keypad layout, and in particular the distribution of letters is for English devices, and will not match the keypads or configurations of many users. Authors cannot rely upon any particular configuration, and should create content in an internationalized and localizable manner.</p>
- <div class="figure" style="text-align: center">
+ <p>In the case where a content author wishes to rely on the mechanical layout of a mobile keypad, this specification suggests the keyboard configuration specified in ISO/IEC 9995-8:2006 [<cite><a class="informative" href="#references-ISO-9995-8">ISO-9995-8</a></cite>], which defines a numeric keypad layout and secondary assignment of Unicode characters in the range <abbr title="a-z">\u0061..\u007A</abbr> to the number keys <code>2</code> through <code>9</code>, as a common layout appropriate to some international uses.</p>
+ <p class="note" id="_52"><strong>Note:</strong> This keypad layout, and in particular the distribution of letters is for English devices, and will not match the keypads or configurations of many users. Content authors cannot rely upon any particular configuration, and should create content in an internationalized and localizable manner.</p>
+ <div id="figure-numberpad" class="figure" style="text-align: center">
<object type="image/svg+xml" data="images/ISOIEC-9995-8-2006.svg" width="180" height="240">
<img src="images/ISOIEC-9995-8-2006.png" alt="A graphical depiction of an ISO standard defining layouts of numeric keypads, with distribution of letters on the keys, ISO/IEC 9995-8:2006" />
</object>
@@ -4830,30 +4846,32 @@
</div>
<div>
- <h3><a id="keyset-keyvalues" href="#keyset-keyvalues">6.2 Key Values</a></h3>
-
- <p>A key value is a <code>DOMString</code> that can be used to indicate any given key on a keyboard, regardless of position or state, by the value it produces. These key values may be used as return values for keyboard events generated by the implementation, or as input values by the author to specify desired input (such as for keyboard shortcuts). This specification defines a set of common key values (called the <a href="#key-values">Key Values Set</a>), and rules for production of new key values.</p>
+ <h3><a id="keys-keyvalues" href="#keys-keyvalues">6.2 Key Values</a></h3>
+
+ <p>A key value is a <code>DOMString</code> that can be used to indicate any given key on a keyboard, regardless of position or state, by the value it produces. These key values may be used as return values for keyboard events generated by the implementation, or as input values by the content author to specify desired input (such as for keyboard shortcuts). This specification defines a set of common key values (called the <a href="#key-values">Key Values Set</a>), and rules for production of new key values.</p>
<p class="issue" id="issue-keyvalues-textInput"><strong>Issue:</strong> Add mention of textInput and it's relationship to key values, per <a href="http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0052.html">Ishida</a></p>
- <!-- It is therefore highly recommended to rely on <a href="#events-Events-TextEvent">Text event types</a> when dealing with character input. -->
+ <!-- It is therefore highly recommended to rely on <a href="#events-TextEvent">Text event types</a> when dealing with character input. -->
- <p>Key values can be used to detect the value of a key which has been pressed, using the <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute. Authors can retrieve the <a class="def" href="#glossary-character-value">character value</a> of upper- or lower-case letters, number, symbols, or other character-producing keys, and also the <a class="def" href="#glossary-key-name">key name</a> of control keys, modifier keys, function keys, or other keys that do not generate characters; these values can be used for monitoring particular input strings, for detecting and acting on modifier key input in combination with other inputs (such as a mouse), for creating virtual keyboards, or for any number of other purposes.</p>
- <p>Key values can also be used by authors in string comparisons, as values for markup attributes (such as the HTML <code>accesskey</code>) in conforming <a class="def" href="#glossary-host-language">host languages</a>, or for other related purposes. A conforming <a class="def" href="#glossary-host-language">host language</a> should allow authors to use either of the two equivalent string values for a key value: the <a class="def" href="#glossary-character-value">character value</a>, or the <a class="def" href="#glossary-key-name">key name</a>.</p>
- <p class="issue"><strong>Issue:</strong> mention that author should use case-insensitive matching to capture both "t" and "T" for hotkeys, etc.?</p>
- <p class="note" id="_53"><strong>Note:</strong> While implementations are recommended to use the most relevant value for a key independently of the platform or keyboard layout mappings, authors should not make assumption on the ability of keyboard devices to generate them. When using keyboard events and key values for shortcut-key combinations, authors should <q>consider using numbers and function keys (F4, F5, and so on) instead of letters</q> ([<cite><a class="informative" href="#references-DWW95">DWW95</a></cite>]) given that most keyboard layouts will provide keys for those.</p>
+ <p>Key values can be used to detect the value of a key which has been pressed, using the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> or <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attributes. Content authors can retrieve the <a class="def" href="#glossary-character-value">character value</a> of upper- or lower-case letters, number, symbols, or other character-producing keys, and also the <a class="def" href="#glossary-key-value">key value</a> of control keys, modifier keys, function keys, or other keys that do not generate characters; these values can be used for monitoring particular input strings, for detecting and acting on modifier key input in combination with other inputs (such as a mouse), for creating virtual keyboards, or for any number of other purposes.</p>
+ <p>Key values can also be used by content authors in string comparisons, as values for markup attributes (such as the HTML <code>accesskey</code>) in conforming <a class="def" href="#glossary-host-language">host languages</a>, or for other related purposes. A conforming <a class="def" href="#glossary-host-language">host language</a> should allow content authors to use either of the two equivalent string values for a key value: the <a class="def" href="#glossary-character-value">character value</a>, or the <a class="def" href="#glossary-key-value">key value</a>.</p>
+ <p class="issue"><strong>Issue:</strong> mention that content author should use case-insensitive matching to capture both "t" and "T" for hotkeys, etc.?</p>
+ <p class="note" id="_53"><strong>Note:</strong> While implementations are recommended to use the most relevant value for a key independently of the platform or keyboard layout mappings, content authors should not make assumption on the ability of keyboard devices to generate them. When using keyboard events and key values for shortcut-key combinations, content authors should <q>consider using numbers and function keys (F4, F5, and so on) instead of letters</q> ([<cite><a class="informative" href="#references-DWW95">DWW95</a></cite>]) given that most keyboard layouts will provide keys for those.</p>
<!-- , and where the key used should default to the most appropriate key for the function, language, operating system, device, and other environmental factors (such as <code>ctrl+c</code> for copy operations) -->
- <p>It is important to note that a key value does not indicate a specific key on the physical keyboard, nor does it reflect the character printed on the key; a key value indicates the current value of the event with consideration to the current state of all active keys and key input modes (including shift modes and <a class="def" href="#glossary-dead-key">dead keys</a>), as reflected in the operating-system mapping of the keyboard and reported to the implementation. In other words, the key value for the key marked <code>'O'</code> on a <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard has the key value <code>'o'</code> in an unshifted state, <code>'O'</code> in a shifted state, <code>'ö'</code> in an unshifted state during a dead-key operation to add an umlaut diacritic, and <code>'Ö'</code> in a shifted state during a dead-key operation to add an umlaut diacritic. Because a user may map their keyboard to an arbitrary custom configuration, the author should not assume that a relationship exists between the shifted and unshifted states of a key and the majuscule form (uppercase or capital letters) and minuscule form (lowercase or small letters) of a character representation, but should instead use the value of the <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute. The keyboard depicted in Figure 3 illustrates one possible set of key mappings on one possible keyboard layout; many others exist, both standard and idiosyncratic.</p>
- <p>It is also important to note that there is not a one-to-one relationship between key event states and key values. A particular key value may be associated with multiple keys; for example, many standard keyboards contain more than one key with the <code class="value">'Shift'</code> key value (normally distinguished by the <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> values <a href="#events-DOM_KEY_LOCATION_LEFT"><code class="constant-name">DOM_KEY_LOCATION_LEFT</code></a> and <a href="#events-DOM_KEY_LOCATION_RIGHT"><code class="constant-name">DOM_KEY_LOCATION_RIGHT</code></a>) or <code class="value">'8'</code> key value (normally distinguished by the <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> values <a href="#events-DOM_KEY_LOCATION_STANDARD"><code class="constant-name">DOM_KEY_LOCATION_STANDARD</code></a> and <a href="#events-DOM_KEY_LOCATION_NUMPAD"><code class="constant-name">DOM_KEY_LOCATION_NUMPAD</code></a>), and user-configured custom keyboard layouts may duplicate any key value in multiple key-state scenarios (note that <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> is intended for standard keyboard layouts, and cannot always indicate a meaningful distinction).</p>
- <p>Similarly, a given key event state may have multiple key values, some of which may represent a character in one of the <a class="def" href="#glossary-Unicode-character-categories">Unicode character categories</a>: a <a class="def" href="#glossary-character-value">character value</a>; and the <a class="def" href="#glossary-key-name">key name</a>. For example, the question mark (<code>'?'</code>) key has the following key values: <code>'\u003F'</code> (the Unicode code point as an escaped character value, which is in the range of <a class="def" href="#glossary-Unicode-character-categories">Unicode character categories</a>); and <code>'QuestionMark'</code> (the name), while the horizontal tabulation (tab) key has a name (<code class="value">'Tab'</code>) and a <a class="def" href="#glossary-character-value">character value</a> (<code class="value">U+0009</code>) but no character representation. Note that not all keys will have both these values; for example, the volume mute key has only a <a class="def" href="#glossary-key-name">key name</a>, <code class="value">'VolumeMute'</code>, and no <a class="def" href="#glossary-character-value">character value</a> or character representation, since it doesn't have a corresponding <a class="def" href="#glossary-unicode-code-point">Unicode code point</a>.</p>
- <p>The value of the <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute of the <a href="#events-Events-KeyboardEvent">KeyboardEvent</a> interface event types (e.g. <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>, <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a>, and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>) must default to the <a class="def" href="#glossary-character-value">character value</a> itself; if the key value does not have a character representation, the value of the <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute must be the <a class="def" href="#glossary-key-name">key name</a>.</p>
- <p>The meaning of any given character representation is context-dependent and complex. For example, in some contexts, the asterisk (star) glyph (<code class="value">'*'</code>) represents a footnote or emphasis (when bracketing a passage of text); however, in some documents or executable programs it is equivalent to the mathematical multiplication operation, while in other documents or executable programs, that function is reserved for the multiplication symbol (<code class="value">'×'</code>, Unicode value <code class="value">U+00D7</code>) or the Latin small letter <code class="value">'x'</code> (due to the lack of a multiplication key on many keyboard and the superficial resemblance of the glyphs <code class="value">'×'</code> and <code class="value">'x'</code>). Thus, the semantic meaning or function of character representations is outside the scope of this specification.</p>
+ <p>It is important to note that a key value does not indicate a specific key on the physical keyboard, nor does it reflect the character printed on the key; a key value indicates the current value of the event with consideration to the current state of all active keys and key input modes (including shift modes and <a class="def" href="#glossary-dead-key">dead keys</a>), as reflected in the operating-system mapping of the keyboard and reported to the implementation. In other words, the key value for the key marked <code>'O'</code> on a <a class="def" href="#glossary-qwerty">QWERTY</a> keyboard has the key value <code>'o'</code> in an unshifted state, <code>'O'</code> in a shifted state, <code>'ö'</code> in an unshifted state during a dead-key operation to add an umlaut diacritic, and <code>'Ö'</code> in a shifted state during a dead-key operation to add an umlaut diacritic. Because a user may map their keyboard to an arbitrary custom configuration, the content author should not assume that a relationship exists between the shifted and unshifted states of a key and the majuscule form (uppercase or capital letters) and minuscule form (lowercase or small letters) of a character representation, but should instead use the value of the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> or <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attributes. The keyboard depicted in <a href="#figure-keyboard">Figure 3</a> illustrates one possible set of key mappings on one possible keyboard layout; many others exist, both standard and idiosyncratic.</p>
+ <p>It is also important to note that there is not a one-to-one relationship between key event states and key values. A particular key value may be associated with multiple keys; for example, many standard keyboards contain more than one key with the <code class="value">'Shift'</code> key value (normally distinguished by the <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> values <a href="#events-DOM_KEY_LOCATION_LEFT"><code class="constant-name">DOM_KEY_LOCATION_LEFT</code></a> and <a href="#events-DOM_KEY_LOCATION_RIGHT"><code class="constant-name">DOM_KEY_LOCATION_RIGHT</code></a>) or <code class="value">'8'</code> key value (normally distinguished by the <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> values <a href="#events-DOM_KEY_LOCATION_STANDARD"><code class="constant-name">DOM_KEY_LOCATION_STANDARD</code></a> and <a href="#events-DOM_KEY_LOCATION_NUMPAD"><code class="constant-name">DOM_KEY_LOCATION_NUMPAD</code></a>), and user-configured custom keyboard layouts may duplicate any key value in multiple key-state scenarios (note that <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> is intended for standard keyboard layouts, and cannot always indicate a meaningful distinction).</p>
+
+ <p>Similarly, a given key event state may have different key values. For most keys which represent characters, such as the letter <code>'m'</code> or the question mark (<code>'?'</code>), the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> and <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attributes will be the same. However, for <em>printing control characters</em>, such as the backspace/back key, the <em>character value</em> is distinct from the <em>key value</em>, with different values for the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> and <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attributes; see the <a id="key-values" href="#key-values">Key Values Set</a> for more details. Certain keys in some states, called <em>modifier keys</em> or <em>control keys</em>, have only a <a class="def" href="#glossary-key-value">key value</a> and no <a class="def" href="#glossary-character-value">character value</a>, such as the volume mute key, which has the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute value <code class="value">'VolumeMute'</code> and the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute value <code>null</code>.</p>
+
+ <p>Finally, the meaning of any given character representation is context-dependent and complex. For example, in some contexts, the asterisk (star) glyph (<code class="value">'*'</code>) represents a footnote or emphasis (when bracketing a passage of text); however, in some documents or executable programs it is equivalent to the mathematical multiplication operation, while in other documents or executable programs, that function is reserved for the multiplication symbol (<code class="value">'×'</code>, Unicode value <code class="value">U+00D7</code>) or the Latin small letter <code class="value">'x'</code> (due to the lack of a multiplication key on many keyboard and the superficial resemblance of the glyphs <code class="value">'×'</code> and <code class="value">'x'</code>). Thus, the semantic meaning or function of character representations is outside the scope of this specification.</p>
+
<div>
- <h4><a id="keyset-unicode" href="#keyset-unicode">6.2.1 Key Values and Unicode</a></h4>
-
- <p>The <a class="def" href="#glossary-character-value">character values</a> in the <a href="#keyset-keyvalues">key values set</a> are Unicode [<a href="#references-Unicode">Unicode</a>] codepoints, and as such, have certain advantages.</p>
- <p>The most obvious advantage is that it allows the author to use the full range of internationalized language functionality available in the implementation, regardless of the limitations of the text input devices on the system. This opens up possibilities for virtual keyboards and Web-application-based <a class="def" href="#glossary-ime">input method editors</a>.</p>
- <p>Another benefit is that it allows the author to utilize the Unicode general category properties <!-- <a class="def" href="#glossary-Unicode-character-categories">Unicode character categories</a> --> programmatically.</p>
- <p>With legacy keyboard event attributes such as <code>keyCode</code> and <code>charCode</code>, authors are forced to filter key input using cryptic, platform- and implementation-specific numeric codes, with poor internationalization, such as the following pseudocode:</p>
+ <h4><a id="keys-unicode" href="#keys-unicode">6.2.1 Key Values and Unicode</a></h4>
+
+ <p>The <a class="def" href="#glossary-character-value">character values</a> described in this specification are Unicode [<a href="#references-Unicode">Unicode</a>] codepoints, and as such, have certain advantages.</p>
+ <p>The most obvious advantage is that it allows the content author to use the full range of internationalized language functionality available in the implementation, regardless of the limitations of the text input devices on the system. This opens up possibilities for virtual keyboards and Web-application-based <a class="def" href="#glossary-ime">input method editors</a>.</p>
+ <p>Another benefit is that it allows the content author to utilize the Unicode general category properties <!-- <a class="def" href="#glossary-Unicode-character-categories">Unicode character categories</a> --> programmatically.</p>
+ <p>With legacy keyboard event attributes such as <code>keyCode</code> and <code>charCode</code>, content authors are forced to filter key input using cryptic, platform- and implementation-specific numeric codes, with poor internationalization, such as the following pseudocode:</p>
<div class="example" id="example-keyCode_charCode">
<p><strong>Example:</strong></p>
<pre><code>
@@ -4874,7 +4892,7 @@
}
</code></pre>
</div>
- <p>With key values and regular expressions, however, authors can support selective and intuitive ranges for key-based input, in a cross-platform manner with advanced internationalization support, such as the following pseudocode:</p>
+ <p>With key values and regular expressions, however, content authors can support selective and intuitive ranges for key-based input, in a cross-platform manner with advanced internationalization support, such as the following pseudocode:</p>
<div class="example" id="example-regex">
<p><strong>Example:</strong></p>
<pre><code>
@@ -4893,23 +4911,23 @@
}
</code></pre>
</div>
- <p>In addition, because Unicode categorizes each assigned <a class="def" href="#glossary-unicode-code-point">code point</a> into a group of code points used by a particular human writing system, even more advanced capabilities are possible. For example, an author can match characters from a particular human script (e.g. Tibetan) using a regular expression such as <code class="example inline">\p{Tibetan}</code>, to filter out other characters, or discover if a <a class="def" href="#glossary-unicode-code-point">code point</a> is in a certain code block (range of code points), using a regular expression like <code class="example inline">\p{InCyrillic}</code>.</p>
+ <p>In addition, because Unicode categorizes each assigned <a class="def" href="#glossary-unicode-code-point">code point</a> into a group of code points used by a particular human writing system, even more advanced capabilities are possible. For example, a content author can match characters from a particular human script (e.g. Tibetan) using a regular expression such as <code class="example inline">\p{Tibetan}</code>, to filter out other characters, or discover if a <a class="def" href="#glossary-unicode-code-point">code point</a> is in a certain code block (range of code points), using a regular expression like <code class="example inline">\p{InCyrillic}</code>.</p>
<p>To facilitate this, implementations should support Unicode range detection using regular expressions, in a manner such as the Perl Compatible Regular Expressions (PCRE) [<a href="#references-pcre">PCRE</a>].</p>
</div>
<div>
- <h4><a id="keyset-Modifiers" href="#keyset-Modifiers">6.2.2 Modifier keys</a></h4>
-
- <p>Keyboard input uses modifier keys to change the normal behavior of a key. Like other keys, modifier keys generate <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events, as shown in the example below. Some modifiers are activated while the key is being pressed down or maintained pressed such as <code class="value">'Alt'</code>, <code class="value">'Control'</code>, <code class="value">'Shift'</code>, <code class="value">'AltGraph'</code>, or <code class="value">'Meta'</code>. Others modifiers are activated depending on their state such as <code class="value">'CapsLock'</code>, <code class="value">'NumLock'</code>, or <code class="value">'Scroll'</code>. Change in the state happens when the modifier key is being pressed down. The <a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a> interface provides convenient attributes for some common modifiers keys: <a href="#events-Events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-Events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-Events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-Events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>. Some operating systems simulate the <code class="value">'AltGraph'</code> modifier key with the combination of the <code>"Alt</code> and <code class="value">'Control'</code> modifier keys. Implementations are encouraged to use the <code class="value">'AltGraph'</code> modifier key.</p>
+ <h4><a id="keys-Modifiers" href="#keys-Modifiers">6.2.2 Modifier keys</a></h4>
+
+ <p>Keyboard input uses modifier keys to change the normal behavior of a key. Like other keys, modifier keys generate <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events, as shown in the example below. Some modifiers are activated while the key is being pressed down or maintained pressed such as <code class="value">'Alt'</code>, <code class="value">'Control'</code>, <code class="value">'Shift'</code>, <code class="value">'AltGraph'</code>, or <code class="value">'Meta'</code>. Others modifiers are activated depending on their state such as <code class="value">'CapsLock'</code>, <code class="value">'NumLock'</code>, or <code class="value">'Scroll'</code>. Change in the state happens when the modifier key is being pressed down. The <a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a> interface provides convenient attributes for some common modifiers keys: <a href="#events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a>, <a href="#events-KeyboardEvent-shiftKey"><code>KeyboardEvent.shiftKey</code></a>, <a href="#events-KeyboardEvent-altKey"><code>KeyboardEvent.altKey</code></a>, <a href="#events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a>. Some operating systems simulate the <code class="value">'AltGraph'</code> modifier key with the combination of the <code>"Alt</code> and <code class="value">'Control'</code> modifier keys. Implementations are encouraged to use the <code class="value">'AltGraph'</code> modifier key.</p>
<p>The following example describes a possible sequence of events associated with the generation of the Unicode character Q (Latin Capital Letter Q, <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> <code class="value">U+0051</code>) on a PC/AT US keyboard using a US mapping:</p>
<p class="issue" id="issue-keyset-Modifiers-example"><strong>Issue:</strong> Reformat example as table with "Event", "Returned value", and "Keys involved", per <a href="http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0052.html">Ishida</a>?</p>
<div class="example" id="example-keyvalue_Q">
<p><strong>Example:</strong></p>
<ol>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a>: <code class="value">'Q'</code></li>
- <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Shift'</code></li>
</ol>
</div>
@@ -4917,8 +4935,8 @@
<div class="example" id="example-keyvalue_Q_keyup">
<p><strong>Example:</strong></p>
<ol>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a>: <code class="value">'Q'</code></li>
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Shift'</code></li>
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'q'</code> (<code class="value">U+0071</code>, Latin Small Letter Q key)</li>
@@ -4938,7 +4956,7 @@
</div>
<!-- div3 Modifiers -->
<div>
- <h4><a id="keyset-DeadKeys" href="#keyset-DeadKeys">6.2.3 Dead keys</a></h4>
+ <h4><a id="keys-DeadKeys" href="#keys-DeadKeys">6.2.3 Dead keys</a></h4>
<p>Some keyboard input uses <a class="def" href="#glossary-dead-key">dead keys</a> for the input of composed character sequences. Unlike the handwriting sequence, in which users enter the base character first, keyboard input requires to enter a special state when a <a class="def" href="#glossary-dead-key">dead key</a> is pressed and emit the character(s) only when one of a limited number of "legal" base character is entered. (NOTE: the MacOS and Linux operating systems use input methods to process <a class="def" href="#glossary-dead-key">dead keys</a>.)
</p>
@@ -4952,9 +4970,10 @@
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">\u0302</code> (Combining Circumflex Accent key)</li>
<li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'ê'</code> (<code class="value">U+00EA</code>, LATIN SMALL LETTER E WITH CIRCUMFLEX)
<br />
- <i class="note" id="note-key-intercept"><strong>Note:</strong> the key value will not be <code class="value">'e'</code> (Latin Small Letter E key) under normal circumstances, because the value delivered to the user agent will already be modified by the dead key operation.</i></li>
+ <i class="note" id="note-key-intercept"><strong>Note:</strong> the key value will not be <code class="value">'e'</code> (Latin Small Letter E key) under normal circumstances, because the value delivered to the user agent will already be modified by the dead key operation.</i>
<br />
<i class="issue" id="issue-key-intercept"><strong>Issue:</strong> is this correct for the case of composition events?</i></li>
+ </li>
<li><a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a>: <code class="value">'ê'</code></li>
<li><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a>: <code class="value">'ê'</code> (<code>"inputMode"</code>: <code class="value">'DOM_INPUT_METHOD_IME'</code>)</li>
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'e'</code> (<code class="value">U+0065</code>, Latin Small Letter E key)</li>
@@ -4977,9 +4996,9 @@
</div>
<!-- div3 DeadKeys -->
<div>
- <h4><a id="keyset-IME" href="#keyset-IME">6.2.4 Input Method Editors</a></h4>
-
- <p>This specification includes a model for <a class="def" href="#glossary-ime">input method editors (IMEs)</a>, through the <a href="#events-compositionevents">CompositionEvent</a> interface and events. However, composition events and keyboard events do not necessarily map as a one-to-one relationship. As an example, receiving a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> for the "Accept" key value does not necessarily imply that the text currently selected in the <a class="def" href="#glossary-ime">IME</a> is being accepted, but indicates only that a keystroke happened, disconnected from the <a class="def" href="#glossary-ime">IME</a> Accept functionality (which would normally result in a <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event in most <a class="def" href="#glossary-ime">IME</a> systems). Keyboard events cannot be used to determine the current state of the input method editor, which should be obtained through the <a href="#events-Events-CompositionEvent-data"><code>data</code></a> attribute of the <a href="#events-compositionevents">CompositionEvent</a> interface. Additionally, <a class="def" href="#glossary-ime">IME</a> systems and devices vary in their functionality, and in which keys are used for activating that functionality, such that the <code class="value">'Convert'</code> and <code class="value">'Accept'</code> keys may be represented by other available keys.</p>
+ <h4><a id="keys-IME" href="#keys-IME">6.2.4 Input Method Editors</a></h4>
+
+ <p>This specification includes a model for <a class="def" href="#glossary-ime">input method editors (IMEs)</a>, through the <a href="#events-compositionevents">CompositionEvent</a> interface and events. However, composition events and keyboard events do not necessarily map as a one-to-one relationship. As an example, receiving a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> for the "Accept" key value does not necessarily imply that the text currently selected in the <a class="def" href="#glossary-ime">IME</a> is being accepted, but indicates only that a keystroke happened, disconnected from the <a class="def" href="#glossary-ime">IME</a> Accept functionality (which would normally result in a <a class="eventtype" href="#event-type-compositionend"><code>compositionend</code></a> event in most <a class="def" href="#glossary-ime">IME</a> systems). Keyboard events cannot be used to determine the current state of the input method editor, which should be obtained through the <a href="#events-CompositionEvent-data"><code>data</code></a> attribute of the <a href="#events-compositionevents">CompositionEvent</a> interface. Additionally, <a class="def" href="#glossary-ime">IME</a> systems and devices vary in their functionality, and in which keys are used for activating that functionality, such that the <code class="value">'Convert'</code> and <code class="value">'Accept'</code> keys may be represented by other available keys.</p>
<p>Keyboard events correspond to the events generated by the input device after the keyboard layout mapping but before the processing of the input method editor.</p>
<p>The following example describes a possible sequence of keys to generate the Unicode character 市 (Kanji character, part of CJK Unified Ideographs) using Japanese input methods. This example assumes that the input method editor is activated and in the Japanese-Romaji input mode. The keys <code class="value">'Convert'</code> and <code class="value">'Accept'</code> may be replaced by others depending on the input device in use and the configuration of the IME, e.g. it could be respectively <code class="value">U+0020</code> (Space key) and <code class="value">'Enter'</code>. <span class="note" id="_54"><strong>Note:</strong><code class="value">'詩'</code> ("poem") and <code class="value">'市'</code> ("city") are homophones, both pronounced "shi", so the user must use the <code class="value">'Convert'</code> key to select the proper option.</span></p>
<div class="example" id="example-compo">
@@ -5024,7 +5043,7 @@
</ol>
</div>
<p>NOTE: Some <a class="def" href="#glossary-ime">input method editors</a> (such as on the MacOS operating system) may set an empty string to the composition data attribute before canceling a composition.</p>
- <h5><a id="keyset-IME_keys" href="#keyset-IME_keys">6.2.4.1 Input Method Editor mode keys</a></h5>
+ <h5><a id="keys-IME_keys" href="#keys-IME_keys">6.2.4.1 Input Method Editor mode keys</a></h5>
<p>Some keys on certain devices are intended to activate <a class="def" href="#glossary-ime">input method editor</a> functionality, or to change the mode of an active <a class="def" href="#glossary-ime">input method editor</a>. Custom keys for this purpose may be defined for different devices or language modes; the keys defined in this specification for this purpose are: <code>Alphanumeric</code>, <code>CodeInput</code>, <code>FinalMode</code>, <code>HangulMode</code>, <code>HanjaMode</code>, <code>Hiragana</code>, <code>JapaneseHiragana</code>, <code>JapaneseKatakana</code>, <code>JapaneseRomaji</code>, <code>JunjaMode</code>, <code>KanaMode</code>, <code>KanjiMode</code>, <code>Katakana</code>, and <code>RomanCharacters</code>. When one of these keys is pressed, and no <a class="def" href="#glossary-ime">IME</a> is currently active, the appropriate <a class="def" href="#glossary-ime">IME</a>, shall be activated in the mode indicated by the key (if available); if an <a class="def" href="#glossary-ime">IME</a> is already active when the key is pressed, the active <a class="def" href="#glossary-ime">IME</a> may change to the indicated mode, or a different <a class="def" href="#glossary-ime">IME</a> may be launched, or the key may be ignored, on a device- and application-specific basis.</p>
<p>This specification also defines other keys which are intended for operation specifically with <a class="def" href="#glossary-ime">input method editors</a>: <code>Accept</code>, <code>AllCandidates</code>, <code>Cancel</code>, <code>Convert</code>, <code>Compose</code>, <code>FullWidth</code>, <code>HalfWidth</code>, <code>NextCandidate</code>, <code>Nonconvert</code>, and <code>PreviousCandidate</code>. The functions of these keys are not defined in this specification; refer to other resources for details on <a class="def" href="#glossary-ime">input method editor</a> functionality.</p>
@@ -5032,21 +5051,21 @@
</div>
<!-- div3 IME -->
<div>
- <h4><a id="keyset-cancelable_keys" href="#keyset-cancelable_keys">6.2.5 Default actions and cancelable keyboard events</a></h4>
+ <h4><a id="keys-cancelable_keys" href="#keys-cancelable_keys">6.2.5 Default actions and cancelable keyboard events</a></h4>
<p>Canceling the <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event must not affect its respective <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event, but it must prevent the respective <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event from being generated. The following example describes a possible sequence of keys to generate the Unicode character Q (Latin Capital Letter Q) on a PC/AT US keyboard using a US mapping:</p>
<div class="example" id="example-cancel_keys">
<p><strong>Example:</strong></p>
<ol>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li>
<em>The <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event is prevented, e.g. by invoking <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> during the dispatch of the keydown event object</em>
</li>
<li>
<em>No <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> event is generated</em>
</li>
- <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Shift'</code></li>
</ol>
</div>
@@ -5054,24 +5073,24 @@
<div class="example" id="example-cancel_mod">
<p><strong>Example:</strong></p>
<ol>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li>
<em>The <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event is prevented, e.g. by invoking <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> during the dispatch of the keydown event object</em>
</li>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a>: <code class="value">'Q'</code></li>
- <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Q'</code> (<code class="value">U+0051</code>, Latin Capital Letter Q key), <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Shift'</code></li>
</ol>
</div>
<p class="issue"><strong>Issue:</strong> does this make sense? shouldn't the shift modifier attribute be canceled? needs testing...</p>
<!-- <p>If the key is a modifier key, the keystroke must not be taken into account for the modifiers states. The following example describes a possible sequence of keys to generate the Unicode character Q (Latin Capital Letter Q) on a PC/AT US keyboard using a US mapping:</p>
<ol>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'Shift'</code>, <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><em>The <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event is prevented, e.g. by invoking <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> during the dispatch of the keydown event object</em></li>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'q'</code> (<code class="value">U+0071</code>, Latin Small Letter Q key), no <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>: <code class="value">'q'</code> (<code class="value">U+0071</code>, Latin Small Letter Q key), no <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-textInput"><code>textInput</code></a>: <code class="value">'q'</code></li>
- <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'q'</code> (<code class="value">U+0071</code>, Latin Small Letter Q key), no <code class="attribute-name"><a href="#events-Events-MouseEvent-shiftKey">shiftKey</a></code></li>
+ <li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'q'</code> (<code class="value">U+0071</code>, Latin Small Letter Q key), no <code class="attribute-name"><a href="#events-MouseEvent-shiftKey">shiftKey</a></code></li>
<li><a class="eventtype" href="#event-type-keyup"><code>keyup</code></a>: <code class="value">'Shift'</code></li>
</ol> -->
<p>If the key is part of a sequence of several keystrokes, whether it is a <a class="def" href="#glossary-dead-key">dead key</a> or it is contributing to an Input Method Editor sequence, the keystroke shall be ignored (not taken into account) only if the <a class="def" href="#glossary-default-action">default action</a> is canceled on the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event. Canceling a <a class="def" href="#glossary-dead-key">dead key</a> on a <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event has no effect on <a class="eventtype" href="#event-type-textInput"><code>textInput</code></a> events. The following example uses the keystrokes <code class="value">U+0302</code> (Combining Circumflex Accent key) and the key marked <code class="value">'e'</code> (<code class="value">U+0065</code>, Latin Small Letter E key) (on a PC/AT french keyboard using a french mapping and without any modifier activated):</p>
@@ -5092,69 +5111,103 @@
</div>
<!-- div3 cancelable_keys -->
<div>
- <h4><a id="keyset-Guide" href="#keyset-Guide">6.2.6 Guidelines for selecting and defining key values</a></h4>
+ <h4><a id="keys-Guide" href="#keys-Guide">6.2.6 Guidelines for selecting and defining key values</a></h4>
<p class="note" id="_55"><strong>Note:</strong> This section is normative.</p>
- <p>The list of key values contained in this specification is not exhaustive and input devices may have to define their own key values. Here is an algorithm to determine which key value to use:</p>
- <ol>
- <li>Consider the current function of the key (i.e., with modifiers), taking into consideration the keyboard layout mapping in use, to determine if the key is represented by the set of defined key values, if a corresponding Unicode character exists from which a key value may be derived, or if a new key value must be defined.
- <ol>
- <li>If the primary current function of the key is to generate a character, then:
- <ol>
- <li>If there exists an appropriate key value in the <a href="#keyset-keyvalues">key values set</a>, then the key value shall be a string consisting of just that character as a <a class="def" href="#glossary-character-value">character value</a>.</li>
- <li>If there is no appropriate key value in the <a href="#keyset-keyvalues">key values set</a>, and there exists an appropriate <a class="def" href="#glossary-unicode-code-point">Unicode code point</a>, then the key value shall be a string consisting of just that character as a <a class="def" href="#glossary-character-value">character value</a>.</li>
- <li>If there is no appropriate key value in the <a href="#keyset-keyvalues">key values set</a>, and no appropriate <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> exists, then... uh, are you sure this is meant to produce a character?</li>
- </ol>
- </li>
- <li>If the primary current function of the key is to serve as a function key, then:
- <ol>
- <li>If there exists an appropriate key value in the <a href="#keyset-keyvalues">key values set</a>, that the key value shall be a string consisting of that key value as a <a class="def" href="#glossary-key-name">key name</a>.</li>
- <li>If there is no appropriate key value in the <a href="#keyset-keyvalues">key values set</a>, then a key value must be devised. The key value should be as human friendly as possible and must not contain whitespace characters. The value must be composed only of characters in the ranges <abbr title="0-9">\u0030..\u0039</abbr>, <abbr title="A-Z">\u0041..\u005A</abbr>, or <abbr title="a-z">\u0061..\u007A</abbr>, and must begin with a character in the range <abbr title="A-Z">\u0041..\u005A</abbr>.</li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- <div class="example" id="example-keyvalues">
+ <p>The list of key values contained in this specification is not exhaustive, and input devices may have to define their own key values. Consider the current function of the key (i.e., with modifiers), taking into consideration the keyboard layout mapping in use, to determine if the key is represented by the set of defined key values, if a corresponding Unicode character exists from which a key value may be derived, or if a new key value must be defined. The following algorithm determines the <em>key value</em> and <em>character value</em> to use:</p>
+
+ <ol class="algo" id="key-algorithm">
+ <li>If the primary current function of the key is to generate a character, then:
+ <ol class="algo">
+ <li>If there exists an appropriate character in the <a href="#keys-keyvalues">key values set</a>, then:
+ <ol class="algo">
+ <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute must be a string consisting of the <em>key value</em> of that character; and</li>
+ <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute must be a string consisting of the <em>char value</em> of that character.</li>
+ </ol>
+ </li>
+
+ <li>If there is no appropriate key value in the <a href="#keys-keyvalues">key values set</a>, and there exists an appropriate <a class="def" href="#glossary-unicode-code-point">Unicode code point</a>, then:
+ <ol class="algo">
+ <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute must be a string consisting of the <em>char value</em> of that character; and</li>
+ <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute must be a string consisting of the <em>char value</em> of that character.</li>
+ </ol>
+ </li>
+
+ <!-- <li>If there is no appropriate key value in the <a href="#keys-keyvalues">key values set</a>, and no appropriate <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> exists, then... uh, are you sure this is meant to produce a character?</li> -->
+ </ol>
+ </li>
+ <li>If the primary current function of the key is to serve as a function key, then:
+ <ol class="algo">
+ <li>If there exists an appropriate key value in the <a href="#keys-keyvalues">key values set</a>, then:
+ <ol class="algo">
+ <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute must be a string consisting of the <em>key value</em> of that character; and</li>
+ <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute must be <code>null</code>.</li>
+ </ol>
+ </li>
+
+
+ <li>If there is no appropriate key value in the <a href="#keys-keyvalues">key values set</a>, then a key value must be devised. The key value should be as human friendly as possible and must not contain whitespace characters. The value must be composed only of characters in the ranges <abbr title="0-9">\u0030..\u0039</abbr>, <abbr title="A-Z">\u0041..\u005A</abbr>, or <abbr title="a-z">\u0061..\u007A</abbr>, and must begin with a character in the range <abbr title="A-Z">\u0041..\u005A</abbr>.</li>
+
+ </ol>
+ </li>
+ </ol>
+ <p class="note" id="change-algo-examples"><strong>To Do:</strong> Update the algorithm example to match the change in the algorithm.</p>
+
+<!-- <div class="example" id="example-keyvalues">
<p><strong>Examples:</strong></p>
<ul>
- <li>On a PC/AT US keyboard with a two-handed Dvorak keyboard mapping, the key labeled <code class="value">'Q'</code> maps to the key values <code class="value">'5'</code> (unmodified) and <code class="value">'%'</code> (shifted). The primary function of this key is to generate the character <code class="value">U+0035</code>. Since this character is in general category <abbr title="Number, Decimal Digit">Nd</abbr>, the key value for the unmodified key shall be <code class="value">'5'</code>.</li>
+ <li>On a PC/AT US keyboard with a right-handed single-hand Dvorak keyboard mapping, the key labeled <code class="value">'Q'</code> maps to the key values <code class="value">'5'</code> (unmodified) and <code class="value">'%'</code> (shifted). The primary function of this key is to generate the character <code class="value">U+0035</code>. Since this character is in general category <abbr title="Number, Decimal Digit">Nd</abbr>, the key value for the unmodified key shall be <code class="value">'5'</code>.</li>
<li>On a French PC keyboard with a standard French mapping, the primary function of the <code class="value">'^'</code> key is as a <a class="def" href="#glossary-dead-key">dead key</a> for the circumflex diacritical mark. This corresponds to the combining Unicode character <code class="value">U+0302</code>. Since this character is in general category <abbr title="Mark, Nonspacing">Mn</abbr>, the key value shall be <code class="value">U+0302</code>.</li>
<li>On a Korean PC keyboard with a standard Korean mapping, the primary function of the <code class="value">'Ha/En'</code> key is to switch between Hangul and English input. The predefined key value list has an appropriate entry for this key, <code class="value">'HangulMode'</code>, so this shall be the key value.</li>
<li>On some models of mobile devices, 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 value list, a new value may be devised, such as <code class="value">'Calendar'</code>.</li>
</ul>
</div>
+ -->
</div>
+
+
+
+
+<!--
+
+ <a href="#events-KeyboardEvent-char">char</a> attribute
+ <a href="#events-KeyboardEvent-key">key</a> attribute
+ <a href="#events-KeyboardEvent-keycode">keycode</a> attribute
+
+
+
+ -->
+
<div>
<h4><a id="key-values" href="#key-values">6.2.7 Key Values Set</a></h4>
- <p>This section defines a list of key values which implementations must support, at a minimum; implementations may support additional key values, in a manner conforming to the <a href="#keyset-Guide">guidelines for selecting and defining key values</a>. Each key value defines one or both of the following: a <a class="def" href="#glossary-character-value">character value</a> and a <a class="def" href="#glossary-key-name">key name</a>. The <a href="#events-Events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute of an event must always be the most author-friendly of these available, in the following order: <a class="def charval" href="#glossary-character-value">character value</a>, or <a class="def keyname" href="#glossary-key-name">key name</a>. Future versions of this specification may include key values not included here, which have become common since the publication of this specification.</p>
- <p>The <a class="def" href="#glossary-key-name">key names</a> defined in this specification are based on the sets of keycodes from the <code>java.awt.event.KeyEvent</code> interface of the Java Platform, Standard Edition 6 API Specification [<cite><a class="informative" href="#references-KeyEvent">KeyEvent for Java</a></cite>], and the <code>System.Windows.Forms.Keys</code> key enumeration of the Microsoft .NET Framework 4.0 Class Library [<cite><a class="informative" href="#references-Keys">Keys enumeration for .Net</a></cite>]. The <a class="def" href="#glossary-character-value">character values</a> defined in this specification are derived from the Unicode standard [<a href="#references-Unicode">Unicode</a>].</p>
- <p class="note" id="_56"><strong>Note:</strong> The key names <code class="value">'NumPad0'</code>, <code class="value">'NumPad1'</code>, <code class="value">'NumPad2'</code>, <code class="value">'NumPad3'</code>, <code class="value">'NumPad4'</code>, <code class="value">'NumPad5'</code>, <code class="value">'NumPad6'</code>, <code class="value">'NumPad7'</code>, <code class="value">'NumPad8'</code>, and <code class="value">'NumPad9'</code>, found in some keyboard enumeration sets, are not distinguished from other numerical key values in this set; an author may use the <a href="#events-Events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> attribute to discover if a key originated from the numeric keypad.</p>
+ <p>This section defines a list of key values which implementations must support, at a minimum, in addition to support for the full range of Unicode [<a href="#references-Unicode">Unicode</a>] codepoints. Implementations may support additional key values, in a manner conforming to the <a href="#keys-Guide">guidelines for selecting and defining key values</a>. Each key value defines one or both of the following: a <a class="def" href="#glossary-character-value">character value</a> and a <a class="def" href="#glossary-key-value">key value</a>. The <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute of an event must always contain one of these control key or character values (even if the value is <code>'Unidentified'</code>), and the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute must have a value if the key represents a printable character. If the key represents one of the set of printable control characters which has a Unicode character entry, such as the tab key, the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute must have the key value (e.g. <a href="#key-Tab"><code class="value keyname">'Tab'</code></a>), while the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute must have the Unicode character value equivalent (e.g. <a href="#key-U-0009"><code class="value charval">\u0009</code></a>). This affords content authors the opportunity to deal with the key as a control key or as direct input into the text stream.</p>
+ <p>The <a class="def" href="#glossary-key-value">key values</a> defined in this specification are based on the sets of keycodes from the <code>java.awt.event.KeyEvent</code> interface of the Java Platform, Standard Edition 6 API Specification [<cite><a class="informative" href="#references-KeyEvent">KeyEvent for Java</a></cite>], and the <code>System.Windows.Forms.Keys</code> key enumeration of the Microsoft .NET Framework 4.0 Class Library [<cite><a class="informative" href="#references-Keys">Keys enumeration for .Net</a></cite>]. The <a class="def" href="#glossary-character-value">character values</a> defined in this specification are derived from the Unicode standard [<a href="#references-Unicode">Unicode</a>].</p>
+ <p class="note" id="_56"><strong>Note:</strong> The key names <code class="value">'NumPad0'</code>, <code class="value">'NumPad1'</code>, <code class="value">'NumPad2'</code>, <code class="value">'NumPad3'</code>, <code class="value">'NumPad4'</code>, <code class="value">'NumPad5'</code>, <code class="value">'NumPad6'</code>, <code class="value">'NumPad7'</code>, <code class="value">'NumPad8'</code>, and <code class="value">'NumPad9'</code>, found in some keyboard enumeration sets, are not distinguished from other numerical key values in this set; a content author may use the <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> attribute to discover if a key originated from the numeric keypad.</p>
+ <p>Future versions of this specification may include key values not included here, which have become common since the publication of this specification.</p>
<!-- <p>Javascript escaped characters may have issues because they are based on UTF-16 encoding, in that it uses surrogate pairs for values outside the Basic Multilingual Plane.</p> -->
- <p>Character values for graphic characters are shown as the character itself in the list that follows. Where a character value doesn't have a graphic form, it is listed here using, for convenience, an equivalent character escape. We have adopted the JavaScript notation for escapes in this list.</p>
+ <p>In the following list, character values for printing control characters are described as a character escape, for convenience, using the JavaScript notation for escapes.</p>
- <div id="js-escape" class="issue">
- <p><strong>Issue:</strong> Javascript escaped characters may have issues:</p>
+ <div id="js-escape" class="note">
+ <p><strong>Note:</strong> There are special internationalization considerations for ECMAScript escaped characters. CharMod conformance [<cite><a class="normative" href="#references-charmod">CharMod</a></cite>] <a href="http://www.w3.org/TR/charmod/#C045">expects</a> the use of code points rather than surrogate pairs in escapes; ECMAScript escaped characters use surrogate pairs for characters outside the Basic Multilingual Plane ("\uD84E\uDDC2" for 𣧂, a Chinese character meaning "untidy"), rather than C-style fixed-length characters ("\U000239c2" for 𣧂) or delimited escapes such as Numeric Character References ("&#x239C2;"). Characters escaped in this manner:</p>
<ul>
+ <li>are based on UTF-16 encoding, in that it uses surrogate pairs for values outside the Basic Multilingual Plane</li>
+ <li>are expressed using surrogate pairs, which makes it difficult for a human to look up the value, and may require unnecessary overhead for machine processing; this can also cause problems with software written in the incorrect belief that Unicode is a 16-bit character set</li>
+ <li>are problematic for characters on supplementary planes (emoji, or Chinese characters on plane 2), some of which may be expected to be input using a keyboard</li>
<li>may not be suitable for Java or C, which use different escaping mechanisms (could be solved with a normalizing method)</li>
- <li>based on UTF-16 encoding, in that it uses surrogate pairs for values outside the Basic Multilingual Plane</li>
- <li>expressing characters using surrogate pairs makes it difficult for a human to look up the value, and requires unnecessary overhead for machine processing; can also cause problems with software written in the incorrect belief that Unicode is a 16-bit character set</li>
- <li>problematic for characters on supplementary planes (emoji, or Chinese characters on plane 2), some of which are keyable</li>
- <li>CharMod conformance [<cite><a class="normative" href="#references-charmod">CharMod</a></cite>] <a href="http://www.w3.org/TR/charmod/#C045">expects</a> the use of code points rather than surrogate pairs in escapes</li>
- <li>Javascript escaped characters use surrogate pairs for characters outside the Basic Multilingual Plane ("\uD84E\uDDC2" for 𣧂), rather than C-style fixed-length characters ("\U000239c2" for 𣧂) or delimited escapes such as Numeric Character References ("&#x239C2;"). <span class="note" id="_57"><strong>Note:</strong> 𣧂 is a Chinese character meaning "untidy".</span></li>
</ul>
</div>
<h5>Legend for the following list:</h5>
<ul>
- <li>Character values, where present, are denoted with a <code class="value charval">green background</code>, and are the first term in a set</li>
- <li>Key names are denoted with a <code class="value keyname">blue background</code>, and come after the character value</li>
- <li>Character representations are denoted with a <code class="value charrep">pale orange background</code>, and do not represent a special data type; the color is only to distinguish the representation from the surrounding text.</li>
+ <li>Key values are denoted with a <code class="value keyname">blue background</code>, and are the first term in a set</li>
+ <li>Character values, where present, are denoted with a <code class="value charval">green background</code>, and follow the key value.</li>
</ul>
+ <div id="key-values-list">
+
<dl id="key-value-set">
<dt><a id="key-Accept"><code class="value keyname">'Accept'</code></a></dt>
<dd>The Accept (Commit, OK) key.</dd>
@@ -5537,494 +5590,123 @@
<dt><a id="key-Zoom"><code class="value keyname">'Zoom'</code></a></dt>
<dd>The Zoom key.</dd>
+ <dt><a id="key-Backspace"><code class="value keyname">'Backspace'</code></a></dt>
<dt><a id="key-U-0008"><code class="value charval">\u0008</code></a></dt>
- <dt><a id="key-Backspace"><code class="value keyname">'Backspace'</code></a></dt>
<dd>The Backspace (Back) key.
<span class="note" id="_62"><strong>Note:</strong> This key value shall be also used for the key labeled <code class="value">'delete'</code> MacOS keyboards when not modified by the <code class="value">'Fn'</code> key.</span>
</dd>
+ <dt><a id="key-Tab"><code class="value keyname">'Tab'</code></a></dt>
<dt><a id="key-U-0009"><code class="value charval">\u0009</code></a></dt>
- <dt><a id="key-Tab"><code class="value keyname">'Tab'</code></a></dt>
<dd>The Horizontal Tabulation (Tab) key.</dd>
+ <dt><a id="key-Cancel"><code class="value keyname">'Cancel'</code></a></dt>
<dt><a id="key-U-0018"><code class="value charval">\u0018</code></a></dt>
- <dt><a id="key-Cancel"><code class="value keyname">'Cancel'</code></a></dt>
<dd>The Cancel key.</dd>
+ <dt><a id="key-Esc"><code class="value keyname">'Esc'</code></a></dt>
<dt><a id="key-U-001B"><code class="value charval">\u001B</code></a></dt>
- <dt><a id="key-Esc"><code class="value keyname">'Esc'</code></a></dt>
<dd>The Escape (Esc) key.</dd>
+ <dt><a id="key-Spacebar"><code class="value keyname">'Spacebar'</code></a></dt>
<dt><a id="key-U-0020"><code class="value charval">\u0020</code></a></dt>
- <dt><a id="key-Spacebar"><code class="value keyname">'Spacebar'</code></a></dt>
<dd>The Space (Spacebar) key: <code class="value charrep"> </code>.</dd>
- <dt><a id="key-U-0021"><code class="value charval">\u0021</code></a></dt>
- <dt><a id="key-Exclamation"><code class="value keyname">'Exclamation'</code></a></dt>
- <dd>The Exclamation Mark (Factorial, Bang) key: <code class="value charrep">!</code>.</dd>
-
- <dt><a id="key-U-0022"><code class="value charval">\u0022</code></a></dt>
- <dt><a id="key-DoubleQuote"><code class="value keyname">'DoubleQuote'</code></a></dt>
- <dd>The Quotation Mark (Quote Double) key: <code class="value charrep">"</code>.</dd>
-
- <dt><a id="key-U-0023"><code class="value charval">\u0023</code></a></dt>
- <dt><a id="key-Hash"><code class="value keyname">'Hash'</code></a></dt>
- <dd>The Number Sign (Pound Sign, Hash, Crosshatch, Octothorpe) key: <code class="value charrep">#</code>.</dd>
-
- <dt><a id="key-U-0024"><code class="value charval">\u0024</code></a></dt>
- <dt><a id="key-Dollar"><code class="value keyname">'Dollar'</code></a></dt>
- <dd>The Dollar Sign (milreis, escudo) key: <code class="value charrep">$</code>.</dd>
-
- <dt><a id="key-U-0026"><code class="value charval">\u0026</code></a></dt>
- <dt><a id="key-Ampersand"><code class="value keyname">'Ampersand'</code></a></dt>
- <dd>The Ampersand key: <code class="value charrep">&</code>.</dd>
-
- <dt><a id="key-U-0027"><code class="value charval">\u0027</code></a></dt>
- <dt><a id="key-Apostrophe"><code class="value keyname">'Apostrophe'</code></a></dt>
- <dd>The Apostrophe (Apostrophe-Quote, APL Quote) key: <code class="value charrep">'</code>.</dd>
-
- <dt><a id="key-U-0028"><code class="value charval">\u0028</code></a></dt>
- <dt><a id="key-LeftParen"><code class="value keyname">'LeftParen'</code></a></dt>
- <dd>The Left Parenthesis (Opening Parenthesis) key: <code class="value charrep">(</code>.</dd>
-
- <dt><a id="key-U-0029"><code class="value charval">\u0029</code></a></dt>
- <dt><a id="key-RightParen"><code class="value keyname">'RightParen'</code></a></dt>
- <dd>The Right Parenthesis (Closing Parenthesis) key: <code class="value charrep">)</code>.</dd>
-
- <dt><a id="key-U-002A"><code class="value charval">\u002A</code></a></dt>
- <dt><a id="key-Asterisk"><code class="value keyname">'Asterisk'</code></a></dt>
- <dd>The Asterisk (Star) key: <code class="value charrep">*</code>.</dd>
-
- <dt><a id="key-U-00D7"><code class="value charval">\u00D7</code></a></dt>
- <dt><a id="key-Multiply"><code class="value keyname">'Multiply'</code></a></dt>
- <dd>The Multiply key: <code class="value charrep">×</code>.</dd>
-
- <dt><a id="key-U-002B"><code class="value charval">\u002B</code></a></dt>
- <dt><a id="key-Plus"><code class="value keyname">'Plus'</code></a></dt>
- <dd>The Plus Sign (Plus) key: <code class="value charrep">+</code>.</dd>
-
- <dt><a id="key-U-0025"><code class="value charval">\u0025</code></a></dt>
- <dt><a id="key-Percent"><code class="value keyname">'Percent'</code></a></dt>
- <dd>The Percent Sign (Percent) key: <code class="value charrep">%</code>.</dd>
-
- <dt><a id="key-U-002C"><code class="value charval">\u002C</code></a></dt>
- <dt><a id="key-Comma"><code class="value keyname">'Comma'</code></a></dt>
- <dd>The Comma (decimal separator) sign key: <code class="value charrep">,</code>.</dd>
-
- <dt><a id="key-U-002D"><code class="value charval">\u002D</code></a></dt>
- <dt><a id="key-HyphenMinus"><code class="value keyname">'HyphenMinus'</code></a></dt>
- <dd>The Hyphen-minus (hyphen or minus sign) key: <code class="value charrep">-</code>.</dd>
-
- <dt><a id="key-U-002E"><code class="value charval">\u002E</code></a></dt>
- <dt><a id="key-Period"><code class="value keyname">'Period'</code></a></dt>
- <dd>The Full Stop (period, dot, decimal point) key: <code class="value charrep">.</code>.</dd>
-
- <dt><a id="key-U-002F"><code class="value charval">\u002F</code></a></dt>
- <dt><a id="key-Solidus"><code class="value keyname">'Solidus'</code></a></dt>
- <dd>The Solidus (slash, virgule, shilling) key: <code class="value charrep">/</code>.</dd>
-
- <dt><a id="key-U-003A"><code class="value charval">\u003A</code></a></dt>
- <dt><a id="key-Colon"><code class="value keyname">'Colon'</code></a></dt>
- <dd>The Colon key: <code class="value charrep">:</code>.</dd>
-
- <dt><a id="key-U-003B"><code class="value charval">\u003B</code></a></dt>
- <dt><a id="key-Semicolon"><code class="value keyname">'Semicolon'</code></a></dt>
- <dd>The Semicolon key: <code class="value charrep">;</code>.</dd>
-
- <dt><a id="key-U-003C"><code class="value charval">\u003C</code></a></dt>
- <dt><a id="key-LessThan"><code class="value keyname">'LessThan'</code></a></dt>
- <dd>The Less-Than Sign key: <code class="value charrep"><</code>.</dd>
-
- <dt><a id="key-U-003D"><code class="value charval">\u003D</code></a></dt>
- <dt><a id="key-Equals"><code class="value keyname">'Equals'</code></a></dt>
- <dd>The Equals Sign key: <code class="value charrep">=</code>.</dd>
-
- <dt><a id="key-U-003E"><code class="value charval">\u003E</code></a></dt>
- <dt><a id="key-"><code class="value keyname">'GreaterThan'</code></a></dt>
- <dd>The Greater-Than Sign key: <code class="value charrep">></code>.</dd>
-
- <dt><a id="key-U-003F"><code class="value charval">\u003F</code></a></dt>
- <dt><a id="key-QuestionMark"><code class="value keyname">'QuestionMark'</code></a></dt>
- <dd>The Question Mark key: <code class="value charrep">?</code>.</dd>
-
- <dt><a id="key-U-0030"><code class="value charval">\u0030</code></a></dt>
- <dt><a id="key-0"><code class="value keyname">'0'</code></a></dt>
- <dd>The Digit Zero key: <code class="value charrep">0</code>.</dd>
-
- <dt><a id="key-U-0031"><code class="value charval">\u0031</code></a></dt>
- <dt><a id="key-1"><code class="value keyname">'1'</code></a></dt>
- <dd>The Digit One key: <code class="value charrep">1</code>.</dd>
-
- <dt><a id="key-U-0032"><code class="value charval">\u0032</code></a></dt>
- <dt><a id="key-2"><code class="value keyname">'2'</code></a></dt>
- <dd>The Digit Two key: <code class="value charrep">2</code>.</dd>
-
- <dt><a id="key-U-0033"><code class="value charval">\u0033</code></a></dt>
- <dt><a id="key-3"><code class="value keyname">'3'</code></a></dt>
- <dd>The Digit Three key: <code class="value charrep">3</code>.</dd>
-
- <dt><a id="key-U-0034"><code class="value charval">\u0034</code></a></dt>
- <dt><a id="key-4"><code class="value keyname">'4'</code></a></dt>
- <dd>The Digit Four key: <code class="value charrep">4</code>.</dd>
-
- <dt><a id="key-U-0035"><code class="value charval">\u0035</code></a></dt>
- <dt><a id="key-5"><code class="value keyname">'5'</code></a></dt>
- <dd>The Digit Five key: <code class="value charrep">5</code>.</dd>
-
- <dt><a id="key-U-0036"><code class="value charval">\u0036</code></a></dt>
- <dt><a id="key-6"><code class="value keyname">'6'</code></a></dt>
- <dd>The Digit Six key: <code class="value charrep">6</code>.</dd>
-
- <dt><a id="key-U-0037"><code class="value charval">\u0037</code></a></dt>
- <dt><a id="key-7"><code class="value keyname">'7'</code></a></dt>
- <dd>The Digit Seven key: <code class="value charrep">7</code>.</dd>
-
- <dt><a id="key-U-0038"><code class="value charval">\u0038</code></a></dt>
- <dt><a id="key-8"><code class="value keyname">'8'</code></a></dt>
- <dd>The Digit Eight key: <code class="value charrep">8</code>.</dd>
-
- <dt><a id="key-U-0039"><code class="value charval">\u0039</code></a></dt>
- <dt><a id="key-9"><code class="value keyname">'9'</code></a></dt>
- <dd>The Digit Nine key: <code class="value charrep">9</code>.</dd>
-
- <dt><a id="key-U-0040"><code class="value charval">\u0040</code></a></dt>
- <dt><a id="key-At"><code class="value keyname">'At'</code></a></dt>
- <dd>The Commercial At key: <code class="value charrep">@</code>.</dd>
-
- <dt><a id="key-U-0041"><code class="value charval">\u0041</code></a></dt>
- <dt><a id="key-A"><code class="value keyname">'A'</code></a></dt>
- <dd>The Latin Capital Letter A key: <code class="value charrep">A</code>.</dd>
-
- <dt><a id="key-U-0042"><code class="value charval">\u0042</code></a></dt>
- <dt><a id="key-B"><code class="value keyname">'B'</code></a></dt>
- <dd>The Latin Capital Letter B key: <code class="value charrep">B</code>.</dd>
-
- <dt><a id="key-U-0043"><code class="value charval">\u0043</code></a></dt>
- <dt><a id="key-C"><code class="value keyname">'C'</code></a></dt>
- <dd>The Latin Capital Letter C key: <code class="value charrep">C</code>.</dd>
-
- <dt><a id="key-U-0044"><code class="value charval">\u0044</code></a></dt>
- <dt><a id="key-D"><code class="value keyname">'D'</code></a></dt>
- <dd>The Latin Capital Letter D key: <code class="value charrep">D</code>.</dd>
-
- <dt><a id="key-U-0045"><code class="value charval">\u0045</code></a></dt>
- <dt><a id="key-E"><code class="value keyname">'E'</code></a></dt>
- <dd>The Latin Capital Letter E key: <code class="value charrep">E</code>.</dd>
-
- <dt><a id="key-U-0046"><code class="value charval">\u0046</code></a></dt>
- <dt><a id="key-F"><code class="value keyname">'F'</code></a></dt>
- <dd>The Latin Capital Letter F key: <code class="value charrep">F</code>.</dd>
-
- <dt><a id="key-U-0047"><code class="value charval">\u0047</code></a></dt>
- <dt><a id="key-G"><code class="value keyname">'G'</code></a></dt>
- <dd>The Latin Capital Letter G key: <code class="value charrep">G</code>.</dd>
-
- <dt><a id="key-U-0048"><code class="value charval">\u0048</code></a></dt>
- <dt><a id="key-H"><code class="value keyname">'H'</code></a></dt>
- <dd>The Latin Capital Letter H key: <code class="value charrep">H</code>.</dd>
-
- <dt><a id="key-U-0049"><code class="value charval">\u0049</code></a></dt>
- <dt><a id="key-I"><code class="value keyname">'I'</code></a></dt>
- <dd>The Latin Capital Letter I key: <code class="value charrep">I</code>.</dd>
-
- <dt><a id="key-U-004A"><code class="value charval">\u004A</code></a></dt>
- <dt><a id="key-J"><code class="value keyname">'J'</code></a></dt>
- <dd>The Latin Capital Letter J key: <code class="value charrep">J</code>.</dd>
-
- <dt><a id="key-U-004B"><code class="value charval">\u004B</code></a></dt>
- <dt><a id="key-K"><code class="value keyname">'K'</code></a></dt>
- <dd>The Latin Capital Letter K key: <code class="value charrep">K</code>.</dd>
-
- <dt><a id="key-U-004C"><code class="value charval">\u004C</code></a></dt>
- <dt><a id="key-L"><code class="value keyname">'L'</code></a></dt>
- <dd>The Latin Capital Letter L key: <code class="value charrep">L</code>.</dd>
-
- <dt><a id="key-U-004D"><code class="value charval">\u004D</code></a></dt>
- <dt><a id="key-M"><code class="value keyname">'M'</code></a></dt>
- <dd>The Latin Capital Letter M key: <code class="value charrep">M</code>.</dd>
-
- <dt><a id="key-U-004E"><code class="value charval">\u004E</code></a></dt>
- <dt><a id="key-N"><code class="value keyname">'N'</code></a></dt>
- <dd>The Latin Capital Letter N key: <code class="value charrep">N</code>.</dd>
-
- <dt><a id="key-U-004F"><code class="value charval">\u004F</code></a></dt>
- <dt><a id="key-O"><code class="value keyname">'O'</code></a></dt>
- <dd>The Latin Capital Letter O key: <code class="value charrep">O</code>.</dd>
-
- <dt><a id="key-U-0050"><code class="value charval">\u0050</code></a></dt>
- <dt><a id="key-P"><code class="value keyname">'P'</code></a></dt>
- <dd>The Latin Capital Letter P key: <code class="value charrep">P</code>.</dd>
-
- <dt><a id="key-U-0051"><code class="value charval">\u0051</code></a></dt>
- <dt><a id="key-Q"><code class="value keyname">'Q'</code></a></dt>
- <dd>The Latin Capital Letter Q key: <code class="value charrep">Q</code>.</dd>
-
- <dt><a id="key-U-0052"><code class="value charval">\u0052</code></a></dt>
- <dt><a id="key-R"><code class="value keyname">'R'</code></a></dt>
- <dd>The Latin Capital Letter R key: <code class="value charrep">R</code>.</dd>
-
- <dt><a id="key-U-0053"><code class="value charval">\u0053</code></a></dt>
- <dt><a id="key-S"><code class="value keyname">'S'</code></a></dt>
- <dd>The Latin Capital Letter S key: <code class="value charrep">S</code>.</dd>
-
- <dt><a id="key-U-0054"><code class="value charval">\u0054</code></a></dt>
- <dt><a id="key-T"><code class="value keyname">'T'</code></a></dt>
- <dd>The Latin Capital Letter T key: <code class="value charrep">T</code>.</dd>
-
- <dt><a id="key-U-0055"><code class="value charval">\u0055</code></a></dt>
- <dt><a id="key-U"><code class="value keyname">'U'</code></a></dt>
- <dd>The Latin Capital Letter U key: <code class="value charrep">U</code>.</dd>
-
- <dt><a id="key-U-0056"><code class="value charval">\u0056</code></a></dt>
- <dt><a id="key-V"><code class="value keyname">'V'</code></a></dt>
- <dd>The Latin Capital Letter V key: <code class="value charrep">V</code>.</dd>
-
- <dt><a id="key-U-0057"><code class="value charval">\u0057</code></a></dt>
- <dt><a id="key-W"><code class="value keyname">'W'</code></a></dt>
- <dd>The Latin Capital Letter W key: <code class="value charrep">W</code>.</dd>
-
- <dt><a id="key-U-0058"><code class="value charval">\u0058</code></a></dt>
- <dt><a id="key-X"><code class="value keyname">'X'</code></a></dt>
- <dd>The Latin Capital Letter X key: <code class="value charrep">X</code>.</dd>
-
- <dt><a id="key-U-0059"><code class="value charval">\u0059</code></a></dt>
- <dt><a id="key-Y"><code class="value keyname">'Y'</code></a></dt>
- <dd>The Latin Capital Letter Y key: <code class="value charrep">Y</code>.</dd>
-
- <dt><a id="key-U-005A"><code class="value charval">\u005A</code></a></dt>
- <dt><a id="key-Z"><code class="value keyname">'Z'</code></a></dt>
- <dd>The Latin Capital Letter Z key: <code class="value charrep">Z</code>.</dd>
-
- <dt><a id="key-U-0061"><code class="value charval">\u0061</code></a></dt>
- <dt><a id="key-a"><code class="value keyname">'a'</code></a></dt>
- <dd>The Latin Small Letter A key: <code class="value charrep">a</code>.</dd>
-
- <dt><a id="key-U-0062"><code class="value charval">\u0062</code></a></dt>
- <dt><a id="key-b"><code class="value keyname">'b'</code></a></dt>
- <dd>The Latin Small Letter B key: <code class="value charrep">b</code>.</dd>
-
- <dt><a id="key-U-0063"><code class="value charval">\u0063</code></a></dt>
- <dt><a id="key-c"><code class="value keyname">'c'</code></a></dt>
- <dd>The Latin Small Letter C key: <code class="value charrep">c</code>.</dd>
-
- <dt><a id="key-U-0064"><code class="value charval">\u0064</code></a></dt>
- <dt><a id="key-d"><code class="value keyname">'d'</code></a></dt>
- <dd>The Latin Small Letter D key: <code class="value charrep">d</code>.</dd>
-
- <dt><a id="key-U-0065"><code class="value charval">\u0065</code></a></dt>
- <dt><a id="key-e"><code class="value keyname">'e'</code></a></dt>
- <dd>The Latin Small Letter E key: <code class="value charrep">e</code>.</dd>
-
- <dt><a id="key-U-0066"><code class="value charval">\u0066</code></a></dt>
- <dt><a id="key-f"><code class="value keyname">'f'</code></a></dt>
- <dd>The Latin Small Letter F key: <code class="value charrep">f</code>.</dd>
-
- <dt><a id="key-U-0067"><code class="value charval">\u0067</code></a></dt>
- <dt><a id="key-g"><code class="value keyname">'g'</code></a></dt>
- <dd>The Latin Small Letter G key: <code class="value charrep">g</code>.</dd>
-
- <dt><a id="key-U-0068"><code class="value charval">\u0068</code></a></dt>
- <dt><a id="key-h"><code class="value keyname">'h'</code></a></dt>
- <dd>The Latin Small Letter H key: <code class="value charrep">h</code>.</dd>
-
- <dt><a id="key-U-0069"><code class="value charval">\u0069</code></a></dt>
- <dt><a id="key-i"><code class="value keyname">'i'</code></a></dt>
- <dd>The Latin Small Letter I key: <code class="value charrep">i</code>.</dd>
-
- <dt><a id="key-U-006A"><code class="value charval">\u006A</code></a></dt>
- <dt><a id="key-j"><code class="value keyname">'j'</code></a></dt>
- <dd>The Latin Small Letter J key: <code class="value charrep">j</code>.</dd>
-
- <dt><a id="key-U-006B"><code class="value charval">\u006B</code></a></dt>
- <dt><a id="key-k"><code class="value keyname">'k'</code></a></dt>
- <dd>The Latin Small Letter K key: <code class="value charrep">k</code>.</dd>
-
- <dt><a id="key-U-006C"><code class="value charval">\u006C</code></a></dt>
- <dt><a id="key-l"><code class="value keyname">'l'</code></a></dt>
- <dd>The Latin Small Letter L key: <code class="value charrep">l</code>.</dd>
-
- <dt><a id="key-U-006D"><code class="value charval">\u006D</code></a></dt>
- <dt><a id="key-m"><code class="value keyname">'m'</code></a></dt>
- <dd>The Latin Small Letter M key: <code class="value charrep">m</code>.</dd>
-
- <dt><a id="key-U-006E"><code class="value charval">\u006E</code></a></dt>
- <dt><a id="key-n"><code class="value keyname">'n'</code></a></dt>
- <dd>The Latin Small Letter N key: <code class="value charrep">n</code>.</dd>
-
- <dt><a id="key-U-006F"><code class="value charval">\u006F</code></a></dt>
- <dt><a id="key-o"><code class="value keyname">'o'</code></a></dt>
- <dd>The Latin Small Letter O key: <code class="value charrep">o</code>.</dd>
-
- <dt><a id="key-U-0070"><code class="value charval">\u0070</code></a></dt>
- <dt><a id="key-p"><code class="value keyname">'p'</code></a></dt>
- <dd>The Latin Small Letter P key: <code class="value charrep">p</code>.</dd>
-
- <dt><a id="key-U-0071"><code class="value charval">\u0071</code></a></dt>
- <dt><a id="key-q"><code class="value keyname">'q'</code></a></dt>
- <dd>The Latin Small Letter Q key: <code class="value charrep">q</code>.</dd>
-
- <dt><a id="key-U-0072"><code class="value charval">\u0072</code></a></dt>
- <dt><a id="key-r"><code class="value keyname">'r'</code></a></dt>
- <dd>The Latin Small Letter R key: <code class="value charrep">r</code>.</dd>
-
- <dt><a id="key-U-0073"><code class="value charval">\u0073</code></a></dt>
- <dt><a id="key-s"><code class="value keyname">'s'</code></a></dt>
- <dd>The Latin Small Letter S key: <code class="value charrep">s</code>.</dd>
-
- <dt><a id="key-U-0074"><code class="value charval">\u0074</code></a></dt>
- <dt><a id="key-t"><code class="value keyname">'t'</code></a></dt>
- <dd>The Latin Small Letter T key: <code class="value charrep">t</code>.</dd>
-
- <dt><a id="key-U-0075"><code class="value charval">\u0075</code></a></dt>
- <dt><a id="key-u"><code class="value keyname">'u'</code></a></dt>
- <dd>The Latin Small Letter U key: <code class="value charrep">u</code>.</dd>
-
- <dt><a id="key-U-0076"><code class="value charval">\u0076</code></a></dt>
- <dt><a id="key-v"><code class="value keyname">'v'</code></a></dt>
- <dd>The Latin Small Letter V key: <code class="value charrep">v</code>.</dd>
-
- <dt><a id="key-U-0077"><code class="value charval">\u0077</code></a></dt>
- <dt><a id="key-w"><code class="value keyname">'w'</code></a></dt>
- <dd>The Latin Small Letter W key: <code class="value charrep">w</code>.</dd>
-
- <dt><a id="key-U-0078"><code class="value charval">\u0078</code></a></dt>
- <dt><a id="key-x"><code class="value keyname">'x'</code></a></dt>
- <dd>The Latin Small Letter X key: <code class="value charrep">x</code>.</dd>
-
- <dt><a id="key-U-0079"><code class="value charval">\u0079</code></a></dt>
- <dt><a id="key-y"><code class="value keyname">'y'</code></a></dt>
- <dd>The Latin Small Letter Y key: <code class="value charrep">y</code>.</dd>
-
- <dt><a id="key-U-007A"><code class="value charval">\u007A</code></a></dt>
- <dt><a id="key-z"><code class="value keyname">'z'</code></a></dt>
- <dd>The Latin Small Letter Z key: <code class="value charrep">z</code>.</dd>
-
- <dt><a id="key-U-005B"><code class="value charval">\u005B</code></a></dt>
- <dt><a id="key-LeftSquareBracket"><code class="value keyname">'LeftSquareBracket'</code></a></dt>
- <dd>The Left Square Bracket (Opening Square Bracket) key: <code class="value charrep">[</code>.</dd>
-
- <dt><a id="key-U-005C"><code class="value charval">\u005C</code></a></dt>
- <dt><a id="key-Backslash"><code class="value keyname">'Backslash'</code></a></dt>
- <dd>The Reverse Solidus (Backslash) key: <code class="value charrep">\</code>.</dd>
-
- <dt><a id="key-U-005D"><code class="value charval">\u005D</code></a></dt>
- <dt><a id="key-RightSquareBracket"><code class="value keyname">'RightSquareBracket'</code></a></dt>
- <dd>The Right Square Bracket (Closing Square Bracket) key: <code class="value charrep">]</code>.</dd>
-
- <dt><a id="key-U-005E"><code class="value charval">\u005E</code></a></dt>
- <dt><a id="key-Circumflex"><code class="value keyname">'Circumflex'</code></a></dt>
- <dd>The Circumflex Accent key: <code class="value charrep">^</code>.</dd>
-
- <dt><a id="key-U-005F"><code class="value charval">\u005F</code></a></dt>
- <dt><a id="key-Underscore"><code class="value keyname">'Underscore'</code></a></dt>
- <dd>The Low Sign (Spacing Underscore, Underscore) key: <code class="value charrep">_</code>.</dd>
-
- <dt><a id="key-U-0060"><code class="value charval">\u0060</code></a></dt>
- <dt><a id="key-Grave"><code class="value keyname">'Grave'</code></a></dt>
- <dd>The Grave Accent (Back Quote) key: <code class="value charrep">`</code>.</dd>
-
- <dt><a id="key-U-007B"><code class="value charval">\u007B</code></a></dt>
- <dt><a id="key-LeftCurlyBracket"><code class="value keyname">'LeftCurlyBracket'</code></a></dt>
- <dd>The Left Curly Bracket (Opening Curly Bracket, Opening Brace, Brace Left) key: <code class="value charrep">{</code>.</dd>
-
- <dt><a id="key-U-007C"><code class="value charval">\u007C</code></a></dt>
- <dt><a id="key-Pipe"><code class="value keyname">'Pipe'</code></a></dt>
- <dd>The Vertical Line (Vertical Bar, Pipe) key: <code class="value charrep">|</code>.</dd>
-
- <dt><a id="key-U-007D"><code class="value charval">\u007D</code></a></dt>
- <dt><a id="key-RightCurlyBracket"><code class="value keyname">'RightCurlyBracket'</code></a></dt>
- <dd>The Right Curly Bracket (Closing Curly Bracket, Closing Brace, Brace Right) key: <code class="value charrep">}</code>.</dd>
-
- <dt><a id="key-U-20AC"><code class="value charval">\u20AC</code></a></dt>
- <dt><a id="key-Euro"><code class="value keyname">'Euro'</code></a></dt>
- <dd>The Euro Currency Sign key: <code class="value charrep">€</code>.</dd>
-
- <dt><a id="key-U-00A1"><code class="value charval">\u00A1</code></a></dt>
- <dt><a id="key-InvertedExclamation"><code class="value keyname">'InvertedExclamation'</code></a></dt>
- <dd>The Inverted Exclamation Mark key: <code class="value charrep">¡</code>.</dd>
-
+ <dt><a id="key-Del"><code class="value keyname">'Del'</code></a></dt>
<dt><a id="key-U-007F"><code class="value charval">\u007F</code></a></dt>
- <dt><a id="key-Del"><code class="value keyname">'Del'</code></a></dt>
<dd>The Delete (Del) Key.
<span class="note" id="_63"><strong>Note:</strong> This key value shall be also used for the key labeled <code class="value">'delete'</code> MacOS keyboards when modified by the <code class="value">'Fn'</code> key.</span>
</dd>
+ <dt><a id="key-DeadGrave"><code class="value keyname">'DeadGrave'</code></a></dt>
<dt><a id="key-U-0300"><code class="value charval">\u0300</code></a></dt>
- <dt><a id="key-DeadGrave"><code class="value keyname">'DeadGrave'</code></a></dt>
<dd>The Combining Grave Accent (Greek Varia, Dead Grave) key.</dd>
+ <dt><a id="key-DeadEacute"><code class="value keyname">'DeadEacute'</code></a></dt>
<dt><a id="key-U-0301"><code class="value charval">\u0301</code></a></dt>
- <dt><a id="key-DeadEacute"><code class="value keyname">'DeadEacute'</code></a></dt>
<dd>The Combining Acute Accent (Stress Mark, Greek Oxia, Tonos, Dead Eacute) key.</dd>
+ <dt><a id="key-DeadCircumflex"><code class="value keyname">'DeadCircumflex'</code></a></dt>
<dt><a id="key-U-0302"><code class="value charval">\u0302</code></a></dt>
- <dt><a id="key-DeadCircumflex"><code class="value keyname">'DeadCircumflex'</code></a></dt>
<dd>The Combining Circumflex Accent (Hat, Dead Circumflex) key.</dd>
+ <dt><a id="key-DeadTilde"><code class="value keyname">'DeadTilde'</code></a></dt>
<dt><a id="key-U-0303"><code class="value charval">\u0303</code></a></dt>
- <dt><a id="key-DeadTilde"><code class="value keyname">'DeadTilde'</code></a></dt>
<dd>The Combining Tilde (Dead Tilde) key.</dd>
+ <dt><a id="key-DeadMacron"><code class="value keyname">'DeadMacron'</code></a></dt>
<dt><a id="key-U-0304"><code class="value charval">\u0304</code></a></dt>
- <dt><a id="key-DeadMacron"><code class="value keyname">'DeadMacron'</code></a></dt>
<dd>The Combining Macron (Long, Dead Macron) key.</dd>
+ <dt><a id="key-DeadBreve"><code class="value keyname">'DeadBreve'</code></a></dt>
<dt><a id="key-U-0306"><code class="value charval">\u0306</code></a></dt>
- <dt><a id="key-DeadBreve"><code class="value keyname">'DeadBreve'</code></a></dt>
<dd>The Combining Breve (Short, Dead Breve) key.</dd>
+ <dt><a id="key-DeadAboveDot"><code class="value keyname">'DeadAboveDot'</code></a></dt>
<dt><a id="key-U-0307"><code class="value charval">\u0307</code></a></dt>
- <dt><a id="key-DeadAboveDot"><code class="value keyname">'DeadAboveDot'</code></a></dt>
<dd>The Combining Dot Above (Derivative, Dead Above Dot) key.</dd>
+ <dt><a id="key-DeadUmlaut"><code class="value keyname">'DeadUmlaut'</code></a></dt>
<dt><a id="key-U-0308"><code class="value charval">\u0308</code></a></dt>
- <dt><a id="key-DeadUmlaut"><code class="value keyname">'DeadUmlaut'</code></a></dt>
<dd>The Combining Diaeresis (Double Dot Abode, Umlaut, Greek Dialytika, Double Derivative, Dead Diaeresis) key.</dd>
+ <dt><a id="key-DeadAboveRing"><code class="value keyname">'DeadAboveRing'</code></a></dt>
<dt><a id="key-U-030A"><code class="value charval">\u030A</code></a></dt>
- <dt><a id="key-DeadAboveRing"><code class="value keyname">'DeadAboveRing'</code></a></dt>
<dd>The Combining Ring Above (Dead Above Ring) key.</dd>
+ <dt><a id="key-DeadDoubleacute"><code class="value keyname">'DeadDoubleacute'</code></a></dt>
<dt><a id="key-U-030B"><code class="value charval">\u030B</code></a></dt>
- <dt><a id="key-DeadDoubleacute"><code class="value keyname">'DeadDoubleacute'</code></a></dt>
<dd>The Combining Double Acute Accent (Dead Doubleacute) key.</dd>
+ <dt><a id="key-DeadCaron"><code class="value keyname">'DeadCaron'</code></a></dt>
<dt><a id="key-U-030C"><code class="value charval">\u030C</code></a></dt>
- <dt><a id="key-DeadCaron"><code class="value keyname">'DeadCaron'</code></a></dt>
<dd>The Combining Caron (Hacek, V Above, Dead Caron) key.</dd>
+ <dt><a id="key-DeadCedilla"><code class="value keyname">'DeadCedilla'</code></a></dt>
<dt><a id="key-U-0327"><code class="value charval">\u0327</code></a></dt>
- <dt><a id="key-DeadCedilla"><code class="value keyname">'DeadCedilla'</code></a></dt>
<dd>The Combining Cedilla (Dead Cedilla) key.</dd>
+ <dt><a id="key-DeadOgonek"><code class="value keyname">'DeadOgonek'</code></a></dt>
<dt><a id="key-U-0328"><code class="value charval">\u0328</code></a></dt>
- <dt><a id="key-DeadOgonek"><code class="value keyname">'DeadOgonek'</code></a></dt>
<dd>The Combining Ogonek (Nasal Hook, Dead Ogonek) key.</dd>
+ <dt><a id="key-DeadIota"><code class="value keyname">'DeadIota'</code></a></dt>
<dt><a id="key-U-0345"><code class="value charval">\u0345</code></a></dt>
- <dt><a id="key-DeadIota"><code class="value keyname">'DeadIota'</code></a></dt>
<dd>The Combining Greek Ypogegrammeni (Greek Non-Spacing Iota Below, Iota Subscript, Dead Iota) key.</dd>
+ <dt><a id="key-DeadVoicedSound"><code class="value keyname">'DeadVoicedSound'</code></a></dt>
<dt><a id="key-U-3099"><code class="value charval">\u3099</code></a></dt>
- <dt><a id="key-DeadVoicedSound"><code class="value keyname">'DeadVoicedSound'</code></a></dt>
<dd>The Combining Katakana-Hiragana Voiced Sound Mark (Dead Voiced Sound) key.</dd>
+ <dt><a id="key-DeadSemivoicedSound"><code class="value keyname">'DeadSemivoicedSound'</code></a></dt>
<dt><a id="key-U-309A"><code class="value charval">\u309A</code></a></dt>
- <dt><a id="key-DeadSemivoicedSound"><code class="value keyname">'DeadSemivoicedSound'</code></a></dt>
<dd>The Combining Katakana-Hiragana Semi-Voiced Sound Mark (Dead Semivoiced Sound) key.</dd>
<dt><a id="key-Unidentified"><code class="value keyname">'Unidentified'</code></a></dt>
<dd>This key value is used when an implementations is unable to identify another key value, due to either hardware, platform, or software constraints. <span class="warning" id="_64"><strong>Warning!</strong> Conforming implementation must only use this key value when there is no way for the implementation to detect the key value, and does not indicate a conforming implementation by itself.</span></dd>
</dl>
+
+
+ </div>
+
</div>
<!-- div2 KeySet-Set -->
<div>
- <h4><a id="keyset-keyCode-charCode" href="#keyset-keyCode-charCode">6.2.8 Key values, keyCode, and charCode</a></h4>
-
- <p class="note" id="_41"><strong>Note:</strong> This section is non-normative.</p>
- <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, <a class="def" href="#glossary-user-agent">user agents</a>, versions, and even event types. A significant amount of legacy content, including script libraries, relies upon detecting the <a class="def" href="#glossary-user-agent">user agent</a> 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 values, which can be used safely and consistently in any <a class="def" href="#glossary-user-agent">user agent</a> which conforms to this specification. However, for the purpose of documenting the current state of these attributes and their relation to equivalent key values, this specification refers to the Legacy Keyboard Event Properties [<cite><a class="informative" href="#references-KeyProps">KeyProps</a></cite>] WG Note, which contains an informative reference table that documents some common values for the <code class="attr-name">keyCode</code> and <code class="attr-name">charCode</code> properties in different implementations.</p>
+ <h4><a id="keys-keyCode-charCode" href="#keys-keyCode-charCode">6.2.8 Key values, keyCode, and charCode</a></h4>
+
+ <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, <a class="def" href="#glossary-user-agent">user agents</a>, versions, and even event types. A significant amount of legacy content, including script libraries, relies upon detecting the <a class="def" href="#glossary-user-agent">user agent</a> 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.</p>
+
+ <p>Therefore, this specification does not normatively define the values for the <code class="attr-name">keyCode</code> or <code class="attr-name">charCode</code> attributes, relying instead only on the more robust key values, which can be used safely and consistently in any <a class="def" href="#glossary-user-agent">user agent</a> which conforms to this specification.</p>
+
+ <p>However, for the purpose of documenting the current state of these attributes and their relation to equivalent key values, this specification refers to the Legacy Keyboard Event Properties [<cite><a class="informative" href="#references-KeyProps">KeyProps</a></cite>] WG Note, which contains an informative reference table that documents some common values for the <code class="attr-name">keyCode</code> and <code class="attr-name">charCode</code> properties in different implementations.</p>
+
+ <p>Additionally, in order to provide raw access to any available environment-specific keys, absent the effect of modifier keys, the <a href="#events-KeyboardEvent">KeyboardEvent</a> interface does define the legacy <a href="#events-KeyboardEvent-keyCode">KeyboardEvent.keyCode</a> attribute, but the value of the attribute may vary between implementations and even between the same implementation on different operating systems. Normally, for modified values, the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute should be used instead of the <a href="#events-KeyboardEvent-keyCode">KeyboardEvent.keyCode</a> attribute.</p>
+
+ <p>This specification does not define the <code class="attr-name">charCode</code> attribute on the <a href="#events-KeyboardEvent">KeyboardEvent</a> interface, though it may be present in <a class="def" href="#glossary-user-agent">user agents</a> for compatibility with legacy content. The <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute should be used instead of the <code class="attr-name">charCode</code> attribute.</p>
+
+
</div>
</div>
@@ -6036,12 +5718,12 @@
<p><em>This section is informative</em></p>
<h2><a id="extending_events-intro" href="#extending_events-intro">A.1 Introduction</a></h2>
- <p class="1st">This specification defines several interfaces and many events; however, this is not an exhaustive set of events for all purposes. To allow authors and implementers to add desired functionality, this specification provides two mechanisms for extend this set of interfaces and events without creating conflicts: <a href="#extending_events-Custom_Events">custom events</a> and <a href="#extending_events-Vendor_Extensions">implementation-specific prefix strings</a>.</p>
+ <p class="1st">This specification defines several interfaces and many events; however, this is not an exhaustive set of events for all purposes. To allow content authors and implementers to add desired functionality, this specification provides two mechanisms for extend this set of interfaces and events without creating conflicts: <a href="#extending_events-Custom_Events">custom events</a> and <a href="#extending_events-Vendor_Extensions">implementation-specific prefix strings</a>.</p>
<h2><a id="extending_events-Custom_Events" href="#extending_events-Custom_Events">A.2 Custom Events</a></h2>
- <p>A script author may wish to define an application in terms of functional components, with event types that are meaningful to the application architecture. The author can use the <a href="#events-Events-CustomEvent"><code>CustomEvent</code></a> interface to create their own events appropriate to the level of abstraction they are using.</p>
+ <p>A script author may wish to define an application in terms of functional components, with event types that are meaningful to the application architecture. The content author can use the <a href="#events-CustomEvent"><code>CustomEvent</code></a> interface to create their own events appropriate to the level of abstraction they are using.</p>
<div class="example" id="example-custom-events">
- <p><strong>Example:</strong> An author may have created an application which features a dynamically generated bar chart. This bar chart is meant to be updated every 5 minutes, or when a feed shows new information, or when the user refreshes it manually by clicking a button. There are several handlers that have to be called when the chart needs to be updated: the application must fetch the most recent data, show an icon to the user that the event is being updated, and rebuild the chart. To manage this, the author can choose to create a custom "updateChart" event, which is fired whenever one of the trigger conditions is met:</p>
+ <p><strong>Example:</strong> A content author may have created an application which features a dynamically generated bar chart. This bar chart is meant to be updated every 5 minutes, or when a feed shows new information, or when the user refreshes it manually by clicking a button. There are several handlers that have to be called when the chart needs to be updated: the application must fetch the most recent data, show an icon to the user that the event is being updated, and rebuild the chart. To manage this, the content author can choose to create a custom "updateChart" event, which is fired whenever one of the trigger conditions is met:</p>
<pre><code>
var chartData = ...;
var evt = document.createEvent("CustomEvent");
@@ -6054,8 +5736,8 @@
<p>While a new event is being designed and prototyped, or when an event is intended for implementation-specific functionality, it is desirable to distinguish it from standardized events. Implementors should prefix event types specific to their implementations with a short string to distinguish it from the same event in other implementations and from standardized events. This is similar to the <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords" title="CSS 2.1: Syntax and basic data types">vendor-specific keyword prefixes</a> in CSS, though without the dashes ("-") used in CSS, since that can cause problems when used as an attribute name in Javascript.</p>
<div class="example" id="example-impl-extensions">
<p><strong>Example:</strong> A particular browser vendor, "FooCorp", may wish to introduce a new event, "<code>jump</code>". This vendor implements "<code>fooJump</code>" in their browser, using their vendor-specific prefix, <code class="value">foo</code>. Early adopters start experimenting with the event, using <code>someElement.addEventListener( "fooJump", doJump, false )</code>, and provide feedback to FooCorp, who change the behavior of "<code>fooJump</code>" accordingly.</p>
- <p>After some time, another vendor, "BarOrg", decides they also want the functionality, but implement it slightly differently, so they use their own vendor-specific prefix, <code class="value">bar</code> in their event type name, "<code>barJump</code>". Authors experimenting with this version of the "<code>jump</code>" event type register events with BarOrg's event type name. Authors who wish to write code that accounts for both browsers can either register each event type separately with specific handlers, or use the same handler and switch on the name of the event type; thus, early experiments in different codebases do not conflict, and the early adopter is able to write easily-maintained code for multiple implementations.</p>
- <p>Eventually, as the feature matures, the behavior of both browsers stabilize and may converge due to author and user feedback or through formal standardization; as this stabilization occurs, and risk of conflicts decrease, authors can remove the forked code, and use the "<code>jump</code>" event type name (even before it is formally standardized) using the same event handler and the more generic registration method <code>someElement.addEventListener( "jump", doJump, false )</code>.</p>
+ <p>After some time, another vendor, "BarOrg", decides they also want the functionality, but implement it slightly differently, so they use their own vendor-specific prefix, <code class="value">bar</code> in their event type name, "<code>barJump</code>". Content authors experimenting with this version of the "<code>jump</code>" event type register events with BarOrg's event type name. Content authors who wish to write code that accounts for both browsers can either register each event type separately with specific handlers, or use the same handler and switch on the name of the event type; thus, early experiments in different codebases do not conflict, and the early adopter is able to write easily-maintained code for multiple implementations.</p>
+ <p>Eventually, as the feature matures, the behavior of both browsers stabilize and may converge due to content author and user feedback or through formal standardization; as this stabilization occurs, and risk of conflicts decrease, content authors can remove the forked code, and use the "<code>jump</code>" event type name (even before it is formally standardized) using the same event handler and the more generic registration method <code>someElement.addEventListener( "jump", doJump, false )</code>.</p>
</div>
<h3><a id="extending_events-prefixes" href="#extending_events-prefixes">A.3.1 Known Implementation-Specific Prefixes</a></h3>
@@ -6096,7 +5778,7 @@
<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 <a class="def" href="#glossary-DOM-application">DOM application</a> 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>
<p>An implementation of DOM Level 3 Events alone is generally insufficient to perform attacks of this kind and the security considerations of the facilities that possibly support such attacks apply. For conformance with this specification, DOM implementations may take reasonable steps to ensure that <a class="def" href="#glossary-DOM-application">DOM applications</a> do not get access to confidential or sensitive information, for example, they may choose to dispatch no <code>load</code> events to nodes that attempt to embed resources on the local network.</p>
- <p>The <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method allows authors 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>
+ <p>The <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-5CED94D7"><code>DOMImplementation.hasFeature()</code></a> method allows content authors 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>
@@ -6105,7 +5787,7 @@
<div>
<h2><a id="changes-DOMEvents2to3Changes" href="#changes-DOMEvents2to3Changes">C.1 Changes between DOM Level 2 Events and DOM Level 3 Events</a></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>UIEvent</code></a> module, the event type <code>dblclick</code> has been added to the <a href="#events-Events-MouseEvent"><code>MouseEvent</code></a> module. This new specification provides a better separation between the DOM event flow, the event types, and the DOM interfaces.</p>
+ <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-UIEvent"><code>UIEvent</code></a> module, the event type <code>dblclick</code> has been added to the <a href="#events-MouseEvent"><code>MouseEvent</code></a> module. This new specification provides a better separation between the DOM event flow, the event types, and the DOM interfaces.</p>
<div>
<h3><a id="changes-DOMEvents2to3Changes-flow" href="#changes-DOMEvents2to3Changes-flow">C.1.1 Changes to DOM Level 2 event flow</a></h3>
@@ -6129,24 +5811,24 @@
<h3><a id="changes-DOMLevel2to3Changes" href="#changes-DOMLevel2to3Changes">C.1.3 Changes to DOM Level 2 Events interfaces</a></h3>
<dl>
- <dt>Interface <a href="#events-Events-Event"><code>Event</code></a></dt>
- <dd>The <a href="#events-Events-Event"><code>Event</code></a> interface has one new attribute, <a href="#events-event-type-defaultPrevented"><code>Event.defaultPrevented</code></a>, and one new methods, <a href="#events-event-type-stopImmediatePropagation"><code>Event.stopImmediatePropagation()</code></a>.<br />
+ <dt>Interface <a href="#events-Event"><code>Event</code></a></dt>
+ <dd>The <a href="#events-Event"><code>Event</code></a> interface has one new attribute, <a href="#events-event-type-defaultPrevented"><code>Event.defaultPrevented</code></a>, and one new methods, <a href="#events-event-type-stopImmediatePropagation"><code>Event.stopImmediatePropagation()</code></a>.<br />
<a href="#events-event-type-timeStamp"><code>Event.timeStamp</code></a> is now a <code>Number</code> in the ECMAScript binding; a proposed correction to make the same change in [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>] is forthcoming.<br />
DOM Level 3 Events considers the <a href="#events-event-type-type"><code>Event.type</code></a> attribute to be case-sensitive, while DOM Level 2 Events considers <a href="#events-event-type-type"><code>Event.type</code></a> to be case-insensitive.</dd>
- <dt>Interface <a href="#events-Events-EventTarget"><code>EventTarget</code></a></dt>
- <dd><!-- The <a href="#events-Events-EventTarget"><code>EventTarget</code></a> interface has foo new methods: . --> The method <a href="#events-Events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> was modified.</dd>
-
-<!-- <dt>Interface <a href="#events-Events-DocumentEvent"><code>DocumentEvent</code></a></dt>
- <dd>The <a href="#events-Events-DocumentEvent"><code>DocumentEvent</code></a> interface has one new method: <a href="#events-Events-DocumentEvent-canDispatch"><code>DocumentEvent.canDispatch()</code></a>.</dd>
+ <dt>Interface <a href="#events-EventTarget"><code>EventTarget</code></a></dt>
+ <dd><!-- The <a href="#events-EventTarget"><code>EventTarget</code></a> interface has foo new methods: . --> The method <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> was modified.</dd>
+
+<!-- <dt>Interface <a href="#events-DocumentEvent"><code>DocumentEvent</code></a></dt>
+ <dd>The <a href="#events-DocumentEvent"><code>DocumentEvent</code></a> interface has one new method: <a href="#events-DocumentEvent-canDispatch"><code>DocumentEvent.canDispatch()</code></a>.</dd>
-->
-<!-- <dt>Interface <a href="#events-Events-UIEvent"><code>UIEvent</code></a></dt>
- <dd>The <a href="#events-Events-UIEvent"><code>UIEvent</code></a> interface has a new method <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>.</dd>
+<!-- <dt>Interface <a href="#events-UIEvent"><code>UIEvent</code></a></dt>
+ <dd>The <a href="#events-UIEvent"><code>UIEvent</code></a> interface has a new method <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a>.</dd>
-->
- <dt>Interface <a href="#events-Events-MouseEvent"><code>MouseEvent</code></a></dt>
- <dd>The <a href="#events-Events-MouseEvent"><code>MouseEvent</code></a> interface has one new methods <a href="#events-Events-MouseEvent-getModifierState"><code>MouseEvent.getModifierState()</code></a>.</dd>
-
- <dt>Exception <a href="#events-Events-EventException"><code>EventException</code></a></dt>
+ <dt>Interface <a href="#events-MouseEvent"><code>MouseEvent</code></a></dt>
+ <dd>The <a href="#events-MouseEvent"><code>MouseEvent</code></a> interface has one new methods <a href="#events-MouseEvent-getModifierState"><code>MouseEvent.getModifierState()</code></a>.</dd>
+
+ <dt>Exception <a href="#events-EventException"><code>EventException</code></a></dt>
<dd>The <a href="#events-DISPATCH_REQUEST_ERR"><code>DISPATCH_REQUEST_ERR</code></a> constant has been added.</dd>
</dl>
@@ -6155,7 +5837,7 @@
<div>
<h3><a id="changes-DOMLevel3Addons" href="#changes-DOMLevel3Addons">C.1.4 New Interfaces</a></h3>
- <p>The interfaces <a href="#events-Events-CustomEvent"><code>CustomEvent</code></a>, <a href="#events-Events-FocusEvent"><code>FocusEvent</code></a>, <a href="#events-Events-TextEvent"><code>TextEvent</code></a>, <a href="#events-Events-KeyboardEvent"><code>KeyboardEvent</code></a>, <a href="#events-Events-CompositionEvent"><code>CompositionEvent</code></a>, <a href="#events-Events-MutationNameEvent"><code>MutationNameEvent</code></a>, <a href="#events-Events-WheelEvent"><code>WheelEvent</code></a>, and <a href="#events-Events-MouseWheelEvent"><code>MouseWheelEvent</code></a> were added to the Events module.</p>
+ <p>The interfaces <a href="#events-CustomEvent"><code>CustomEvent</code></a>, <a href="#events-FocusEvent"><code>FocusEvent</code></a>, <a href="#events-TextEvent"><code>TextEvent</code></a>, <a href="#events-KeyboardEvent"><code>KeyboardEvent</code></a>, <a href="#events-CompositionEvent"><code>CompositionEvent</code></a>, <a href="#events-MutationNameEvent"><code>MutationNameEvent</code></a>, <a href="#events-WheelEvent"><code>WheelEvent</code></a>, and <a href="#events-MouseWheelEvent"><code>MouseWheelEvent</code></a> were added to the Events module.</p>
</div>
<!-- div3 DOMLevel3Addons -->
</div>
@@ -6183,7 +5865,7 @@
<p>Glossary contributors: Arnaud Le Hors (W3C) and Robert S. Sutor (IBM Research).</p>
<p>Test suite contributors: Fred Drake, Mary Brady (NIST), Carmelo Montanez (NIST), Rick Rivello (NIST), Robert Clary (Netscape), Neil Delima (IBM), with a special mention to Curt Arnold.</p>
<p>In the WebApps Working Group, the following people made substantial material contributions in the process of refining and revising this specification: Hironori Bono (Google), Daniel Danilatos (Google), Travis Leithead (Microsoft), Cameron McCormack (Invited Expert), Olli Pettay (Mozilla), Jacob Rossi (Microsoft), Hallvord R. M. Steen (Opera)</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!), or writing informative books or Web sites: 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, NAKANO Masayuki, Garrett Smith, Sergey Ilinsky, Martijn Wargers, Sean Hogan, Magnus Kristiansen, Alex Russell, Jorge Chamorro, Peter-Paul Koch, William Edney, Erik Arvidsson, Cameron McCormack, Kazuyuki Ashimura, and Jan Goyvaerts (regular-expressions.info).</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!), or writing informative books or Web sites: 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, NAKANO Masayuki, Garrett Smith, Sergey Ilinsky, Martijn Wargers, Sean Hogan, Magnus Kristiansen, Alex Russell, Jorge Chamorro, Peter-Paul Koch, William Edney, Erik Arvidsson, Cameron McCormack, Kazuyuki Ashimura, Øistein E. Andersen, and Jan Goyvaerts (regular-expressions.info).</p>
<div>
<h2><a id="acknowledgements-Productions" href="#acknowledgements-Productions">D.1 Production Systems</a></h2>
@@ -6233,12 +5915,10 @@
</dt>
<dd><cite>"OMG IDL Syntax and Semantics"</cite> defined in <cite><a href="http://www.omg.org/technology/documents/formal/corba_2.htm">The Common Object Request Broker: Architecture and Specification, version 2</a></cite>, Object Management Group. The latest version of CORBA version 2.0 is available at http://www.omg.org/technology/documents/formal/corba_2.htm.</dd>
- <dt id="ref-rfc2119"><strong>[<a name="RFC2119" id="RFC2119">RFC2119</a>]</strong> Key words for use in RFCs to indicate Requirement Levels</dt>
+ <dt id="ref-rfc2119"><strong>[<a id="RFC2119">RFC2119</a>]</strong>Key words for use in RFCs to indicate Requirement Levels</dt>
<dd>S Bradner, 1997. The specification for how to use English to specify normativity, as if it were a technical language. Available at <a href="http://rfc.net/rfc2119.html">http://rfc.net/rfc2119.html</a></dd>
- <dt>
- <strong>[<a id="references-Unicode">Unicode</a>]</strong>
- </dt>
+ <dt><strong>[<a id="references-Unicode">Unicode</a>]</strong></dt>
<dd><cite>The Unicode Standard, Version 5.0</cite>, ISBN 0-321-48091-0, as updated periodically by the publication of new versions. See also <a class="normative" href="http://www.unicode.org/unicode/standard/versions">Versions of the Unicode Standard</a>, available at http://www.unicode.org/unicode/standard/versions, for latest version and additional information on versions of the standard and of the Unicode Character Database.</dd>
<dt>
@@ -6357,6 +6037,13 @@
</dt>
<dd><cite><a href="http://www.pcre.org/">Perl Compatible Regular Expressions library</a></cite>. Available at http://www.pcre.org/.</dd>
+
+ <dt id="ref-rfc20"><strong>[<a id="RFC20">RFC20</a>]</strong>ASCII format for Network Interchange</dt>
+ <dd>V. Cerf, 1969. Available at <a href="http://tools.ietf.org/rfc/rfc20.txt">http://tools.ietf.org/rfc/rfc20.txt</a></dd>
+
+ <dt id="ref-US-ASCII"><strong>[<a id="US-ASCII">US-ASCII</a>]</strong>Coded Character Set - 7-Bit American Standard Code for Information Interchange</dt>
+ <dd>Standard ANSI X3.4-1986, ANSI, 1986.</dd>
+
<dt>
<strong class="informref">[<a id="references-UAAG2">UAAG 2.0</a>]</strong>
</dt>
@@ -6367,6 +6054,10 @@
This version of the UAAG 2.0 specfication is http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100308/. The <a class="normative" href="http://www.w3.org/TR/UAAG20/">latest version of UAAG 2.0</a> is available at http://www.w3.org/TR/UAAG20/.
</dd>
+ <dt id="ref-WIN1252"><strong>[<a id="WIN1252">WIN1252</a>]</strong>Windows 1252</dt>
+ <dd><cite>S Steele. Unicode, Microsoft, 1998. cp1252 to Unicode table. Available at <a href="http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP1252.TXT">http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP1252.TXT</a></cite></dd>
+
+
<dt>
<strong>[<a id="references-XHTML10">XHTML 1.0</a>]</strong>
</dt>