--- a/html/DOM3-Events.html Tue Jun 04 13:27:25 2013 -0700
+++ b/html/DOM3-Events.html Tue Jun 04 13:32:11 2013 -0700
@@ -65,7 +65,7 @@
wgURI: ["http://www.w3.org/2008/webapps/"],
wgPublicList: "www-dom",
wgPatentURI: ["http://www.w3.org/2004/01/pp-impl/42538/status"],
- maxTocLevel: 3
+ maxTocLevel: 4
};
</script>
</head>
@@ -103,7 +103,7 @@
before it eventually reaches the Candidate Recommendation stage should join the aforementioned mailing lists and take part in the discussions.</p>
</section>
- <!-- Section: DOM3 Events Overview ========================================================-->
+ <!-- Section 1: DOM3 Events Overview ========================================================-->
<section id="dom-events">
<h1>Document Object Model Events</h1>
<section id="dom-events-overview">
@@ -264,7 +264,7 @@
</section> <!-- style-conventions -->
</section> <!-- dom-events -->
- <!-- Section: Glossary ========================================================-->
+ <!-- Section 2: Glossary ========================================================-->
<section id="glossary">
<h1>Glossary</h1>
@@ -305,14 +305,14 @@
<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. In this
specification, character values are denoted as a unicode string (e.g., <code class="char">'\u0020'</code>) or a glyph representation of the same code point (e.g.,
<code class="glyph">' '</code>), and are color coded to help distinguish these two representations.
- <p class="note"><strong>Note:</strong> in source code, some key values, such as non-graphic characters, can be represented using
+ <p class="note"><strong>Note:</strong> In source code, some key values, such as non-graphic characters, can be represented using
the character escape syntax of the programming language in use.</p>
</dd>
<dt id="glossary-candidate-event-handlers"><dfn>candidate event handlers</dfn></dt>
<dt><dfn>candidate event listeners</dfn></dt>
<dd>The list of all <a class="def" href="#glossary-event-handler">event listeners</a> that have been registered on the target object in their order of registration. This
- list is captured or <q>frozen</q> before event listeners on the target object are dispatched, and released or <q>un-frozen</q> after this set of of candidate event
+ list is captured or <q>frozen</q> before event listeners on the target object are dispatched, and released or <q>un-frozen</q> after this set of candidate event
handlers have been dispatched (allowing these event listeners to add or remove additional listeners on other objects in an event's propagation chain, but not affect
the order of listeners that will be invoked on the target object).
@@ -397,7 +397,7 @@
(the <a class="def" href="#glossary-current-event-target">current event target</a>) and are provided with the event object itself.
<p class="note"><strong>Note: </strong>In JavaScript, user-defined functions are considered to implement the <code>EventListener</code> interface. Thus the
- <code>Event</code> object will be provided as the first paramter to the user-defined function when it is invoked. Additionally, JavaScript objects can also implement
+ <code>Event</code> object will be provided as the first parameter to the user-defined function when it is invoked. Additionally, JavaScript objects can also implement
the <code>EventListener</code> interface when they define a <q><code>handleEvent</code></q> method.</p>
</dd>
@@ -407,7 +407,7 @@
href="#event-type-mousedown"><code>mousedown</code></a> event from the trackpad followed by a <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>
event from the mouse would not result in a <a class="eventtype" href="#event-type-click"><code>click</code></a> event.
- <p class="note"><strong>Note:</strong> there can be interactions between different event orders; for example, a <a class="eventtype" href="#event-type-click"><code>click</code></a> event might
+ <p class="note"><strong>Note:</strong> There can be interactions between different event orders; for example, a <a class="eventtype" href="#event-type-click"><code>click</code></a> event might
be modified by a concurrent <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event (<code class="key">'Shift'</code><code>+click</code>); however, the event orders
of these different event sources would be distinct.</p>
@@ -437,7 +437,7 @@
Document Focus and Focus Context</a>.</dd>
<dt id="glossary-event-focus-ring"><dfn>focus ring</dfn></dt>
- <dd>A focus ring is a an ordered set of <a class="def" href="#glossary-event-focus">focus</a> targets within a document. A <a class="def" href="#glossary-host-language">
+ <dd>A focus ring is an ordered set of <a class="def" href="#glossary-event-focus">focus</a> targets within a document. A <a class="def" href="#glossary-host-language">
host language</a> MAY define one or more ways to determine the order of targets, such as document order, a numerical index defined per focus target, explicit pointers
between focus targets, or a hybrid of different models. Each document MAY contain multiple focus rings, or conditional focus rings. Typically, for document-order
or indexed focus rings, focus <q>wraps around</q> from the last focus target to the first.</dd>
@@ -536,26 +536,27 @@
possible peers (nodes of the same level in the hierarchy, with the same immediate ancestor).</dd>
<dt id="glossary-Unicode-character-categories"><dfn>Unicode character categories</dfn></dt>
- <dd>The Unicode character categories, a subset of the complete Unicode general categories, comprise the categories
- <abbr title="Letter, Lowercase">Ll</abbr>,
- <abbr title="Letter, Modifier">Lm</abbr>,
- <abbr title="Letter, Other">Lo</abbr>,
- <abbr title="Letter, Titlecase">Lt</abbr>,
- <abbr title="Letter, Uppercase">Lu</abbr>,
- <abbr title="Number, Decimal Digit">Nd</abbr>,
- <abbr title="Number, Letter">Nl</abbr>,
- <abbr title="Number, Other">No</abbr>,
- <abbr title="Punctuation, Connector">Pc</abbr>,
- <abbr title="Punctuation, Dash">Pd</abbr>,
- <abbr title="Punctuation, Close">Pe</abbr>,
- <abbr title="Punctuation, Final quote">Pf</abbr>,
- <abbr title="Punctuation, Initial quote">Pi</abbr>,
- <abbr title="Punctuation, Other">Po</abbr>,
- <abbr title="Punctuation, Open">Ps</abbr>,
- <abbr title="Symbol, Currency">Sc</abbr>,
- <abbr title="Symbol, Modifier">Sk</abbr>,
- <abbr title="Symbol, Math">Sm</abbr>, and
- <abbr title="Symbol, Other">So</abbr>.</dd>
+ <dd>A subset of the General Category values that are defined for each Unicode code point. This subset contains all the
+ Letter (<abbr title="Letter, Lowercase">Ll</abbr>,
+ <abbr title="Letter, Modifier">Lm</abbr>,
+ <abbr title="Letter, Other">Lo</abbr>,
+ <abbr title="Letter, Titlecase">Lt</abbr>,
+ <abbr title="Letter, Uppercase">Lu</abbr>),
+ Number (<abbr title="Number, Decimal Digit">Nd</abbr>,
+ <abbr title="Number, Letter">Nl</abbr>,
+ <abbr title="Number, Other">No</abbr>),
+ Punctuation (<abbr title="Punctuation, Connector">Pc</abbr>,
+ <abbr title="Punctuation, Dash">Pd</abbr>,
+ <abbr title="Punctuation, Close">Pe</abbr>,
+ <abbr title="Punctuation, Final quote">Pf</abbr>,
+ <abbr title="Punctuation, Initial quote">Pi</abbr>,
+ <abbr title="Punctuation, Other">Po</abbr>,
+ <abbr title="Punctuation, Open">Ps</abbr>)
+ and Symbol (<abbr title="Symbol, Currency">Sc</abbr>,
+ <abbr title="Symbol, Modifier">Sk</abbr>,
+ <abbr title="Symbol, Math">Sm</abbr>,
+ <abbr title="Symbol, Other">So</abbr>)
+ category values.</dd>
<dt id="glossary-unicode-code-point"><dfn>Unicode code point</dfn></dt>
<dd>A Unicode code point is a unique hexadecimal number signifying a character by its index in the Unicode codespace (or library of characters). In the context of
@@ -576,7 +577,7 @@
</dl>
</section>
- <!-- Section: Architecture ========================================================-->
+ <!-- Section 3: Architecture ========================================================-->
<section id="dom-event-architecture">
<h1>DOM Event Architecture</h1>
@@ -592,7 +593,7 @@
<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" />
+ <img src="images/eventflow.png" alt="Graphical representation of an event dispatched in a DOM tree using the DOM event flow" title="graphical representation of an event dispatched in a DOM tree using the DOM event flow" />
</object>
</div>
@@ -613,12 +614,12 @@
</div>
<p>Exceptions thrown inside event listeners MUST NOT stop the propagation of the event or affect the
- <a class="def" href="#glossary-propagation-path">propagation path</a>. The exception itself MUST NOT propogate outside the scope of the event
+ <a class="def" href="#glossary-propagation-path">propagation path</a>. The exception itself MUST NOT propagate outside the scope of the event
handler.</p>
<div class="example">
<div class="example-title">Example</div>
- <p>In the following code, the exception thrown from the call to <code>throw "Error"</code> does not propogate into the parent scope,
+ <p>In the following code, the exception thrown from the call to <code>throw "Error"</code> does not propagate into the parent scope
(which would prevent the <code>console.log</code> statement from executing):</p>
<pre>var e = document.createEvent("Event");
e.initEvent("myevent", false, false);
@@ -632,23 +633,23 @@
</div>
<p id="event-phase">As the next step, the event object MUST complete one or more <a class="def" href="#glossary-phase">event phases</a>. This specification defines
- three event phases: <a href="#capture-phase">capture phase</a>; <a href="#target-phase">target phase</a>; and <a href="#bubble-phase">bubble phase</a>. Event objects
+ three event phases: <a href="#capture-phase">capture phase</a>, <a href="#target-phase">target phase</a> and <a href="#bubble-phase">bubble phase</a>. Event objects
complete these phases in the specified order using the partial propagation paths as defined below. A phase MUST be skipped if it is not
supported, or if the event object's propagation has been stopped. For example, if the <a href="#events-event-type-canBubble"><code>Event.bubbles</code></a>
attribute is set to false, the bubble phase will be skipped, and if <a href="#events-event-type-stopPropagation"><code>Event.stopPropagation()</code></a> has been
called prior to the dispatch, all phases MUST be skipped.</p>
<ol>
- <li>The <strong id="capture-phase">capture phase</strong>: the event object MUST propagate through the target's ancestors from the <a class="def"
+ <li>The <strong id="capture-phase">capture phase</strong>: The event object MUST propagate through the target's ancestors from the <a class="def"
href="#glossary-defaultView">defaultView</a> to the target's parent. This phase is also known as the <em>capturing phase</em>. Event
listeners registered for this phase MUST handle the event before it reaches its target.</li>
- <li>The <strong id="target-phase">target phase</strong>: the event object MUST arrive at the event object's <a class="def" href="#glossary-event-target">
+ <li>The <strong id="target-phase">target phase</strong>: The event object MUST arrive at the event object's <a class="def" href="#glossary-event-target">
event target</a>. This phase is also known as the <em>at-target phase</em>. Event listeners registered for this phase MUST
handle the event once it has reached its target. If the <a class="def" href="#glossary-event-type">event type</a> indicates that
the event MUST NOT bubble, the event object MUST halt after completion of this phase.</li>
- <li>The <strong id="bubble-phase">bubble phase</strong>: the event object propagates through the target's ancestors in reverse order, starting
+ <li>The <strong id="bubble-phase">bubble phase</strong>: The event object propagates through the target's ancestors in reverse order, starting
with the target's parent and ending with the <a class="def" href="#glossary-defaultView">defaultView</a>. This phase is also known as the <em>bubbling phase</em>.
Event listeners registered for this phase MUST handle the event after it has reached its target.</li>
</ol>
@@ -710,7 +711,7 @@
<div class="example-title">Example</div>
<p>A <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a> event is dispatched immediately after the user presses down a button on a
pointing device (typically a mouse). One possible <a class="def" href="#glossary-default-action">default action</a> taken by the implementation is to set up a state
- machine that allows the user to drag images or select text; the <a class="def" href="#glossary-default-action">default action</a> depends on what happens next--for
+ machine that allows the user to drag images or select text. The <a class="def" href="#glossary-default-action">default action</a> depends on what happens next — for
example, if the user's pointing device is over text, a text selection might begin. If the user's pointing device is over an image, then an image-drag action could
begin. Preventing the <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>
event prevents these actions from occuring.</p>
@@ -721,8 +722,8 @@
<div class="example">
<div class="example-title">Example</div>
- <p>The default action associated with the <a class="eventtype" href="#event-type-click"><code>click</code></a> event on <input
- type="checkbox"> elements toggles the <code>checked</code> IDL attribute value of that element. If the <a class="eventtype" href="#event-type-click"><code>click</code>
+ <p>The default action associated with the <a class="eventtype" href="#event-type-click"><code>click</code></a> event on <code><input
+ type="checkbox"></code> elements toggles the <code>checked</code> IDL attribute value of that element. If the <a class="eventtype" href="#event-type-click"><code>click</code>
</a> event's default action is cancelled, then the value is restored to its former state.</p>
</div>
@@ -760,7 +761,7 @@
<p>Events MAY be dispatched either synchronously or asynchronously.</p>
<p>Events which are synchronous (<em><q>sync events</q></em>) MUST be treated as if they are in a virtual queue in a first-in-first-out model, ordered by sequence
- of temporal occurrence, with respect to other events, to changes in the DOM, and to user interaction. Each event in this virtual queue MUST be delayed until the
+ of temporal occurrence with respect to other events, to changes in the DOM, and to user interaction. Each event in this virtual queue MUST be delayed until the
previous event has completed its propagation behavior, or been canceled. Some sync events are driven by a specific device or process, such as mouse button events;
these events are governed by the <a class="def" href="#glossary-event-order">event order</a> algorithms defined for that set of events, and a user agent MUST dispatch
these events in the defined order.</p>
@@ -866,7 +867,7 @@
type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> (that is, when it does not result from a user's activation of 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>
+ 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-event-target">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">
@@ -963,7 +964,7 @@
<p>Event operations can throw a <code>DOMException</code> as specified in their method descriptions.</p>
- <p class="note" id="note-eventexcpetion-removed"><strong>Note:</strong> the exception <em>EventException</em> introduced in <strong class="version">DOM Level 2</strong> is
+ <p class="note" id="note-eventexcpetion-removed"><strong>Note:</strong> The exception <em>EventException</em> introduced in <strong class="version">DOM Level 2</strong> is
removed in this specification as part of this specification's normative support of <a href="#references-WebIDL">Web IDL</a>. <em>EventException</em> formerly defined
an exception code <code>UNSPECIFIED_EVENT_TYPE_ERR</code> which is replaced in this specification by the use of a <code>DOMException</code> of type
<code>InvalidStateError</code>.</p>
@@ -989,7 +990,7 @@
</section>
</section> <!-- dom-event-architecture -->
- <!-- Section: Basic Event Interfaces ========================================================-->
+ <!-- Section 4: Basic Event Interfaces ========================================================-->
<section id="event-interfaces">
<h1>Basic Event Interfaces</h1>
@@ -1001,7 +1002,7 @@
<div class="figure" style="text-align: center">
<object type="image/svg+xml" data="images/event-inheritance.svg" width="960" height="230">
- <img src="images/event-inheritance.png" alt="graphical representation of the DOM3 Events interface inheritance" />
+ <img src="images/event-inheritance.png" alt="Graphical representation of the DOM3 Events interface inheritance" />
</object>
</div>
@@ -1072,7 +1073,7 @@
<p>Used to indicate the <a href="#event-phase">phase</a> of the event's current propagation path (capture, target, or bubble).
The event flow phases are defined in <a href="#event-flow">Event dispatch and DOM event flow</a>.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>0</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>0</code> (<code>NONE</code>).</p>
</dd>
<dt>readonly attribute boolean bubbles</dt>
@@ -1250,7 +1251,7 @@
<p class="note"><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 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>
+ (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-event-target">event targets</a> and target ancestors,
@@ -1263,7 +1264,7 @@
<p class="note"><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> allow a content author to register event listeners by the use of attributes, e.g.,
- <em><code>onclick="handleClick()"</code></em> (see [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] for further examples). Due to the
+ <code>onclick="handleClick()"</code> (see [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] for further examples). Due to the
language-specific details, this type of event listener registration is not defined in this specification. In general, many event types can be used as an attribute
in this way by adding the prefix <em><code>on-</code></em> to the event type name. Dispatching events to these listeners is expected to behave consistently with the
event registration and propagation defined in this specification, with the same interfaces, properties, and methods.</p>
@@ -1361,7 +1362,7 @@
<code>EventTarget.dispatchEvent()</code></a> MUST have a <code class="attribute-name"><a href="#events-event-type-isTrusted">isTrusted</a></code> attribute value
of <code>false</code>. See <a href="#trusted-events">trusted events</a> for more details.</p>
- <p class="note"><strong>Note:</strong> while a dispatch (triggered by <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a>) is in progress, calls to
+ <p class="note"><strong>Note:</strong> While a dispatch (triggered by <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a>) is in progress, calls to
<a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> are ignored (the method returns immediately without side-effects) and calls to
<a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> result in an exception.</p>
@@ -1434,6 +1435,8 @@
<dl class="idl" title="[NoInterfaceObject] interface DocumentEvent">
<dt>Event createEvent()</dt>
<dd>
+ <p class="intro-dom">Modified in DOM Level 3</p>
+
<p>Creates an event object of the type specified. Returns the newly created object.</p>
<p><strong>Exceptions:</strong>
@@ -1500,7 +1503,7 @@
</section> <!-- event-interfaces -->
- <!-- Section: The Events ========================================================-->
+ <!-- Section 5: The Events ========================================================-->
<section id="events-module">
<h1>Events Module</h1>
@@ -2109,7 +2112,7 @@
that loaded them is still accessible via the DOM. If this event type is dispatched, implementations are REQUIRED to dispatch this event at least on the <code>Document</code>
node.</p>
- <p class="note"><strong>Note:</strong> for legacy reasons, <a class="eventtype" href="#event-type-load"><code>load</code></a> events for resources inside
+ <p class="note"><strong>Note:</strong> For legacy reasons, <a class="eventtype" href="#event-type-load"><code>load</code></a> events for resources inside
the document (e.g., images) do not include the <a class="def" href="#glossary-defaultView">defaultView</a> in the propagation path in HTML implementations. See
[<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] for more information.</p>
</dd>
@@ -2536,27 +2539,27 @@
</ol>
<p class="note"><strong>Note:</strong> This specification does not define the behavior of focus events when interacting with methods such as <code>focus()</code> or
- <code>blur()</code>; see the relevant specifications where those methods are defined for such behavior.</p>
+ <code>blur()</code>. See the relevant specifications where those methods are defined for such behavior.</p>
</section>
<section id="events-focusevent-doc-focus">
<h4>Document Focus and Focus Context</h4>
<p>This event module includes event types for notification of changes in document <a class="def" href="#glossary-event-focus">focus</a>. Depending on the environment,
- document focus MAY be distinct from <a class="def" href="#glossary-user-agent">user agent</a> focus and operating system focus; this is referred to as focus context.
- For example, in a typical desktop browser environment, the operating system context focus might be on one of many different applications, one of which is the browser;
- when the browser has focus, the user can shift the application context focus (such as with the tab key) among different browser user interface fields (e.g., the
- Web site location bar, a search field, etc.) before or after achieving document focus; once the document itself has focus, sequential shifting of focus will step
+ document focus MAY be distinct from <a class="def" href="#glossary-user-agent">user agent</a> focus and operating system focus. This is referred to as focus context.
+ For example, in a typical desktop browser environment, the operating system context focus might be on one of many different applications, one of which is the browser.
+ When the browser has focus, the user can shift the application context focus (such as with the tab key) among different browser user interface fields (e.g., the
+ Web site location bar, a search field, etc.) before or after achieving document focus. Once the document itself has focus, sequential shifting of focus will step
through the focusable elements in the document. The event types defined in this specification deal exclusively with document focus, and the <a class="def" href="#glossary-event-target">
event target</a> identified in the event details MUST only be part of the document or documents in the window, never a part of the browser or operating system,
even when switching from one focus context to another.</p>
- <p>Normally, a document always has a focused element, even if it is the document element itself, and a persistent <a class="def" href="#glossary-event-focus-ring">focus
- ring</a>; when switching between focus contexts, the document's currently focused element and focus ring normally remain in their current state; for example,
+ <p>Normally, a document always has a focused element (even if it is the document element itself) and a persistent <a class="def" href="#glossary-event-focus-ring">focus
+ ring</a>. When switching between focus contexts, the document's currently focused element and focus ring normally remain in their current state. For example,
if a document has three focusable elements, with the second element focused, when a user changes operating system focus to another application and then back to
the browser, the second element will still be focused within the document, and tabbing will change the focus to the third element. A <a class="def" href="#glossary-host-language">
host language</a> MAY define specific elements which might receive focus, the conditions under which an element MAY receive focus, the means by which
focus MAY be changed, and the order in which the focus changes. For example, in some cases an element might be given focus by moving a pointer over it, while other
- circumstances might require a mouse click; some elements might not be focusable at all, and some might be focusable only by special means (clicking on the element),
+ circumstances might require a mouse click. Some elements might not be focusable at all, and some might be focusable only by special means (clicking on the element),
but not by tabbing to it. Documents MAY contain multiple focus rings. Other specifications MAY define a more complex focus model than is described in this specification,
including allowing multiple elements to have the current focus.</p>
</section>
@@ -2676,7 +2679,7 @@
focus. The focus MUST be given to the element before the dispatch of this event type. This event type MUST be dispatched after the event type <a class="eventtype"
href="#event-type-focus"><code>focus</code></a>.</p>
- <p class="warning" id="_7"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a> event type is defined in this
+ <p class="warning" id="_7"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMFocusIn"><code>DOMFocusIn</code></a> event type is defined in this
specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in favor
of the related event types <a class="eventtype" href="#event-type-focus"><code>focus</code></a> and <a class="eventtype" href="#event-type-focusIn"><code>focusin</code></a>.</p>
</dd>
@@ -2735,7 +2738,7 @@
focus. The focus MUST be taken from the element before the dispatch of this event type. This event type MUST be dispatched after the event type <a class="eventtype"
href="#event-type-blur"><code>blur</code></a>.</p>
- <p class="warning" id="_8"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a> event type is defined in
+ <p class="warning" id="_8"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMFocusOut"><code>DOMFocusOut</code></a> event type is defined in
this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type in
favor of the related event types <a class="eventtype" href="#event-type-blur"><code>blur</code></a> and <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a>.</p>
</dd>
@@ -3045,7 +3048,7 @@
<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>0</code> MUST indicate 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>
<li><code>2</code> MUST indicate the secondary button (in general, the right button, often used to display a context menu), if present.</li>
@@ -3229,7 +3232,7 @@
absolute position on a web page. Element C is a child of B, and B is a child of A in the DOM:</p>
<div class="figure" style="text-align: center">
- <img src="images/stacked-event-mouse-dispatch.png" alt="graphical representation of three stacked elements all on top of each other. The bottom element is labeled A and the top element is C" title="graphical representation of three stacked elements all on top of each other, with the pointing device moving over the stack." />
+ <img src="images/stacked-event-mouse-dispatch.png" alt="Graphical representation of three stacked elements all on top of each other. The bottom element is labeled A and the top element is C" title="graphical representation of three stacked elements all on top of each other, with the pointing device moving over the stack." />
</div>
<p>When the pointing device is moved from outside the element stack to the element labeled C and then moved out again, the following series of events occur:</p>
@@ -3249,7 +3252,7 @@
<li><a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a> (element <em>A</em>)</li>
</ol>
- <p class="note"><strong>Note:</strong> that <code>mouseover</code>/<code>mouseout</code> are only fired once, while <code>mouseenter</code>/<code>mouseleave</code>
+ <p class="note"><strong>Note:</strong> The <code>mouseover</code>/<code>mouseout</code> events are only fired once, while <code>mouseenter</code>/<code>mouseleave</code>
events are fired three times.</p>
<p>The following is the typical sequence of events when a button associated with a pointing device (e.g., a mouse button or trackpad) is pressed and released over
@@ -3290,8 +3293,8 @@
<p>If the target element is removed from the DOM as the result of a <a class="eventtype" href="#event-type-mousedown">
<code>mousedown</code></a> event, no events for that element will be dispatched for <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>,
<a class="eventtype" href="#event-type-click"><code>click</code></a>, or <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>, nor any default
- activation events; however, the <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> event will still be dispatched on the element that is exposed
- to the mouse after the removal of the initial target element. Similarly, if the target element is removed from the DOM during the dispatch of a <a class="eventtype"
+ activation events. However, the <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> event will still be dispatched on the element that is exposed
+ to the mouse after the removal of the initial target element. Similarly, if the target element is removed from the DOM during the dispatch of a <a class="eventtype"
href="#event-type-mouseup"><code>mouseup</code></a> event, the <a class="eventtype" href="#event-type-click"><code>click</code></a> and subsequent events will
not be dispatched.</p>
</div>
@@ -3379,11 +3382,11 @@
<div class="example">
<div class="example-title">Example</div>
- <p>If a user mouses down on a text node child of a <p> element which has been styled with
- a large line-height, shifts the mouse slightly such that it is no longer over an area containing text but is still within the containing block of that <p>
+ <p>If a user mouses down on a text node child of a <code><p></code> element which has been styled with
+ a large line-height, shifts the mouse slightly such that it is no longer over an area containing text but is still within the containing block of that <code><p></code>
element (i.e., the pointer is between lines of the same text block, but not over the text node per se), then subsequently mouses up, this will likely still trigger
a <a class="eventtype" href="#event-type-click"><code>click</code></a> event (if it falls within the normal temporal hysteresis for a <a class="eventtype" href="#event-type-click">
- <code>click</code></a>), since the user has stayed within the scope of the same element; user-agent-generated mouse events are not dispatched on text nodes.
+ <code>click</code></a>), since the user has stayed within the scope of the same element. Note that user-agent-generated mouse events are not dispatched on text nodes.
</p>
</div>
@@ -4341,7 +4344,7 @@
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 the <a class="def" href="#glossary-empty-string">empty string</a>.</p>
- <p class="note"><strong>Note:</strong> the <code>char</code> attribute is not related to the legacy <code>charCode</code> attribute and does
+ <p class="note"><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>
<p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>""</code> (the empty string).</p>
@@ -4354,7 +4357,7 @@
<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 <a href="#key-Unidentified"><code class="key">'Unidentified'</code></a>.</p>
- <p class="note"><strong>Note:</strong> the <code>key</code> attribute is not related to the legacy <code>keyCode</code> attribute and does not have the same set of values.</p>
+ <p class="note"><strong>Note:</strong> The <code>key</code> attribute is not related to the legacy <code>keyCode</code> attribute and does not have the same set of values.</p>
<p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>""</code> (the empty string).</p>
</dd>
@@ -4498,12 +4501,12 @@
</ol>
<p class="note"><strong>Note:</strong> Typically, any <a class="def" href="#glossary-default-action">default actions</a> associated with any particular
- key are completed before the <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event is dispatched; this might delay the <a class="eventtype"
+ key are completed before the <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event is dispatched. This might delay the <a class="eventtype"
href="#event-type-keyup"><code>keyup</code></a> event slightly (though this is not likely to be a perceptible delay).</p>
- <p>The <a class="def" href="#glossary-event-target">event target</a> of a key event is the currently focused element which is processing the keyboard activity; this
+ <p>The <a class="def" href="#glossary-event-target">event target</a> of a key event is the currently focused element which is processing the keyboard activity. This
is often an HTML <code>input</code> element or a textual element which is editable, but MAY be an element defined by the <a class="def" href="#glossary-host-language">
- host language</a> to accept keyboard input for non-text purposes, such as the activation of a hotkey or trigger of some other behavior; if no suitable element
+ host language</a> to accept keyboard input for non-text purposes, such as the activation of a hotkey or trigger of some other behavior. If no suitable element
is in focus, the event target will be the root element.</p>
<p class="note"><strong>Note:</strong> The <a class="def" href="#glossary-event-target">event target</a> might change between different key events;
@@ -4587,17 +4590,17 @@
<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 MUST be to dispatch a <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a>
+ <li>If the key is associated with a character, the default action MUST be to dispatch a <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a>
event; in the case where the key which is associated with multiple characters (such as with a macro or certain sequences of dead keys), the default action MUST
be to dispatch one <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event for each character</li>
- <li>if the key is associated with a <a class="def" href="#glossary-text-composition-system">text composition system</a>, the default action MUST be to launch that
+ <li>If the key is associated with a <a class="def" href="#glossary-text-composition-system">text composition system</a>, the default action MUST be to launch that
system</li>
- <li>if the key is the <a href="#key-Tab"><code class="key">'Tab'</code></a> key, the default action MUST be to shift the document focus from the currently focused
+ <li>If the key is the <a href="#key-Tab"><code class="key">'Tab'</code></a> key, the default action MUST be to shift the document focus from the currently focused
element (if any) to the new focused element, as described in <a href="#events-focusevent">Focus Event Types</a></li>
- <li>if the key is the <a href="#key-Enter"><code class="key">'Enter'</code></a> or <a href="#key-Spacebar"><code class="key">'Space'</code></a> key and the
+ <li>If the key is the <a href="#key-Enter"><code class="key">'Enter'</code></a> or <a href="#key-Spacebar"><code class="key">'Space'</code></a> key and the
current focus is on a state-changing element, the default action MUST be to dispatch a <a class="eventtype" href="#event-type-click"><code>click</code></a> event,
and a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event if that event type is supported by the <a class="def" href="#glossary-user-agent">
user agent</a> (refer to <a href="#event-flow-activation">activation triggers and behavior</a> for more details)</li>
@@ -4605,7 +4608,7 @@
<p>If this event is canceled, the associated event types MUST NOT be dispatched, and the associated actions MUST NOT be performed.</p>
- <p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup">
+ <p class="note"><strong>Note:</strong> The <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keyup">
<code>keyup</code></a> events are traditionally associated with detecting any key, not just those which produce a <a class="def" href="#glossary-character-value">character
value</a>.</p>
</dd>
@@ -4683,10 +4686,10 @@
MUST be dispatched after the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event and before the <a class="eventtype" href="#event-type-keyup">
<code>keyup</code></a> event associated with the same key.</p>
- <p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event is traditionally associated with detecting a
+ <p class="note"><strong>Note:</strong> The <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event is traditionally associated with detecting a
<a class="def" href="#glossary-character-value">character value</a> rather than a physical key, and might not be available on all keys in some configurations.</p>
- <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event type is defined in this
+ <p class="warning"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event type is defined in this
specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type. When
in editing contexts, authors can subscribe to the "input" event defined in [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] instead.</p>
</dd>
@@ -4913,9 +4916,9 @@
system</a> is enabled and a new composition session is about to begin (or has begun, depending on the <a class="def" href="#glossary-text-composition-system">text composition
system</a>) 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 <a class="eventtype"><code>keydown</code></a> event,
- but speech or handwriting recognition systems MAY send this event type without keyboard events. Some implemenations MAY populate the
+ but speech or handwriting recognition systems MAY send this event type without keyboard events. Some implementations 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>
+ 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 MUST be the <a class="def" href="#glossary-empty-string">empty string</a>.</p>
<p>This event MUST be dispatched immediately before a <a class="def" href="#glossary-text-composition-system">text composition system</a> begins a new composition session, and
@@ -5059,7 +5062,7 @@
<p>The mutation and mutation name event modules are designed to allow notification of any changes to the structure of a document, including attribute, text, or name
modifications.</p>
- <p class="note"><strong>Note:</strong> none of the event types associated with the <code>MutationEvent</code> interface are designated as cancelable. This stems from
+ <p class="note"><strong>Note:</strong> None of the event types associated with the <code>MutationEvent</code> interface are designated as cancelable. This stems from
the fact that it is very difficult to make use of existing DOM interfaces which cause document modifications if any change to the document might or might not take
place due to cancelation of the resulting event. Although this is still a desired capability, it was decided that it would be better left until the addition of
transactions into the DOM.</p>
@@ -5260,7 +5263,7 @@
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"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a> event type is defined
+ <p class="warning"><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>
</dl>
@@ -5321,7 +5324,7 @@
have been modified, but the node itself has not been inserted or deleted. The <a class="def" href="#glossary-event-target">event target</a> of this event MUST
be the <code>CharacterData</code> node or the <code>ProcessingInstruction</code> node.</p>
- <p class="warning" id="_45"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a>
+ <p class="warning" id="_45"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</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>
@@ -5387,10 +5390,10 @@
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-event-target">
event target</a> of this event MUST be the node being inserted.</p>
- <p class="note" id="DOMNodeInserted-attr"><strong>Note:</strong> for detecting attribute insertion, use the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
+ <p class="note" id="DOMNodeInserted-attr"><strong>Note:</strong> For detecting attribute insertion, use the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
event type instead.</p>
- <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeInserted"><code>DOMNodeInserted</code></a> event type is defined in this specification
+ <p class="warning"><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>
@@ -5456,7 +5459,7 @@
event target</a> of this event MUST 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"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeInsertedIntoDocument"><code>DOMNodeInsertedIntoDocument</code></a>
+ <p class="warning"><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>
@@ -5522,10 +5525,10 @@
(see <a href="#DOMNodeRemoved-attr">note</a> below). This event MUST be dispatched before the removal takes place. The <a class="def" href="#glossary-event-target">
event target</a> of this event MUST be the node being removed.</p>
- <p class="note" id="DOMNodeRemoved-attr"><strong>Note:</strong> for reliably detecting attribute removal, use the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
+ <p class="note" id="DOMNodeRemoved-attr"><strong>Note:</strong> For reliably detecting attribute removal, use the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
event type instead.</p>
- <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeRemoved"><code>DOMNodeRemoved</code></a> event type is defined
+ <p class="warning"><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>
@@ -5592,10 +5595,10 @@
target</a> of this event type MUST 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"><strong>Note:</strong> for reliably detecting attribute removal, use the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
+ <p class="note"><strong>Note:</strong> For reliably detecting attribute removal, use the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
event type instead.</p>
- <p class="warning"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMNodeRemovedFromDocument"><code>DOMNodeRemovedFromDocument</code></a>
+ <p class="warning"><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>
@@ -5660,7 +5663,7 @@
be used to accommodate multiple changes which occur either simultaneously or in rapid succession. The target of this event MUST 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"><strong>Warning!</strong> the <a class="eventtype" href="#event-type-DOMSubtreeModified"><code>DOMSubtreeModified</code></a> event type is defined in this
+ <p class="warning"><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>
@@ -5671,7 +5674,7 @@
</section> <!-- events-module -->
- <!-- Section: Keyboard and key values ========================================================-->
+ <!-- Section 6: Keyboard and key values ========================================================-->
<section id="keys">
<h1>Keyboard events and key values</h1>
@@ -5720,7 +5723,7 @@
'F'</code> key (the key marked with the glyph <code class="glyph">'F'</code>), will produce the character value <code class="char">'f'</code> when pressing
without an active modifier key (<code class="key">'Shift'</code>) or modifier state (<code class="key">'CapsLock'</code>).</p>
- <p class="note"><strong>Note:</strong> the key legends for function keys do not normally produce any characters, although the symbol might have a Unicode equivalent; for example, the <code
+ <p class="note"><strong>Note:</strong> The key legends for function keys do not normally produce any characters, although the symbol might have a Unicode equivalent; for example, the <code
class="key">'Shift'</code> key might bear the symbol <code class="glyph">⇧</code>, which has the <a class="def" href="#glossary-unicode-code-point">Unicode code point</a> <code class="char">
'\u21E7'</code>, but pressing the <code class="key">'Shift'</code> key will not produce this character value, and there is no <a class="def" href="#glossary-unicode-code-point">
Unicode code point</a> for <code class="key">'Shift'</code>.</p>
@@ -5777,7 +5780,7 @@
<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
+ of Unicode characters in the range <code class="char">'\u0061'</code>..<code class="char">'\u007A'</code> to the number keys <code>2</code> through <code>9</code>, as a common layout appropriate to some
international uses.</p>
<p class="note"><strong>Note:</strong> This keypad layout, and in particular the distribution of letters is for English devices, and will not match the keypads
@@ -6036,7 +6039,7 @@
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 <q>legal</q> base character is entered.</p>
- <p class="note"><strong>Note:</strong> the MacOS and Linux operating systems use input methods to process <a class="def" href="#glossary-dead-key">dead keys</a>.)</p>
+ <p class="note"><strong>Note:</strong> The MacOS and Linux operating systems use input methods to process <a class="def" href="#glossary-dead-key">dead keys</a>.)</p>
<p>The <a class="def" href="#glossary-dead-key">dead keys</a> are represented in the key values set using combining diacritical marks. While Unicode combining characters
always follow the handwriting sequence, with the combining character trailing the corresponding letter, typical deadkey input MAY reverse the sequence, with the
@@ -6180,8 +6183,8 @@
<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>
- <p class="note"><strong>Note:</strong> keys with <a class="def" href="#glossary-ime">input method editor</a> functions are not restricted to that purpose, and can have other device- or implementation-specific
- purposes, as well.</p>
+ <p class="note"><strong>Note:</strong> Keys with <a class="def" href="#glossary-ime">input method editor</a> functions are not restricted to that purpose, and can have other device- or implementation-specific
+ purposes.</p>
</div>
</section>
@@ -7746,7 +7749,7 @@
</section>
</section>
- <!-- Appendix: Initializing events ========================================================-->
+ <!-- Appendix A: Initializing events ========================================================-->
<section id="new-event-interface-initializers" class="appendix">
<h1>Initializing New Event Interfaces</h1>
@@ -8164,7 +8167,7 @@
</section>
</section>
- <!-- Appendix: Legacy key attributes ========================================================-->
+ <!-- Appendix B: Legacy key attributes ========================================================-->
<section id="legacy-key-attributes">
<h1>Legacy key attributes: <code class="attribute-name">keyCode</code>, <code class="attribute-name">charCode</code>, and <code class="attribute-name">which</code></h1>
@@ -8475,7 +8478,7 @@
</section>
</section>
- <!-- Appendix: Extending events ========================================================-->
+ <!-- Appendix C: Extending events ========================================================-->
<section id="extending_events">
<h1>Extending Events</h1>
<p><em>This section is informative</em></p>
@@ -8568,7 +8571,7 @@
</section>
</section>
- <!-- Appendix: Security considerations ========================================================-->
+ <!-- Appendix D: Security considerations ========================================================-->
<section id="security-considerations-Security">
<h1>Security Considerations</h1>
@@ -8595,7 +8598,7 @@
events to nodes that attempt to embed resources on the local network.</p>
</section>
- <!-- Appendix: Changes ========================================================-->
+ <!-- Appendix E: Changes ========================================================-->
<section id="changes-Changes">
<h1>Changes</h1>
@@ -8689,7 +8692,7 @@
</section>
</section>
- <!-- Appendix: Acknowledgements ========================================================-->
+ <!-- Appendix F: Acknowledgements ========================================================-->
<section id="acknowledgements-contributors">
<h1>Acknowledgements</h1>
@@ -8745,7 +8748,7 @@
</section>
</section>
- <!-- Appendix: References ========================================================-->
+ <!-- Appendix G: References ========================================================-->
<section id="references-role-references">
<h1>References</h1>