--- a/html/DOM3-Events.html Wed Apr 19 21:41:52 2006 +0900
+++ b/html/DOM3-Events.html Wed Apr 19 21:42:42 2006 +0900
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!--
- Generated: Thu Apr 13 21:43:54 CEST 2006 hive
+ Generated: Wed Apr 19 14:39:13 CEST 2006 hive
-->
<html lang='en-US' xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US">
<head>
@@ -324,7 +324,7 @@
<div class='div2'><a name='events-Events-overview' id='events-Events-overview'></a>
<h2 id='events-Events-overview-h2' class='div2'>1.1 Introduction</h2>
<p>DOM Events is designed with two main goals. The first goal is the design of an <a href='#glossary-dt-event'>event</a> system which allows registration of event listeners and describes event flow through a tree structure. Additionally, the specification will provide standard modules of events for user interface control and document mutation notifications, including defined contextual information for each of these event modules.</p>
-<p>The second goal of the DOM Events is to provide a common subset of the current event systems used in <a href='#glossary-dt-DOM-Level-0'>DOM Level 0</a> browsers. This is intended to foster interoperability of existing scripts and content. It is not expected that this goal will be met with full backwards compatibility. However, the specification attempts to achieve this when possible.</p>
+<p>The second goal of DOM Events is to provide a common subset of the current event systems used in <a href='#glossary-dt-DOM-Level-0'>DOM Level 0</a> browsers. This is intended to foster interoperability of existing scripts and content. It is not expected that this goal will be met with full backwards compatibility. However, the specification attempts to achieve this when possible.</p>
<p>The following sections of the specification define both the specification for the DOM Event Model and a number of conformant event modules designed for use within the model. The DOM Event Model consists of:</p>
<ul>
<li>The <a href='#events-Events-flow'>DOM event flow</a>, which describe the flow of events in a tree-based structure.</li>
@@ -350,7 +350,7 @@
<p><a name='events-dt-event-flow' id='events-dt-event-flow'></a> The DOM event flow is the process through which the <a href='#glossary-dt-event'>event</a> originates from the DOM Events implementation and is dispatched into a tree. Each event has an <a href='#glossary-dt-event-target'>event target</a>, a targeted node in the case of the DOM Event flow, toward which the event is dispatched by the DOM Events implementation.</p>
<div class='div3'><a name='events-Events-phases' id='events-Events-phases'></a>
<h3 id='events-Events-phases-h3' class='div3'>1.2.1 Phases</h3>
-<p>The event is dispatched following a path from the root of the tree to this <a href='#glossary-dt-target-node'>target node</a>. It can then be handled locally at the target node level or from any target's ancestors higher in the tree. The event dispatching (also called event propagation) occurs in three phases and the following order:</p>
+<p>The event is dispatched following a path from the root of the tree to this <a href='#glossary-dt-target-node'>target node</a>. It can then be handled locally at the target node level or from any target's ancestors higher in the tree. Event propagation occurs in three phases in the following order:</p>
<ol>
<li>The <a href='#glossary-dt-capture-phase'>capture phase</a>: the event is dispatched to the target's ancestors from the root of the tree to the direct parent of the <a href='#glossary-dt-target-node'>target node</a>.</li>
<li>The <a href='#glossary-dt-target-phase'>target phase</a>: the event is dispatched to the <a href='#glossary-dt-target-node'>target node</a>.</li>
@@ -359,7 +359,7 @@
<div class='figure' style='text-align: center'><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' />
<p style='text-align:left'><i>Figure: graphical representation of an event dispatched in a DOM tree using the DOM event flow</i> [<a href='images/eventflow.svg'>SVG 1.0 version</a>]</p>
</div>
-<p>The target's ancestors are determined before the initial dispatch of the event. If the target node is removed during the dispatching, or a target's ancestor is added or removed, the event propagation will always be based on the target node and the target's ancestors determined before the dispatch.</p>
+<p>The target's ancestors are determined before the initial dispatch of the event. If the target node is removed while the event is being dispatched, or a target's ancestor is added or removed, the event propagation will always be based on the target node and the target's ancestors determined before the dispatch.</p>
<p>Some events may not necessarily accomplish the three phases of the DOM event flow, e.g. the event could only be defined for one or two phases. As an example, events defined in this specification will always accomplish the capture and target phases but some will not accomplish the bubbling phase ("bubbling events" versus "non-bubbling events", see also the <a href='#events-Events-Event-canBubble'><code>Event.bubbles</code></a> attribute).</p>
</div>
<!-- div3 Events-phases -->
@@ -374,7 +374,7 @@
<!-- div4 Events-listeners-registration -->
<div class='div4'><a name='events-Event-groups' id='events-Event-groups'></a>
<h4 id='events-Event-groups-h4' class='div4'>1.2.2.2 Event groups</h4>
-<p>An event listener is always part of a group. It is either explicitly in a group if a group has been specified at the registration or implicitly in the default group if no group has been specified. Within a group, event listeners are ordered in their order of registration. If two event listeners {A1, A2}, which are part of the same group, are registered one after the other (A1, then A2) for the same phase, the DOM event flow guarantees their triggering order (A1, then A2). If the two listeners are not part of the same group, no specification is made as to the order in which they will be triggered.</p>
+<p>An event listener is always part of a group. It is either explicitly in a group if a group has been specified at the registration or implicitly in the default group if no group has been specified. Within a group, event listeners are ordered according to their order of registration. If two event listeners {A1, A2}, which are part of the same group, are registered one after the other (A1, then A2) for the same phase, the DOM event flow guarantees their triggering order (A1, then A2). If the two listeners are not part of the same group, no specification is made as to the order in which they will be triggered.</p>
<p>In general, a DOM application does not need to define and use a separate group unless other event listeners, external to the DOM application, may change the event propagation (e.g. from a concurrent DOM application, from imported functionalities that rely on the event system, etc.).</p>
<p><b>Note:</b> While this specification does not specify a full ordering (i.e. groups are still unordered), it does specify ordering within a group. This implies that if the event listeners {A1, A2, B1, B2}, with A and B being two different groups, are registered for the same phase in the order A1, A2, B1, and B2, the following triggering orders are possible and conform to the DOM event flow:</p>
<ul>
@@ -411,10 +411,10 @@
<!-- div4 Events-listeners-reentrance -->
<div class='div4'><a name='events-Events-propagation-and-groups' id='events-Events-propagation-and-groups'></a>
<h4 id='events-Events-propagation-and-groups-h4' class='div4'>1.2.2.6 Event propagation and event groups</h4>
-<p>All event listeners are part of a group (see <a href='#events-Events-listeners-registration'>Registration of event listeners</a>). An event listener may prevent event listeners that are part of a same group from being triggered. The effect can be:</p>
+<p>All event listeners are part of a group (see <a href='#events-Events-listeners-registration'>Registration of event listeners</a>). An event listener may prevent event listeners that are part of the same group from being triggered. The effect can be:</p>
<ul>
<li>immediate: no more event listeners from the same group will be triggered by the event object (see <a href='#events-Events-Event-stopImmediatePropagation'><code>Event.stopImmediatePropagation()</code></a>);</li>
-<li>deferred until all event listeners from the same group have been triggered on the current node, i.e. the event listeners of the same group attached on other nodes will not be triggered (see <a href='#events-Events-Event-stopPropagation'><code>Event.stopPropagation()</code></a>).</li>
+<li>deferred: all event listeners from the same group on the current node will be triggered, but event listeners from the same group attached on other nodes will not be triggered (see <a href='#events-Events-Event-stopPropagation'><code>Event.stopPropagation()</code></a>).</li>
</ul>
<p>If two event listeners are registered for two different groups, one cannot prevent the other from being triggered.</p>
</div>
@@ -428,7 +428,7 @@
<p><a name='events-dt-cancelable-event' id='events-dt-cancelable-event'></a> A <i>cancelable event</i> is an event associated with a default action which is allowed to be canceled during the DOM event flow. At any phase during the event flow, the triggered event listeners have the option of canceling the default action or allowing the default action to proceed. In the case of the hyperlink in the browser, canceling the action would have the result of not activating the hyperlink. Not all events defined in this specification are cancelable events. See also <a href='#keyset-cancelable_keys'>Default actions and cancelable keyboard events</a>.</p>
<p>Different implementations will specify their own default actions, if any, associated with each event. The DOM Events specification does not attempt to specify these actions.</p>
<p>This specification does not provide mechanisms for accessing default actions or adding new ones.</p>
-<p>Implementations could react to an event before dispatching it and do changes on the display and the DOM tree. In such case, if a DOM attribute is changed before the event is fired, cancelling the device event type will also reverse the change. A good example is the attribute <code>HTMLInputElement.checked</code>: as described in [<cite><a class='noxref informative' href='#references-DOM2HTML'>DOM Level 2 HTML</a></cite>], the value of this property may be changed before the dispatch of the event; the user clicks on the radio button, the radio button is being checked (or unchecked) on the display, the attribute <code>HTMLInputElement.checked</code> is changed as well, and then the device event type <a href='#events-event-click'>click</a> is being dispatched. If the default action of the device event type is prevented, or if the default action attached to the <a href='#events-event-DOMActivate'>DOMActivate</a> event type is prevented, the property <code>HTMLInputElement.checked</code> will need to be changed back to its original value.</p>
+<p>Implementations could react to an event before dispatching it and make changes to the display and the DOM tree. Preventing the default action of such an event will reverse these changes. A good example is the attribute <code>HTMLInputElement.checked</code>: as described in [<cite><a class='noxref informative' href='#references-DOM2HTML'>DOM Level 2 HTML</a></cite>], the value of this attribute may be changed before the dispatch of the event; the user clicks on the radio button, the radio button is being checked (or unchecked) on the display, the attribute <code>HTMLInputElement.checked</code> is changed as well, and then the device event type <a href='#events-event-click'>click</a> is being dispatched. If the default action of the device event type is prevented, or if the default action attached to the <a href='#events-event-DOMActivate'>DOMActivate</a> event type is prevented, the attribute <code>HTMLInputElement.checked</code> will need to be changed back to its original value.</p>
</div>
<!-- div2 Events-flow-cancelation -->
<div class='div2'><a name='events-Events-flow-activation' id='events-Events-flow-activation'></a>
@@ -436,8 +436,8 @@
<p>Event targets may have associated <i>activation behavior</i> that implementations perform in response to an <i>activation request</i>. As an example, the typical activiation behavior associated with hyperlinks is to follow the link. Activation requests are typically initiated by users through an input device.</p>
<p>In terms of this specification, the activation behavior of the event target is the default action of the event type <a href='#events-event-DOMActivate'>DOMActivate</a>. DOM applications should use this event type whenever they wish to make or react to an activation request.</p>
<p>Implementations dispatch the <code>DOMActivate</code> event as default action of a <a href='#events-event-click'>click</a> event. This click event is either part of the activation request (e.g., a user requests activiation using a mouse), or synthesized by the implementation to accomodate legacy applications. Context information of such a <code>click</code> event is implementation dependent.</p>
-<p>When implementations dispatch a synthesized <code>click</code> event, the expectation is that they do so as default action of another event type. For example, when a user activates a hyperlink using a keyboard, the <code>click</code> event would be dispatched as default action of respective keyboard event.</p>
-<p>Implementations are, however, required to dispatch the synthesized <code>click</code> event as described above even if they do not dispatch such an event (e.g., when activation is requested by a voice command since this specification does not address event types for voice input).</p>
+<p>When implementations dispatch a synthesized <code>click</code> event, the expectation is that they do so as default action of another event type. For example, when a user activates a hyperlink using a keyboard, the <code>click</code> event would be dispatched as default action of the respective keyboard event.</p>
+<p>Implementations are required to dispatch the synthesized <code>click</code> event as described above even if they do not dispatch such an event (e.g., when activation is requested by a voice command, since this specification does not address event types for voice input).</p>
<p><b>Note:</b> The activation of an event target is device dependent but is also application dependent, e.g. a link in a document can be activated using a mouse click or a mouse double click.</p>
</div>
<!-- div2 Events-flow-activation -->
@@ -451,7 +451,7 @@
<!-- div3 Events-EventTypes-category -->
<div class='div3'><a name='events-Events-EventTypes-complete' id='events-Events-EventTypes-complete'></a>
<h3 id='events-Events-EventTypes-complete-h3' class='div3'>1.5.2 Complete list of event types</h3>
-<p>Depending on the level of DOM support, or the devices used for display (e.g. screen) or interaction (e.g., mouse, keyboard, touch screen, and voice), these event types can be generated by the implementation. When used with an [<cite><a class='noxref informative' href='#references-XML'>XML 1.0</a></cite>] or [<cite><a class='noxref informative' href='#references-HTML40'>HTML 4.01</a></cite>] application, the specifications of those languages may restrict the semantics and scope (in particular the possible target nodes) associated with an event type. Refer to the specification defining the language used in order to find those restrictions or to find event types that are not defined in this document.</p>
+<p>Depending on the level of DOM support, or the devices used for display (e.g. screen) or interaction (e.g., mouse, keyboard, touch screen, or voice), these event types can be generated by the implementation. When used with an [<cite><a class='noxref informative' href='#references-XML'>XML 1.0</a></cite>] or [<cite><a class='noxref informative' href='#references-HTML40'>HTML 4.01</a></cite>] application, the specifications of those languages may restrict the semantics and scope (in particular the possible target nodes) associated with an event type. Refer to the specification defining the language used in order to find those restrictions or to find event types that are not defined in this document.</p>
<p>The following table provides a non-normative summary of the event types defined in this specification. All event types are in no namespace and this specification refers to them by their local name only. All events will accomplish the capture and target phases, but not all of them will accomplish the bubbling phase (see also <a href='#events-Events-flow'>DOM event flow</a>). Some events are not <a href='#events-dt-cancelable-event'>cancelable</a> (see <a href='#events-Events-flow-cancelation'>Default actions and cancelable events</a>). Some events will only be dispatched to a specific set of possible targets, specified using node types. Contextual information related to the event type is accessible using DOM interfaces.</p>
<table border='1' summary='This table contains the complete list of event types defined by DOM Level 3 Events. The first column contains the local name of the event type. The second column indicates if the event accomplish the bubbling phase or not (all events accomplish the capture and target phases). The third column indicates if the default action associated with the event can be canceled. The fourth column indicates the nodes that can be target of the event. the fifth (and last) column indicates the DOM interface implemented by the event object.' cellpadding='0' cellspacing='0'>
<tr>
@@ -783,7 +783,7 @@
<dl>
<dt><b>Interface <i><a name='events-Events-Event' id='events-Events-Event'>Event</a></i></b> (introduced in <b class='since'>DOM Level 2</b>)</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 is passed as the parameter to an <a href='#events-Events-EventListener'><code>EventListener</code></a>. More specific context information is passed to event listeners by deriving additional interfaces from <code>Event</code> which contain information directly relating to the type of event they represent. These derived interfaces are also implemented by the object passed to the event listener.</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 is 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>
<dl>
<dt><br />
@@ -856,8 +856,8 @@
<dt><code class='attribute-name'><a name='events-Events-Event-eventPhase' id='events-Events-Event-eventPhase'>eventPhase</a></code> of type <code>unsigned short</code>, readonly</dt>
<dd>Used to indicate which phase of event flow is currently being accomplished.<br /></dd>
<dt><code class='attribute-name'><a name='events-Events-Event-namespaceURI' id='events-Events-Event-namespaceURI'>namespaceURI</a></code> of type <code>DOMString</code>, readonly, introduced in <b class='version'>DOM Level 3</b></dt>
-<dd>The <a href='#glossary-dt-namespaceURI'>namespace URI</a> associated with this event at creation time, or <code>null</code> if it is unspecified.<br />
-For events initialized with a DOM Level 2 Events method, such as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>, this is always <code>null</code>.<br /></dd>
+<dd>The <a href='#glossary-dt-namespaceURI'>namespace URI</a> associated with this event at initialization time, or <code>null</code> if it is unspecified.<br />
+DOM Level 2 Events initialization methods, such as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>, set the value to null.<br /></dd>
<dt><code class='attribute-name'><a name='events-Events-Event-target' id='events-Events-Event-target'>target</a></code> of type <a href='#events-Events-EventTarget'><code>EventTarget</code></a>, readonly</dt>
<dd>Used to indicate the <a href='#glossary-dt-event-target'>event target</a>. This attribute contains the <a href='#glossary-dt-target-node'>target node</a> when used with the <a href='#events-Events-flow'>DOM event flow</a>.<br /></dd>
<dt><code class='attribute-name'><a name='events-Events-Event-timeStamp' id='events-Events-Event-timeStamp'>timeStamp</a></code> of type <code>DOMTimeStamp</code>, readonly</dt>
@@ -871,7 +871,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-Event-initEvent' id='events-Events-Event-initEvent'>initEvent</a></code></dt>
<dd>
-<div class='method'>The <code>initEvent</code> method is used to initialize the value 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.<br />
+<div class='method'>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.<br />
This method sets the <a href='#events-Events-Event-type'><code>Event.type</code></a> attribute to <code>eventTypeArg</code>, and <a href='#events-Events-Event-namespaceURI'><code>Event.namespaceURI</code></a> to <code>null</code>. To initialize an event with a namespace URI, use the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
@@ -892,7 +892,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-initEventNS' id='events-Events-Event-initEventNS'>initEventNS</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>The <code>initEventNS</code> method is used to initialize the value of an <code>Event</code> object and has the same behavior as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>.
+<div class='method'>Initializes attributes of an <code>Event</code> object. This method has the same behavior as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -914,7 +914,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-preventDefault' id='events-Events-Event-preventDefault'>preventDefault</a></code></dt>
<dd>
-<div class='method'>If an event is cancelable, the <code>preventDefault</code> method is used to signify that the event is to be canceled, meaning any default action normally taken by the implementation as a result of the event will not occur (see also <a href='#events-Events-flow-cancelation'>Default actions and cancelable events</a>), and thus independently of event groups. Calling this method for a non-cancelable event has no effect.
+<div class='method'>Signifies that the event is to be canceled, meaning any default action normally taken by the implementation as a result of the event will not occur (see also <a href='#events-Events-flow-cancelation'>Default actions and cancelable events</a>). Calling this method for a non-cancelable event has no effect.
<p><b>Note:</b> This method does not stop the event propagation; use <a href='#events-Events-Event-stopPropagation'><code>Event.stopPropagation()</code></a> or <a href='#events-Events-Event-stopImmediatePropagation'><code>Event.stopImmediatePropagation()</code></a> for that effect.</p>
<div><b>No Parameters</b></div>
<div><b>No Return Value</b></div>
@@ -923,7 +923,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-stopImmediatePropagation' id='events-Events-Event-stopImmediatePropagation'>stopImmediatePropagation</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>This method is used to prevent event listeners of the same group to be triggered and, unlike <a href='#events-Events-Event-stopPropagation'><code>Event.stopPropagation()</code></a> its effect is immediate (see <a href='#events-Events-propagation-and-groups'>Event propagation and event groups</a>). Once it has been called, further calls to that method have no additional effect.
+<div class='method'>Prevents event listeners of the same group from being triggered and, unlike <a href='#events-Events-Event-stopPropagation'><code>Event.stopPropagation()</code></a> its effect is immediate (see <a href='#events-Events-propagation-and-groups'>Event propagation and event groups</a>). Once it has been called, further calls to this method have no additional effect.
<p><b>Note:</b> This method does not prevent the default action from being invoked; use <a href='#events-Events-Event-preventDefault'><code>Event.preventDefault()</code></a> for that effect.</p>
<div><b>No Parameters</b></div>
<div><b>No Return Value</b></div>
@@ -932,7 +932,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-stopPropagation' id='events-Events-Event-stopPropagation'>stopPropagation</a></code></dt>
<dd>
-<div class='method'>This method is used to prevent event listeners of the same group to be triggered but its effect is deferred until all event listeners attached on the <a href='#events-Events-Event-currentTarget'><code>Event.currentTarget</code></a> have been triggered (see <a href='#events-Events-propagation-and-groups'>Event propagation and event groups</a>). Once it has been called, further calls to that method have no additional effect.
+<div class='method'>Prevents event listeners of the same group from being triggered but its effect is deferred until all event listeners attached on the <a href='#events-Events-Event-currentTarget'><code>Event.currentTarget</code></a> have been triggered (see <a href='#events-Events-propagation-and-groups'>Event propagation and event groups</a>). Once it has been called, further calls to this method have no additional effect.
<p><b>Note:</b> This method does not prevent the default action from being invoked; use <a href='#events-Events-Event-preventDefault'><code>Event.preventDefault()</code></a> for that effect.</p>
<div><b>No Parameters</b></div>
<div><b>No Return Value</b></div>
@@ -976,7 +976,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-Event-initCustomEventNS' id='events-Events-Event-initCustomEventNS'>initCustomEventNS</a></code></dt>
<dd>
-<div class='method'>The <code>initCustomEventNS</code> method is used to initialize the value of a <code>CustomEvent</code> object and has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
+<div class='method'>Initializes attributes of a <code>CustomEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1004,8 +1004,8 @@
</dd>
<dt><b>Interface <i><a name='events-Events-EventTarget' id='events-Events-EventTarget'>EventTarget</a></i></b> (introduced in <b class='since'>DOM Level 2</b>)</dt>
<dd>
-<p>The <code>EventTarget</code> interface is implemented by all the objects which could be <a href='#glossary-dt-event-target'>event targets</a> in an implementation which supports the <a href='#events-Events-flows'>Event flows</a>. The interface allows registration and removal of event listeners, and dispatch of events to an event target.</p>
-<p>When used with <a href='#events-Events-flow'>DOM event flow</a>, this interface is implemented by all <a href='#glossary-dt-target-node'>target nodes</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>The <code>EventTarget</code> interface is implemented by all the objects which could be <a href='#glossary-dt-event-target'>event targets</a> in an implementation which supports an <a href='#events-Events-flows'>Event flows</a>. The interface allows registration and removal of event listeners, and dispatch of events to an event target.</p>
+<p>When used with the <a href='#events-Events-flow'>DOM event flow</a>, this interface is implemented by all <a href='#glossary-dt-target-node'>target nodes</a> and target ancestors, i.e. all DOM <code>Nodes</code> of the tree support this interface when the implementation conforms to DOM Level 3 Events and, therefore, this interface can be obtained by using binding-specific casting methods on an instance of the <code>Node</code> interface.</p>
<p>Invoking <code>addEventListener</code> or <code>addEventListenerNS</code> repeatedly on the same <code>EventTarget</code> with the same values for the parameters <code>namespaceURI</code>, <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. In order to register a listener for a different event group (<a href='#events-Event-groups'>Event groups</a>) the previously registered listener has to be removed first.</p>
<dl>
<dt><br />
@@ -1044,7 +1044,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-EventTarget-addEventListener' id='events-Events-EventTarget-addEventListener'>addEventListener</a></code></dt>
<dd>
-<div class='method'>This method allows the registration of an event listener in the default group and, depending on the <code>useCapture</code> parameter, on the capture phase of the DOM event flow or its target and bubbling phases. Invoking this method is equivalent to invoking <code>addEventListenerNS</code> with the same values for the parameters <code>type</code>, <code>listener</code>, and <code>useCapture</code>, and the value <code>null</code> for the parameters <code>namespaceURI</code> and <code>evtGroup</code>.
+<div class='method'>Registers an event listener in the default group and, depending on the <code>useCapture</code> parameter, on the capture phase of the DOM event flow or its target and bubbling phases. Invoking this method is equivalent to invoking <code>addEventListenerNS</code> with the same values for the parameters <code>type</code>, <code>listener</code>, and <code>useCapture</code>, and the value <code>null</code> for the parameters <code>namespaceURI</code> and <code>evtGroup</code>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1064,7 +1064,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-EventTargetGroup-addEventListenerNS' id='events-Events-EventTargetGroup-addEventListenerNS'>addEventListenerNS</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>This method allows the registration of an event listener in a specified group or the default group and, depending on the <code>useCapture</code> parameter, on the capture phase of the DOM event flow or its target and bubbling phases.
+<div class='method'>Registers an event listener in a specified group or the default group and, depending on the <code>useCapture</code> parameter, on the capture phase of the DOM event flow or its target and bubbling phases.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1088,7 +1088,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-EventTarget-dispatchEvent' id='events-Events-EventTarget-dispatchEvent'>dispatchEvent</a></code> modified in <b class='version'>DOM Level 3</b></dt>
<dd>
-<div class='method'>This method allows the dispatch of events into the implementation's event model. The <a href='#glossary-dt-event-target'>event target</a> of the event is the <code>EventTarget</code> object on which <code>dispatchEvent</code> is called.
+<div class='method'>Dispatches an event into the implementation's event model. The <a href='#glossary-dt-event-target'>event target</a> of the event is the <code>EventTarget</code> object on which <code>dispatchEvent</code> is called.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1141,7 +1141,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-EventTarget-removeEventListener' id='events-Events-EventTarget-removeEventListener'>removeEventListener</a></code></dt>
<dd>
-<div class='method'>This method allows the removal of event listeners from the default group. 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. The <a href='#events-Events-Event-namespaceURI'><code>Event.namespaceURI</code></a> for which the user registered the event listener is implied and is <code>null</code>.
+<div class='method'>Removes an event listener from the default group. 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. The <a href='#events-Events-Event-namespaceURI'><code>Event.namespaceURI</code></a> for which the user registered the event listener is implied and is <code>null</code>.
<p><b>Note:</b> Event listeners registered for other event groups than the default group cannot be removed using this method; see <a href='#events-Events-EventTargetGroup-removeEventListenerNS'><code>EventTarget.removeEventListenerNS()</code></a> for that effect.</p>
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
@@ -1162,7 +1162,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-EventTargetGroup-removeEventListenerNS' id='events-Events-EventTargetGroup-removeEventListenerNS'>removeEventListenerNS</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>This method allows the removal of an event listener, independently of the associated event group. Calling <code>removeEventListenerNS</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, independently of the associated event group. Calling <code>removeEventListenerNS</code> with arguments which do not identify any currently registered <a href='#events-Events-EventListener'><code>EventListener</code></a> on the <code>EventTarget</code> has no effect.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1292,7 +1292,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-DocumentEvent-canDispatch' id='events-Events-DocumentEvent-canDispatch'>canDispatch</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>Test if the implementation can generate events of a specified type.
+<div class='method'>Tests if the implementation can generate events of a specified type.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1324,12 +1324,12 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-DocumentEvent-createEvent' id='events-Events-DocumentEvent-createEvent'>createEvent</a></code></dt>
<dd>
-<div class='method'>
+<div class='method'>Creates an event object of the type specified.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
<dt><code class='parameter-name'>eventType</code> of type <code>DOMString</code></dt>
-<dd>The <code>eventType</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 init method must be called after creation in order to initialize the <a class='noxref' href='#events-Events-Event'><code>Event</code></a>'s values.<br />
+<dd>The <code>eventType</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.<br />
As an example, a user 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-Events-Event-initUIEventNS'><code>UIEvent.initUIEventNS()</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 href='#events-event-DOMActivate'>DOMActivate</a> for example, and set its context information, e.g. <a href='#events-Events-UIEvent-detail'><code>UIEvent.detail</code></a> in this example.
<p><b>Note:</b> For backward compatibility reason, "UIEvents", "MouseEvents", "MutationEvents", and "HTMLEvents" feature names are valid values for the parameter <code>eventType</code> and represent respectively the interfaces "UIEvent", "MouseEvent", "MutationEvent", and "Event".</p>
</dd>
@@ -1426,7 +1426,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-Event-initUIEvent' id='events-Events-Event-initUIEvent'>initUIEvent</a></code></dt>
<dd>
-<div class='method'>The <code>initUIEvent</code> method is used to initialize the value of a <code>UIEvent</code> object and has the same behavior as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>.
+<div class='method'>Initializes attributes of an <code>UIEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1450,7 +1450,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-initUIEventNS' id='events-Events-Event-initUIEventNS'>initUIEventNS</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>The <code>initUIEventNS</code> method is used to initialize the value of a <code>UIEvent</code> object and has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
+<div class='method'>Initializes attributes of an <code>UIEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1479,7 +1479,7 @@
</dl>
</dd>
</dl>
-<p>The User Interface event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values <code>"UIEvents"</code> and <code>"3.0"</code> (respectively) to determine whether or not the DOM Level 3 User Interface event module are supported by the implementation. In order to fully support this module, an implementation must also support the <code>"Events"</code> feature defined in this specification and the <code>"Views"</code> feature defined in the DOM Level 2 Views specification [<cite><a class='noxref normative' href='#references-DOM2Views'>DOM Level 2 Views</a></cite>]. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. The DOM Level 3 User Interface Events module is built on top of the DOM Level 2 User Interface Events [<cite><a class='noxref normative' href='#references-DOM2Events'>DOM Level 2 Events</a></cite>] module, i.e. a DOM Level 3 User Interface Events implementation where <code>hasFeature("UIEvents", "3.0")</code> returns <code>true</code> must also return <code>true</code> when the <code>version</code> number is <code>"2.0"</code>, <code>""</code> or, <code>null</code>.</p>
+<p>The User Interface event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values <code>"UIEvents"</code> and <code>"3.0"</code> (respectively) to determine whether or not the DOM Level 3 User Interface event module is supported by the implementation. In order to fully support this module, an implementation must also support the <code>"Events"</code> feature defined in this specification and the <code>"Views"</code> feature defined in the DOM Level 2 Views specification [<cite><a class='noxref normative' href='#references-DOM2Views'>DOM Level 2 Views</a></cite>]. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. The DOM Level 3 User Interface Events module is built on top of the DOM Level 2 User Interface Events [<cite><a class='noxref normative' href='#references-DOM2Events'>DOM Level 2 Events</a></cite>] module, i.e. a DOM Level 3 User Interface Events implementation where <code>hasFeature("UIEvents", "3.0")</code> returns <code>true</code> must also return <code>true</code> when the <code>version</code> number is <code>"2.0"</code>, <code>""</code> or, <code>null</code>.</p>
<div class='event-definition'>
<dl>
<dt><a name='events-event-DOMActivate' id='events-event-DOMActivate'></a><a class='noxref' href='#events-event-DOMActivate'>DOMActivate</a></dt>
@@ -1710,7 +1710,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-Event-initTextEvent' id='events-Events-Event-initTextEvent'>initTextEvent</a></code></dt>
<dd>
-<div class='method'>The <code>initTextEvent</code> method is used to initialize the value of a <code>TextEvent</code> object and has the same behavior as <a href='#events-Events-Event-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>TextEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initUIEvent'><code>UIEvent.initUIEvent()</code></a>. The value of <a href='#events-Events-UIEvent-detail'><code>UIEvent.detail</code></a> remains undefined.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1734,7 +1734,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-initTextEventNS' id='events-Events-Event-initTextEventNS'>initTextEventNS</a></code></dt>
<dd>
-<div class='method'>The <code>initTextEventNS</code> method is used to initialize the value of a <code>TextEvent</code> object and has the same behavior as <a href='#events-Events-Event-initUIEventNS'><code>UIEvent.initUIEventNS()</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>TextEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initUIEventNS'><code>UIEvent.initUIEventNS()</code></a>. The value of <a href='#events-Events-UIEvent-detail'><code>UIEvent.detail</code></a> remains undefined.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1810,7 +1810,7 @@
<dt><b>Interface <i><a name='events-Events-MouseEvent' id='events-Events-MouseEvent'>MouseEvent</a></i></b> (introduced in <b class='since'>DOM Level 2</b>)</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 theirs descendent elements.</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><b>Note:</b> When initializing <code>MouseEvent</code> objects using <code>initMouseEvent</code> or <code>initMouseEventNS</code>, implementations should use the client coordinates <code>clientX</code> and <code>clientY</code> for calculation of other coordinates (such as target coordinates exposed by <a href='#glossary-dt-DOM-Level-0'>DOM Level 0</a> implementations).</p>
<dl>
@@ -1899,7 +1899,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-MouseEvent-getModifierState' id='events-Events-MouseEvent-getModifierState'>getModifierState</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>This methods queries the state of a modifier using a key identifier. See also <a href='#keyset-Modifiers'>Modifier keys</a>.
+<div class='method'>This method queries the state of a modifier using a key identifier. See also <a href='#keyset-Modifiers'>Modifier keys</a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1919,7 +1919,7 @@
<p><code>boolean</code></p>
</td>
<td>
-<p><code>true</code> if it is modifier key and the modifier is activated, <code>false</code> otherwise.</p>
+<p><code>true</code> if it is a modifier key and the modifier is activated, <code>false</code> otherwise.</p>
</td>
</tr>
</table>
@@ -1931,7 +1931,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-initMouseEvent' id='events-Events-Event-initMouseEvent'>initMouseEvent</a></code></dt>
<dd>
-<div class='method'>The <code>initMouseEvent</code> method is used to initialize the value of a <code>MouseEvent</code> object and has the same behavior as <a href='#events-Events-Event-initUIEvent'><code>UIEvent.initUIEvent()</code></a>.
+<div class='method'>Initializes attributes of a <code>MouseEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initUIEvent'><code>UIEvent.initUIEvent()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -1975,7 +1975,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-initMouseEventNS' id='events-Events-Event-initMouseEventNS'>initMouseEventNS</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>The <code>initMouseEventNS</code> method is used to initialize the value of a <code>MouseEvent</code> object and has the same behavior as <a href='#events-Events-Event-initUIEventNS'><code>UIEvent.initUIEventNS()</code></a>.
+<div class='method'>Initializes attributes of a <code>MouseEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initUIEventNS'><code>UIEvent.initUIEventNS()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -2054,7 +2054,7 @@
<td valign='top' rowspan='1' colspan='1'><a href='#events-Events-MouseEvent-screenX'><code>MouseEvent.screenX</code></a>, <a href='#events-Events-MouseEvent-screenY'><code>MouseEvent.screenY</code></a>, <a href='#events-Events-MouseEvent-clientX'><code>MouseEvent.clientX</code></a>, <a href='#events-Events-MouseEvent-clientY'><code>MouseEvent.clientY</code></a>, <a href='#events-Events-MouseEvent-altKey'><code>MouseEvent.altKey</code></a>, <a href='#events-Events-MouseEvent-ctrlKey'><code>MouseEvent.ctrlKey</code></a>, <a href='#events-Events-MouseEvent-shiftKey'><code>MouseEvent.shiftKey</code></a>, <a href='#events-Events-MouseEvent-metaKey'><code>MouseEvent.metaKey</code></a>, <a href='#events-Events-MouseEvent-button'><code>MouseEvent.button</code></a>, and <a href='#events-Events-UIEvent-view'><code>UIEvent.view</code></a> are in use. The <a href='#events-Events-UIEvent-detail'><code>UIEvent.detail</code></a> attribute indicates the number of consecutive clicks of a pointing device button during a user action. The attribute value is <code>1</code> when the user begins this action and increments by <code>1</code> for each click. The notion of consecutive clicks depends on the environment configuration. For example, a "double click" will not happen if there is a long delay between the two clicks, even if the pointing device did not move.</td>
</tr>
</table>
-A pointing device button is clicked over an element. The definition of a click depends on the environment configuration; i.e. may depend on the screen location or the delay between the press and release of the pointing device button. In any case, the target node must be the same between the <a href='#events-event-mousedown'>mousedown</a>, <a href='#events-event-mouseup'>mouseup</a>, and <a href='#events-event-click'>click</a>. The sequence of these events is: <a href='#events-event-mousedown'>mousedown</a>, <a href='#events-event-mouseup'>mouseup</a>, and <a href='#events-event-click'>click</a>. It depends on the environment configuration whether the event type <a href='#events-event-click'>click</a> can occur if one or more of the event types <a href='#events-event-mouseover'>mouseover</a>, <a href='#events-event-mousemove'>mousemove</a>, and <a href='#events-event-mouseout'>mouseout</a> occur between the press and release of the pointing device button. In the case of nested elements, this event type is always targeted at the most deeply nested element. In addition, the event type is dispatched as described in <a href='#events-Events-flow-activation'>Activation requests and behavior</a>.</dd>
+A pointing device button is clicked over an element. The definition of a click depends on the environment configuration; i.e. it may depend on the screen location or the delay between the press and release of the pointing device button. In any case, the target node must be the same between the <a href='#events-event-mousedown'>mousedown</a>, <a href='#events-event-mouseup'>mouseup</a>, and <a href='#events-event-click'>click</a>. The sequence of these events is: <a href='#events-event-mousedown'>mousedown</a>, <a href='#events-event-mouseup'>mouseup</a>, and <a href='#events-event-click'>click</a>. It depends on the environment configuration whether the event type <a href='#events-event-click'>click</a> can occur if one or more of the event types <a href='#events-event-mouseover'>mouseover</a>, <a href='#events-event-mousemove'>mousemove</a>, and <a href='#events-event-mouseout'>mouseout</a> occur between the press and release of the pointing device button. In the case of nested elements, this event type is always targeted at the most deeply nested element. In addition, the event type is dispatched as described in <a href='#events-Events-flow-activation'>Activation requests and behavior</a>.</dd>
</dl>
</div>
<div class='event-definition'>
@@ -2260,7 +2260,7 @@
<dt><b>Interface <i><a name='events-Events-KeyboardEvent' id='events-Events-KeyboardEvent'>KeyboardEvent</a></i></b> (introduced in <b class='since'>DOM Level 3</b>)</dt>
<dd>
<p>The <code>KeyboardEvent</code> interface provides specific contextual information associated with keyboard devices. Each keyboard event references a key using an identifier. 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 use the method <a href='#events-Events-KeyboardEvent-getModifierState'><code>KeyboardEvent.getModifierState(keyIdentifierArg)</code></a> with "Control", "Shift", "Alt", or "Meta" respectively.</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(keyIdentifierArg)</code></a> with "Control", "Shift", "Alt", or "Meta" 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>
<dl>
<dt><br />
@@ -2347,7 +2347,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-KeyboardEvent-getModifierState' id='events-Events-KeyboardEvent-getModifierState'>getModifierState</a></code></dt>
<dd>
-<div class='method'>This methods queries the state of a modifier using a key identifier. See also <a href='#keyset-Modifiers'>Modifier keys</a>.
+<div class='method'>This method queries the state of a modifier using a key identifier. See also <a href='#keyset-Modifiers'>Modifier keys</a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -2367,7 +2367,7 @@
<p><code>boolean</code></p>
</td>
<td>
-<p><code>true</code> if it is modifier key and the modifier is activated, <code>false</code> otherwise.</p>
+<p><code>true</code> if it is a modifier key and the modifier is activated, <code>false</code> otherwise.</p>
</td>
</tr>
</table>
@@ -2379,7 +2379,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-KeyboardEvent-initKeyboardEvent' id='events-Events-KeyboardEvent-initKeyboardEvent'>initKeyboardEvent</a></code></dt>
<dd>
-<div class='method'>The <code>initKeyboardEvent</code> method is used to initialize the value of a <code>KeyboardEvent</code> object and has the same behavior as <a href='#events-Events-Event-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>KeyboardEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initUIEvent'><code>UIEvent.initUIEvent()</code></a>. The value of <a href='#events-Events-UIEvent-detail'><code>UIEvent.detail</code></a> remains undefined.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -2407,7 +2407,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-KeyboardEvent-initKeyboardEventNS' id='events-Events-KeyboardEvent-initKeyboardEventNS'>initKeyboardEventNS</a></code></dt>
<dd>
-<div class='method'>The <code>initKeyboardEventNS</code> method is used to initialize the value of a <code>KeyboardEvent</code> object and has the same behavior as <a href='#events-Events-Event-initUIEventNS'><code>UIEvent.initUIEventNS()</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>KeyboardEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initUIEventNS'><code>UIEvent.initUIEventNS()</code></a>. The value of <a href='#events-Events-UIEvent-detail'><code>UIEvent.detail</code></a> remains undefined.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -2604,7 +2604,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-Event-initMutationEvent' id='events-Events-Event-initMutationEvent'>initMutationEvent</a></code></dt>
<dd>
-<div class='method'>The <code>initMutationEvent</code> method is used to initialize the value of a <code>MutationEvent</code> object and has the same behavior as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>.
+<div class='method'>Initializes attributes of a <code>MutationEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initEvent'><code>Event.initEvent()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -2634,7 +2634,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-initMutationEventNS' id='events-Events-Event-initMutationEventNS'>initMutationEventNS</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>The <code>initMutationEventNS</code> method is used to initialize the value of a <code>MutationEvent</code> object and has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
+<div class='method'>Initializes attributes of a <code>MutationEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -2976,7 +2976,7 @@
<dl>
<dt><code class='method-name'><a name='events-Events-Event-initMutationNameEvent' id='events-Events-Event-initMutationNameEvent'>initMutationNameEvent</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>The <code>initMutationNameEvent</code> method is used to initialize the value of a <code>MutationNameEvent</code> object and has the same behavior as <a href='#events-Events-Event-initMutationEvent'><code>MutationEvent.initMutationEvent()</code></a>.
+<div class='method'>Initializes attributes of a <code>MutationNameEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initMutationEvent'><code>MutationEvent.initMutationEvent()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>
@@ -3002,7 +3002,7 @@
<!-- method --></dd>
<dt><code class='method-name'><a name='events-Events-Event-initMutationNameEventNS' id='events-Events-Event-initMutationNameEventNS'>initMutationNameEventNS</a></code> introduced in <b class='since'>DOM Level 3</b></dt>
<dd>
-<div class='method'>The <code>initMutationNameEventNS</code> method is used to initialize the value of a <code>MutationNameEvent</code> object and has the same behavior as <a href='#events-Events-Event-initMutationEventNS'><code>MutationEvent.initMutationEventNS()</code></a>.
+<div class='method'>Initializes attributes of a <code>MutationNameEvent</code> object. This method has the same behavior as <a href='#events-Events-Event-initMutationEventNS'><code>MutationEvent.initMutationEventNS()</code></a>.
<div class='parameters'><b>Parameters</b>
<div class='paramtable'>
<dl>