--- a/html/DOM3-Events.html Tue Jun 04 13:24:48 2013 -0700
+++ b/html/DOM3-Events.html Tue Jun 04 13:27:25 2013 -0700
@@ -92,15 +92,15 @@
<p id="this-document-is-produced-by-the-web-app">This document is produced by the <a href="http://www.w3.org/2008/webapps/">Web Applications WG</a>, part of the <a
href="http://www.w3.org/2006/rwc/Activity">Rich Web Clients Activity</a> in the W3C <a href="http://www.w3.org/Interaction/">Interaction Domain</a>. It is expected
that this document will progress along the W3C's Recommendation track. Publication as a Working Draft does not imply endorsement by the W3C Membership. This is
- a draft document and <span class="may">may</span> be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other
+ a draft document and MAY be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other
than work in progress.</p>
<p id="latest-editors-draft"><strong>You can find the latest <a href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html">Editor's Draft</a> of
this document in the <a href="http://dev.w3.org/">W3C's CVS repository</a>, which is updated on a regular basis.</strong></p>
- <p id="unstable"><strong class="redNote">Implementers <span class="should">should</span> be aware that this document is not stable.</strong> Implementers who are not
+ <p id="unstable"><strong class="redNote">Implementers should be aware that this document is not stable.</strong> Implementers who are not
taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this document
- before it eventually reaches the Candidate Recommendation stage <span class="should">should</span> join the aforementioned mailing lists and take part in the discussions.</p>
+ 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 ========================================================-->
@@ -121,19 +121,18 @@
<h2>Conformance</h2>
<p><strong>This section is normative.</strong></p>
- <p>Within this specification, the key words <q><span class="must">MUST</span></q>, <q><span class="mustnot">MUST NOT</span></q>, <q><span class="required">REQUIRED</span></q>,
- <q><span class="shall">SHALL</span></q>, <q><span class="shallnot">SHALL NOT</span></q>, <q><span class="should">SHOULD</span></q>, <q><span class="shouldnot">SHOULD NOT</span></q>,
- <q><span class="recommended">RECOMMENDED</span></q>, <q><span class="may">MAY</span></q>, and <q><span class="optional">OPTIONAL</span></q> are to be interpreted as described in
- <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a> [<a href="#ref-rfc2119">RFC2119</a>]. However, for readability, these words do not necessarily appear in uppercase in this
- specification.</p>
+ <p>Within this specification, the key words <q>MUST</q>, <q>MUST NOT</q>, <q>REQUIRED</q>,
+ <q>SHALL</q>, <q>SHALL NOT</q>, <q>SHOULD</q>, <q>SHOULD NOT</q>,
+ <q>RECOMMENDED</q>, <q>MAY</q>, and <q>OPTIONAL</q> are to be interpreted as described in
+ <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a> [<a href="#ref-rfc2119">RFC2119</a>].</p>
<p>This specification is to be understood in the context of the DOM Level 3 Core specification [<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>]
and the general considerations for DOM implementations apply. For example, handling of <a class="def" href="#glossary-namespaceURI">namespace URIs</a> is discussed in
<a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations"><em>XML Namespaces</em></a>. For additional information about
<a class="normative" href="http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance"><em>conformance</em></a>, please see the DOM Level 3 Core specification
[<cite><a class="normative" href="#references-DOMCore">DOM3 Core</a></cite>]. A <a class="def" href="#glossary-user-agent">user agent</a> is not required to conform
- to the entirety of another specification in order to conform to this specification, but it <span class="must">must</span> conform to the specific parts of any other specification which are called
- out in this specification (e.g., a conforming DOM3 Events <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> support the <code>DOMString</code> data type as defined
+ to the entirety of another specification in order to conform to this specification, but it MUST conform to the specific parts of any other specification which are called
+ out in this specification (e.g., a conforming DOM3 Events <a class="def" href="#glossary-user-agent">user agent</a> MUST support the <code>DOMString</code> data type as defined
in <a href="#references-WebIDL">Web IDL</a>, but need not support every method or data type defined in <a href="#references-WebIDL">Web IDL</a> in order to conform
to DOM3 Events).</p>
@@ -145,9 +144,9 @@
Technology) application, or other similar program), conforms to DOM Level 3 Events if it supports the Core module defined in [<cite><a class="normative" href="#references-DOMCore">DOM3
Core</a></cite>], the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism, all the interfaces and events with their associated methods, attributes,
and semantics defined in this specification with the exception of those marked as <a class="def" href="#glossary-deprecated">deprecated</a> (a conforming user agent
- <span class="may">may</span> implement the deprecated interfaces, events, or APIs for backwards compatibility, but is not required to do so in order to be conforming), and the complete
+ MAY implement the deprecated interfaces, events, or APIs for backwards compatibility, but is not required to do so in order to be conforming), and the complete
set of <a class="def" href="#glossary-character-value">character values</a> and <a class="def" href="#glossary-key-value">key values</a> in the <a href="#key-values">
- Key Values Set</a> (subject to platform availability), as well as all other normative requirements defined in this specification. A conforming browser <span class="must">must</span>
+ Key Values Set</a> (subject to platform availability), as well as all other normative requirements defined in this specification. A conforming browser MUST
<a class="def" href="#glossary-dispatch">dispatch</a> events appropriate to the given <a href="#events-EventTarget">EventTarget</a> when the conditions defined
for that <a class="def" href="#glossary-event-type">event type</a> have been met.</p>
@@ -157,38 +156,38 @@
the interfaces and its related <a class="def" href="#glossary-event-type">event types</a> specified in the <a href="#events-module">Events Module</a>, and to each
event interface if it implements that interface and its related <a class="def" href="#glossary-event-type">event types</a>.</span></p>
- <p><span id="conform-script">A conforming browser <span class="must">must</span> support scripting, declarative interactivity, or some other means of detecting and dispatching events in the manner
- described by this specification, and <span class="must">must</span> support the APIs specified for that <a class="def" href="#glossary-event-type">event type</a>.</span></p>
-
- <p>In addition to meeting all other conformance criteria, a conforming browser <span class="may">may</span> implement features of this specification marked as <a class="def" href="#glossary-deprecated">
+ <p><span id="conform-script">A conforming browser MUST support scripting, declarative interactivity, or some other means of detecting and dispatching events in the manner
+ described by this specification, and MUST support the APIs specified for that <a class="def" href="#glossary-event-type">event type</a>.</span></p>
+
+ <p>In addition to meeting all other conformance criteria, a conforming browser MAY implement features of this specification marked as <a class="def" href="#glossary-deprecated">
deprecated</a>, for backwards compatibility with existing content, but such implementation is discouraged.</p>
- <p>A conforming browser <span class="may">may</span> also support features not found in this specification, but which use the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism,
- interfaces, events, or other features defined in DOM Level 3 Events, and <span class="may">may</span> implement additional interfaces and <a class="def" href="#glossary-event-type">event types</a>
+ <p>A conforming browser MAY also support features not found in this specification, but which use the <a href="#event-flow">Event dispatch and DOM event flow</a> mechanism,
+ interfaces, events, or other features defined in DOM Level 3 Events, and MAY implement additional interfaces and <a class="def" href="#glossary-event-type">event types</a>
appropriate to that implementation. Such features can be later standardized in future specifications.</p>
- <p>A browser which does not conform to all required portions of this specification <span class="mustnot">must not</span> claim conformance to DOM Level 3 Events. Such an implementation which
- does conform to portions of this specification <span class="may">may</span> claim conformance to those specific portions.</p>
-
- <p>A conforming browser <span class="must">must</span> also be a <i>conforming implementation</i> of the IDL fragments in this specification, as described in the Web IDL specification. <a
+ <p>A browser which does not conform to all required portions of this specification MUST NOT claim conformance to DOM Level 3 Events. Such an implementation which
+ does conform to portions of this specification MAY claim conformance to those specific portions.</p>
+
+ <p>A conforming browser MUST also be a <i>conforming implementation</i> of the IDL fragments in this specification, as described in the Web IDL specification. <a
href="#references-WebIDL">[WEBIDL]</a></p>
</dd>
<dt id="conf-author-tools">Authoring tools</dt>
<dd>
<p>A content authoring tool conforms to DOM Level 3 Events if it produces content which uses the <a class="def" href="#glossary-event-type">event types</a> and <a
- href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. A content authoring tool <span class="mustnot">must not</span> claim
+ href="#event-flow">Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. A content authoring tool MUST NOT claim
conformance to DOM Level 3 Events for content it produces which uses features of this specification marked as <a class="def" href="#glossary-deprecated">deprecated</a>
- in this specification. A conforming content authoring tool <span class="should">should</span> provide to the content author a means to use all <a class="def" href="#glossary-event-type">event
+ in this specification. A conforming content authoring tool SHOULD provide to the content author a means to use all <a class="def" href="#glossary-event-type">event
types</a> and interfaces appropriate to all <a class="def" href="#glossary-host-language">host languages</a> in the content document being produced.</p>
</dd>
<dt id="conf-authors">Content authors and content</dt>
<dd>
<p>A content author creates conforming DOM Level 3 Events content if that content uses the <a class="def" href="#glossary-event-type">event types</a> and <a href="#event-flow">
- Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. A content author <span class="shouldnot">should not</span> use features of this specification
- marked as <a class="def" href="#glossary-deprecated">deprecated</a>, but <span class="should">should</span> rely instead upon replacement mechanisms defined in this specification and elsewhere.
- Conforming content <span class="must">must</span> use the semantics of the interfaces and <a class="def" href="#glossary-event-type">event types</a> as described in this specification.</p>
+ Event dispatch and DOM event flow</a> model, consistent in a manner as defined in this specification. A content author SHOULD NOT use features of this specification
+ marked as <a class="def" href="#glossary-deprecated">deprecated</a>, but SHOULD rely instead upon replacement mechanisms defined in this specification and elsewhere.
+ Conforming content MUST use the semantics of the interfaces and <a class="def" href="#glossary-event-type">event types</a> as described in this specification.</p>
<p class="note"><strong>Authoring Note: </strong>Content authors are advised to follow best practices as described in <a href="http://www.w3.org/TR/WAI-WEBCONTENT/">
accessibility</a> and <a href="http://www.w3.org/standards/techs/i18n">internationalization</a> guideline specifications.</p>
@@ -204,13 +203,13 @@
<p>A specification or <a class="def" href="#glossary-host-language">host language</a> conforms specifically to the DOM Level 3 Events Module if it references and uses the interfaces and
its related <a class="def" href="#glossary-event-type">event types</a> specified in the <a href="#events-module">Events Module</a>, and to each event interface
- if it references and uses that interface and its related <a class="def" href="#glossary-event-type">event types</a>. A conforming specification <span class="may">may</span>
- define additional interfaces and <a class="def" href="#glossary-event-type">event types</a> appropriate to that specification, or <span class="may">may</span> extend the DOM Level 3 Events
+ if it references and uses that interface and its related <a class="def" href="#glossary-event-type">event types</a>. A conforming specification MAY
+ define additional interfaces and <a class="def" href="#glossary-event-type">event types</a> appropriate to that specification, or MAY extend the DOM Level 3 Events
interfaces and <a class="def" href="#glossary-event-type">event types</a> in a manner that does not contradict or conflict with the definitions of those interfaces
and <a class="def" href="#glossary-event-type">event types</a> in this specification.</p>
- <p>Specifications or <a class="def" href="#glossary-host-language">host languages</a> which reference DOM Level 3 Events <span class="shouldnot">should not</span> use or recommend features of this
- specification marked as <a class="def" href="#glossary-deprecated">deprecated</a>, but <span class="should">should</span> use or recommend the indicated replacement for that the feature (if available).</p>
+ <p>Specifications or <a class="def" href="#glossary-host-language">host languages</a> which reference DOM Level 3 Events SHOULD NOT use or recommend features of this
+ specification marked as <a class="def" href="#glossary-deprecated">deprecated</a>, but SHOULD use or recommend the indicated replacement for that the feature (if available).</p>
</dd>
</dl>
</section> <!-- dom-events-conformance -->
@@ -275,8 +274,8 @@
<dl id="glossary-list">
<dt id="glossary-activation-behavior"><dfn>activation behavior</dfn></dt>
<dd>The action taken when an <a class="def" href="#glossary-event">event</a>, typically initiated by users through an input device, causes an element to fulfill a
- defined task. The task <span class="may">may</span> be defined for that element by the <a class="def" href="#glossary-host-language">host language</a>, or by
- author-defined variables, or both. The default task for any given element <span class="may">may</span> be a generic action, or <span class="may">may</span> be
+ defined task. The task MAY be defined for that element by the <a class="def" href="#glossary-host-language">host language</a>, or by
+ author-defined variables, or both. The default task for any given element MAY be a generic action, or MAY be
unique to that element. For example, the activation behavior of an HTML or SVG <code><a></code> element is to cause the
<a class="def" href="#glossary-user-agent">user agent</a> to traverse the link specified in the <code>href</code> attribute, with the further optional parameter
of specifying the browsing context for the traversal (such as the current window or tab, a named window, or a new window); the activation behavior of an HTML
@@ -322,7 +321,7 @@
<dt id="glossary-current-event-target"><dfn>current event target</dfn></dt>
<dd>In an event flow, the current event target is the object associated with the <a class="def" href="#glossary-event-handler">event handler</a> that is currently being
- dispatched. This object <span class="may">may</span> be the <a href="#glossary-event-target">event target</a> itself or one of its ancestors. The current event target changes as the
+ dispatched. This object MAY be the <a href="#glossary-event-target">event target</a> itself or one of its ancestors. The current event target changes as the
<a class="def" href="#glossary-event">event</a> propagates from object to object through the various <a class="def" href="#glossary-phase">phases</a> of the event flow.
The current event target is the value of the <a href="#events-event-type-currentTarget"><code>Event.currentTarget</code></a> attribute.</dd>
@@ -331,11 +330,11 @@
such as a character with diacritical marks (e.g., <code>ö</code>, <code>é</code>, <code>â</code>).</dd>
<dt id="glossary-default-action"><dfn>default action</dfn></dt>
- <dd>A <a class="def" href="#glossary-default-action">default action</a> is an <span class="optional">optional</span> supplementary behavior that an implementation
- <span class="must">must</span> perform in combination with the dispatch of the event object. Each event type definition, and each specification, defines the
- <a class="def" href="#glossary-default-action">default action</a> for that event type, if it has one. An instance of an event <span class="may">may</span> have more than
+ <dd>A <a class="def" href="#glossary-default-action">default action</a> is an OPTIONAL supplementary behavior that an implementation
+ MUST perform in combination with the dispatch of the event object. Each event type definition, and each specification, defines the
+ <a class="def" href="#glossary-default-action">default action</a> for that event type, if it has one. An instance of an event MAY have more than
one <a class="def" href="#glossary-default-action">default action</a> under some circumstances, such as when associated with an
- <a class="def" href="#glossary-activation-trigger">activation trigger</a>. A <a class="def" href="#glossary-default-action"> default action</a> <span class="may">may</span>
+ <a class="def" href="#glossary-activation-trigger">activation trigger</a>. A <a class="def" href="#glossary-default-action"> default action</a> MAY
be cancelled through the invocation of the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method. For more details, see
<a href="#event-flow-default-cancel">Default actions and cancelable events</a>.</dd>
@@ -354,11 +353,11 @@
document, respectively.</dd>
<dt id="glossary-deprecated"><dfn>deprecated</dfn></dt>
- <dd>Features marked as deprecated are included in the specification as reference to older implementations or specifications, but are <span class="optional">optional</span>
- and discouraged. Only features which have existing or in-progress replacements <span class="must">must</span> be deprecated in this specification. Implementations
- which do not already include support for the feature <span class="may">may</span> implement deprecated features for reasons of backwards compatibility with existing
- content, but content authors creating content <span class="shouldnot">should not</span> use deprecated features, unless there is no other way to solve a use case.
- Other specifications which reference this specification <span class="shouldnot">should not</span> use deprecated features, but <span class="should">should</span>
+ <dd>Features marked as deprecated are included in the specification as reference to older implementations or specifications, but are OPTIONAL
+ and discouraged. Only features which have existing or in-progress replacements MUST be deprecated in this specification. Implementations
+ which do not already include support for the feature MAY implement deprecated features for reasons of backwards compatibility with existing
+ content, but content authors creating content SHOULD NOT use deprecated features, unless there is no other way to solve a use case.
+ Other specifications which reference this specification SHOULD NOT use deprecated features, but SHOULD
point instead to the replacements of which the feature is deprecated in favor. Features marked as deprecated in this specification are expected to be dropped from
future specifications.</dd>
@@ -439,8 +438,8 @@
<dt id="glossary-event-focus-ring"><dfn>focus ring</dfn></dt>
<dd>A focus ring is a an ordered set of <a class="def" href="#glossary-event-focus">focus</a> targets within a document. A <a class="def" href="#glossary-host-language">
- host language</a> <span class="may">may</span> 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 <span class="may">may</span> contain multiple focus rings, or conditional focus rings. Typically, for document-order
+ 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>
<dt id="glossary-fire"><dfn>fire</dfn></dt>
@@ -461,7 +460,7 @@
<dt id="glossary-input-method-editor"><dfn>input method editor</dfn></dt>
<dd>An <em>input method editor</em> (IME), also known as a <em>front end processor</em>, is an application that performs the conversion between keystrokes and ideographs
or other characters, usually by user-guided dictionary lookup, often used in East Asian languages (e.g., Chinese, Japanese, Korean). An <a class="def" href="#glossary-ime">
- IME</a> <span class="may">may</span> also be used for dictionary-based word completion, such as on mobile devices. See <a href="#keys-IME">Input Method Editors</a> for treatment of
+ IME</a> MAY also be used for dictionary-based word completion, such as on mobile devices. See <a href="#keys-IME">Input Method Editors</a> for treatment of
IMEs in this specification. See also <a class="def" href="#glossary-text-composition-system">text composition system</a>.</dd>
<dt id="glossary-key-value"><dfn>key value</dfn></dt>
@@ -504,7 +503,7 @@
sequentially on the way to and back from the <a class="def" href="#glossary-event-target">event target</a>. As the event propagates, each <a class="def"
href="#glossary-current-event-target">current event target</a> in the propagation path is in turn set as the <a href="#events-event-type-currentTarget"><code>Event.currentTarget</code></a>.
The propagation path is initially composed of one or more <a class="def" href="#glossary-event-phase">event phases</a> as defined by the <a class="def" href="#glossary-event-type">
- event type</a>, but <span class="may">may</span> be interrupted. Also known as an <em>event target chain</em>.</dd>
+ event type</a>, but MAY be interrupted. Also known as an <em>event target chain</em>.</dd>
<dt id="glossary-qwerty"><dfn>QWERTY</dfn></dt>
<dd>QWERTY (pronounced <q>ˈkwɜrti</q>) is a common keyboard layout, so named because the first five character keys on the top row of letter keys are Q,
@@ -514,8 +513,8 @@
<dd>The first element node of a document, of which all other elements are children; the document element.</dd>
<dt id="events-WheelEvent-rotation"><dfn>rotation</dfn></dt>
- <dd>An indication of incremental change on an input device using the <a href="#events-wheelevents">WheelEvent</a> interface. On some devices this <span class="may">may</span> be a literal
- rotation of a wheel, while on others, it <span class="may">may</span> be movement along a flat surface, or pressure on a particular button.</dd>
+ <dd>An indication of incremental change on an input device using the <a href="#events-wheelevents">WheelEvent</a> interface. On some devices this MAY be a literal
+ rotation of a wheel, while on others, it MAY be movement along a flat surface, or pressure on a particular button.</dd>
<dt id="glossary-text-composition-system"><dfn>text composition system</dfn></dt>
<dd>A software component that interprets some form of alternate input (such as a <a class="def" href="#glossary-ime">input method editor</a>, a speech processor, or
@@ -526,7 +525,7 @@
See the description of the <a href="#target-phase">target phase</a> in the context of event flow for more details.</dd>
<dt id="glossary-topmost-event-target"><dfn>topmost event target</dfn></dt>
- <dd>The <a class="def" href="#glossary-topmost-event-target">topmost event target</a> <span class="must">must</span> be the element highest in the rendering order which is capable of being
+ <dd>The <a class="def" href="#glossary-topmost-event-target">topmost event target</a> MUST be the element highest in the rendering order which is capable of being
an <a class="def" href="#glossary-event-target">event target</a>. In graphical user interfaces this is the element under the user's pointing device. A user
interface's <q>hit testing</q> facility is used to determine the target. For specific details regarding hit testing and stacking order, refer to the
<a class="def" href="#glossary-host-language">host language</a>.</dd>
@@ -571,7 +570,7 @@
<dt id="glossary-user-agent"><dfn>user agent</dfn></dt>
<dd>A program, such as a browser or content authoring tool, normally running on a client machine, which acts on a user's behalf in retrieving, interpreting, executing,
- presenting, or creating content. Users <span class="may">may</span> act on the content using different user agents at different times, for different purposes. See the <a href="#conf-interactive-ua">
+ presenting, or creating content. Users MAY act on the content using different user agents at different times, for different purposes. See the <a href="#conf-interactive-ua">
Web browsers and other dynamic or interactive user agents</a> and <a href="#conf-author-tools">Authoring tools</a> for details on the requirements for a <em>conforming</em>
user agent.</dd>
</dl>
@@ -585,8 +584,8 @@
<h2>Event dispatch and DOM event flow</h2>
<p>This section defines the event <a class="def" href="#glossary-dispatch">dispatch</a> mechanism of the event model defined in this specification.
- Applications <span class="may">may</span> dispatch event objects using the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method, and
- implementations <span class="must">must</span> dispatch event objects as if through this method. The behavior of this method depends on the <em>event flow</em>
+ Applications MAY dispatch event objects using the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method, and
+ implementations MUST dispatch event objects as if through this method. The behavior of this method depends on the <em>event flow</em>
associated with the underlying object. An event flow describes how event objects <em>propagate</em> through a data structure. As an example, when an event object
is dispatched to an element in an XML document, the object propagates through parts of the document, as determined by the DOM event flow which is defined at the
end of this section.</p>
@@ -598,13 +597,13 @@
</div>
<p>Event objects are dispatched to an <a class="def" href="#glossary-event-target">event target</a>. At the beginning
- of the dispatch, implementations <span class="must">must</span> first determine the event object's <a class="def" href="#glossary-propagation-path">propagation path</a>.</p>
-
- <p>The propagation path <span class="must">must</span> be an ordered list of <a class="def" href="#glossary-current-event-target">current event targets</a> through which
- the event object <span class="must">must</span> pass. For DOM implementations, the propagation path <span class="must">must</span> reflect the hierarchical tree
- structure of the document. The last item in the list <span class="must">must</span> be the <a class="def" href="#glossary-event-target">event target</a>; the
+ of the dispatch, implementations MUST first determine the event object's <a class="def" href="#glossary-propagation-path">propagation path</a>.</p>
+
+ <p>The propagation path MUST be an ordered list of <a class="def" href="#glossary-current-event-target">current event targets</a> through which
+ the event object MUST pass. For DOM implementations, the propagation path MUST reflect the hierarchical tree
+ structure of the document. The last item in the list MUST be the <a class="def" href="#glossary-event-target">event target</a>; the
preceding items in the list are referred to as the <em>target's ancestors</em>, and the immediately preceding item as the <em>target's parent</em>. Once determined, the
- propagation path <span class="mustnot">must not</span> be changed; for DOM implementations, this applies even if an element in the propagation path is moved within the
+ propagation path MUST NOT be changed; for DOM implementations, this applies even if an element in the propagation path is moved within the
DOM. or removed from the DOM.</p>
<div class="example">
@@ -613,8 +612,8 @@
event target</a> in the document while the event object is being dispatched; such changes do not affect the propagation path.</p>
</div>
- <p>Exceptions thrown inside event listeners <span class="mustnot">must not</span> stop the propagation of the event or affect the
- <a class="def" href="#glossary-propagation-path">propagation path</a>. The exception itself <span class="mustnot">must not</span> propogate outside the scope of the event
+ <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
handler.</p>
<div class="example">
@@ -632,41 +631,41 @@
console.log("Exceptions? No problem");</pre>
</div>
- <p id="event-phase">As the next step, the event object <span class="must">must</span> complete one or more <a class="def" href="#glossary-phase">event phases</a>. This specification defines
+ <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
- complete these phases in the specified order using the partial propagation paths as defined below. A phase <span class="must">must</span> be skipped if it is not
+ 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 <span class="must">must</span> be skipped.</p>
+ called prior to the dispatch, all phases MUST be skipped.</p>
<ol>
- <li>The <strong id="capture-phase">capture phase</strong>: the event object <span class="must">must</span> 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 <span class="must">must</span> handle the event before it reaches its target.</li>
-
- <li>The <strong id="target-phase">target phase</strong>: the event object <span class="must">must</span> 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 <span class="must">must</span>
+ 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">
+ 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 <span class="mustnot">must not</span> bubble, the event object <span class="must">must</span> halt after completion of this phase.</li>
+ 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
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 <span class="must">must</span> handle the event after it has reached its target.</li>
+ Event listeners registered for this phase MUST handle the event after it has reached its target.</li>
</ol>
- <p>Implementations <span class="must">must</span> let event objects accomplish an event phase by applying the following steps while there are pending event targets in
+ <p>Implementations MUST let event objects accomplish an event phase by applying the following steps while there are pending event targets in
the partial propagation path for this phase and the event object's propagation has not been stopped through <a href="#events-event-type-stopPropagation"><code>
Event.stopPropagation()</code></a>.</p>
- <p>First, the implementation <span class="must">must</span> determine the <em>current target</em>. This <span class="must">must</span> be the next pending event target in the partial propagation
- path, starting with the first. From the perspective of an event listener this <span class="must">must</span> be the event target the listener has been registered on.</p>
-
- <p>Next, the implementation <span class="must">must</span> determine the current target's <a class="def" href="#glossary-candidate-event-handlers">candidate event listeners</a>.
- This <span class="must">must</span> be the list of all event listeners that have been registered on the current target in their order of registration. [<cite><a class="informative"
+ <p>First, the implementation MUST determine the <em>current target</em>. This MUST be the next pending event target in the partial propagation
+ path, starting with the first. From the perspective of an event listener this MUST be the event target the listener has been registered on.</p>
+
+ <p>Next, the implementation MUST determine the current target's <a class="def" href="#glossary-candidate-event-handlers">candidate event listeners</a>.
+ This MUST be the list of all event listeners that have been registered on the current target in their order of registration. [<cite><a class="informative"
href="#references-HTML5">HTML5</a></cite>] defines the ordering of listeners registered through event handler attributes. Once determined, the candidate event listeners
- <span class="mustnot">must not</span> be changed; adding or removing listeners does not affect the current target's candidate event listeners.</p>
-
- <p>Finally, the implementation <span class="must">must</span> process all candidate <a class="def" href="#glossary-event-handler">event handlers</a> in order and trigger
+ MUST NOT be changed; adding or removing listeners does not affect the current target's candidate event listeners.</p>
+
+ <p>Finally, the implementation MUST process all candidate <a class="def" href="#glossary-event-handler">event handlers</a> in order and trigger
each handler if all the following conditions are met:</p>
<ul>
@@ -683,26 +682,26 @@
<a class="def" href="#glossary-defaultView">defaultView</a> during the <a class="def" href="#glossary-bubbling-phase">bubble phase</a>.</p>
<p>After an event completes all the phases of its <a class="def" href="#glossary-propagation-path">propagation path</a>, its <a href="#events-event-type-currentTarget">
- <code>Event.currentTarget</code></a> <span class="must">must</span> be set to <code>null</code> and the <a href="#events-event-type-eventPhase"><code>Event.eventPhase</code></a> <span class="must">must</span> be
+ <code>Event.currentTarget</code></a> MUST be set to <code>null</code> and the <a href="#events-event-type-eventPhase"><code>Event.eventPhase</code></a> MUST be
set to <code>0</code> (<a href="#events-UNINIT"><code>NONE</code></a>). All other attributes of the <code>Event</code> (or interface derived from <code>Event</code>)
- are unchanged (including the <a href="#events-event-type-target"><code>Event.target</code></a> attribute, which <span class="must">must</span> continue to reference the <a class="def" href="#glossary-event-target">
+ are unchanged (including the <a href="#events-event-type-target"><code>Event.target</code></a> attribute, which MUST continue to reference the <a class="def" href="#glossary-event-target">
event target</a>).</p>
- <p>The model defined above <span class="must">must</span> be applied regardless of the specific event flow associated with an event target. Each event flow <span class="must">must</span> define how the propagation path
- <span class="must">must</span> be determined and which event phases are supported. The <em>DOM event flow</em> is an application of this model: the propagation path for a <code>Node</code>
- object <span class="must">must</span> be determined by its <code>Node.parentNode</code> chain, and if applicable, the document's containing <a class="def" href="#glossary-defaultView">defaultView</a>;
- all events accomplish the capture and target phases; whether an event accomplishes the bubble phase <span class="must">must</span> be defined individually for each <a class="def" href="#glossary-event-type">
+ <p>The model defined above MUST be applied regardless of the specific event flow associated with an event target. Each event flow MUST define how the propagation path
+ MUST be determined and which event phases are supported. The <em>DOM event flow</em> is an application of this model: the propagation path for a <code>Node</code>
+ object MUST be determined by its <code>Node.parentNode</code> chain, and if applicable, the document's containing <a class="def" href="#glossary-defaultView">defaultView</a>;
+ all events accomplish the capture and target phases; whether an event accomplishes the bubble phase MUST be defined individually for each <a class="def" href="#glossary-event-type">
event type</a>. An alternate application of this model can be found in [<cite><a class="informative" href="#references-DOMLS">DOM3 Load and Save</a></cite>].</p>
- <p>Implementations of the DOM event model <span class="must">must</span> be reentrant. Event listeners <span class="may">may</span> perform actions that cause additional events to be dispatched. Such events are handled
- in a synchronous manner, the event propagation that causes the event listener to be triggered <span class="must">must</span> resume only after the event dispatch of the new event is completed.</p>
+ <p>Implementations of the DOM event model MUST be reentrant. Event listeners MAY perform actions that cause additional events to be dispatched. Such events are handled
+ in a synchronous manner, the event propagation that causes the event listener to be triggered MUST resume only after the event dispatch of the new event is completed.</p>
</section>
<section id="event-flow-default-cancel">
<h2>Default actions and cancelable events</h2>
<p>Events are typically dispatched by the implementation as a result of a user action, in response to the completion of a task, or to signal progress during asynchronous
- activity (such as a network request). Some events can be used to control the behavior that the implementation <span class="may">may</span> take next (or undo an action that the implementation
+ activity (such as a network request). Some events can be used to control the behavior that the implementation MAY take next (or undo an action that the implementation
already took). Events in this category are said to be <em>cancelable</em> and the behavior they cancel is called their <a class="def" href="#glossary-default-action">
<em>default action</em></a>. Cancelable event objects can be associated with one or more <a class="def" href="#glossary-default-action">default actions</a>.
To cancel an event, call the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method.</p>
@@ -717,8 +716,8 @@
event prevents these actions from occuring.</p>
</div>
- <p><a class="def" href="#glossary-default-action">Default actions</a> <span class="should">should</span> be performed after the event dispatch has been completed, but in exceptional
- cases <span class="may">may</span> also be performed immediately before the event is dispatched.</p>
+ <p><a class="def" href="#glossary-default-action">Default actions</a> SHOULD be performed after the event dispatch has been completed, but in exceptional
+ cases MAY also be performed immediately before the event is dispatched.</p>
<div class="example">
<div class="example-title">Example</div>
@@ -727,9 +726,9 @@
</a> event's default action is cancelled, then the value is restored to its former state.</p>
</div>
- <p id="events-dt-cancelable-event">When an event is canceled, then the conditional <a class="def" href="#glossary-default-action">default actions</a> associated with the event <span class="must">must</span> be skipped (or
- as mentioned above, if the <a class="def" href="#glossary-default-action">default actions</a> are carried out before the dispatch, their effect <span class="must">must</span> be undone).
- Whether an event object is cancelable <span class="must">must</span> be indicated by the <a href="#events-event-type-canCancel"><code>Event.cancelable</code></a> attribute. <a href="#events-event-type-preventDefault">
+ <p id="events-dt-cancelable-event">When an event is canceled, then the conditional <a class="def" href="#glossary-default-action">default actions</a> associated with the event MUST be skipped (or
+ as mentioned above, if the <a class="def" href="#glossary-default-action">default actions</a> are carried out before the dispatch, their effect MUST be undone).
+ Whether an event object is cancelable MUST be indicated by the <a href="#events-event-type-canCancel"><code>Event.cancelable</code></a> attribute. <a href="#events-event-type-preventDefault">
<code>Event.preventDefault()</code></a> stops all related <a class="def" href="#glossary-default-action">default actions</a> of an event object. The <a href="#events-event-type-defaultPrevented">
<code>Event.defaultPrevented</code></a> attribute indicates whether an event has already been canceled (e.g., by a prior event listener). If the <a class="def" href="#glossary-DOM-application">
DOM application</a> itself initiated the dispatch, then the return value of the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a>
@@ -743,8 +742,8 @@
example, the <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> event.</p>
<p>This specification does not offer features to programatically query if an event object has any <a class="def" href="#glossary-default-action">default action</a> associated with
- it, or to associate new <a class="def" href="#glossary-default-action">default actions</a> with an event object. Other specifications <span class="should">should</span> define what default actions, if any,
- are associated with certain event objects. Further, implementations <span class="may">may</span> associate <a class="def" href="#glossary-default-action">default actions</a> with events as necessary and
+ it, or to associate new <a class="def" href="#glossary-default-action">default actions</a> with an event object. Other specifications SHOULD define what default actions, if any,
+ are associated with certain event objects. Further, implementations MAY associate <a class="def" href="#glossary-default-action">default actions</a> with events as necessary and
appropriate for that implementation.</p>
<div class="example">
@@ -758,12 +757,12 @@
<section id="sync-async">
<h2>Synchronous and asynchronous events</h2>
- <p>Events <span class="may">may</span> be dispatched either synchronously or asynchronously.</p>
-
- <p>Events which are synchronous (<em><q>sync events</q></em>) <span class="must">must</span> 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 <span class="must">must</span> be delayed until the
+ <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
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 <span class="must">must</span> dispatch
+ 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>
<div class="example">
@@ -777,7 +776,7 @@
Each of these events are fired in the sequence initiated by the user's actions.</p>
</div>
- <p>Events which are asynchronous (<em><q>async events</q></em>) <span class="may">may</span> be dispatched as the results of the action are completed, with no relation to other events, to
+ <p>Events which are asynchronous (<em><q>async events</q></em>) MAY be dispatched as the results of the action are completed, with no relation to other events, to
other changes in the DOM, nor to user interaction.</p>
<div class="example">
@@ -795,7 +794,7 @@
event loop mechanism, but it is compatible with this mechanism. Instead, this specification defines several operation-specific <a class="def" href="#glossary-event-order">
event orders</a>.</p>
- <p>Using the terminology of HTML5, each independent device, such as a mouse or keyboard, <span class="should">should</span> be treated as a <em>task source</em> which feeds into the appropriate
+ <p>Using the terminology of HTML5, each independent device, such as a mouse or keyboard, SHOULD be treated as a <em>task source</em> which feeds into the appropriate
<em>task queue</em>, in the order defined by the <a class="def" href="#glossary-event-order">event order</a> associated with that device; each operation, such as
a focus change or composition input, also acts as a <em>task source</em> for the appropriate <em>task queue</em>. The resolution of these event loops is handled
in a manner conforming to the <a class="def" href="#glossary-host-language">host language</a>, such as HTML [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>].</p>
@@ -814,24 +813,24 @@
<code>EventTarget.dispatchEvent()</code></a> method. The <a href="#events-event-type-isTrusted"><code>isTrusted</code></a> attribute of trusted events has a
value of <code>true</code>, while untrusted events have a <a href="#events-event-type-isTrusted"><code>isTrusted</code></a> attribute value of <code>false</code>.</p>
- <p>Most untrusted events <span class="shouldnot">should not</span> trigger <a class="def" href="#glossary-default-action">default actions</a>, with the exception of <a class="eventtype" href="#event-type-click">
+ <p>Most untrusted events SHOULD NOT trigger <a class="def" href="#glossary-default-action">default actions</a>, with the exception of <a class="eventtype" href="#event-type-click">
<code>click</code></a> or <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> events. These events trigger the <a class="def" href="#glossary-default-action">
default action</a> of an <a class="def" href="#glossary-activation-trigger">activation trigger</a> (see <a href="#event-flow-activation">Activation triggers and behaviors</a> for more details); these
untrusted events have an <a href="#events-event-type-isTrusted"><code>isTrusted</code></a> attribute value of <code>false</code>, but still initiate any
- <a class="def" href="#glossary-default-action">default actions</a> for backwards compatibility. All other untrusted events <span class="must">must</span> behave
+ <a class="def" href="#glossary-default-action">default actions</a> for backwards compatibility. All other untrusted events MUST behave
as if the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> method had been called on that event.</p>
</section>
<section id="event-flow-activation">
<h2>Activation triggers and behavior</h2>
- <p>Certain <a class="def" href="#glossary-event-target">event targets</a> (such as a link or button element) <span class="may">may</span> have associated <a class="def" href="#glossary-activation-behavior">
+ <p>Certain <a class="def" href="#glossary-event-target">event targets</a> (such as a link or button element) MAY have associated <a class="def" href="#glossary-activation-behavior">
activation behavior</a> (such a following a link) that implementations perform in response to an <em><a class="def" href="#glossary-activation-trigger">activation
trigger</a></em> (such as clicking a link).</p>
- <p>A <a class="def" href="#glossary-host-language">host language</a> <span class="should">should</span> indicate which, if any, elements have activation behavior, describe appropriate <a class="def"
+ <p>A <a class="def" href="#glossary-host-language">host language</a> SHOULD indicate which, if any, elements have activation behavior, describe appropriate <a class="def"
href="#glossary-activation-trigger">activation triggers</a>, and define the result of that activation behavior. An implementation which supports a <a class="def"
- href="#glossary-host-language">host language</a> <span class="should">should</span> initiate these <a class="def" href="#glossary-activation-behavior">activation behavior</a> when the associated
+ href="#glossary-host-language">host language</a> SHOULD initiate these <a class="def" href="#glossary-activation-behavior">activation behavior</a> when the associated
<a class="def" href="#glossary-activation-trigger">activation trigger</a> occurs.</p>
<div class="example" id="example-activation">
@@ -845,18 +844,18 @@
</div>
<p>An <a class="def" href="#glossary-activation-trigger">activation trigger</a> is a user action or an event which indicates to the implementation that an activation
- behavior <span class="should">should</span> be initiated. User-initiated <a class="def" href="#glossary-activation-trigger">activation triggers</a> include clicking a mouse button on an activatable
+ behavior SHOULD be initiated. User-initiated <a class="def" href="#glossary-activation-trigger">activation triggers</a> include clicking a mouse button on an activatable
element, pressing the <a href="#key-Enter"><code class="key">'Enter'</code></a> key when an activatable element has focus, or pressing a key that is somehow
linked to an activatable element (a <q>hotkey</q> or <q>access key</q>) even when that element does not have focus. Event-based <a class="def" href="#glossary-activation-trigger">
- activation triggers</a> <span class="may">may</span> include timer-based events that activate an element at a certain clock time or after a certain time period has elapsed, progress
+ activation triggers</a> MAY include timer-based events that activate an element at a certain clock time or after a certain time period has elapsed, progress
events after a certain action has been completed, or many other condition-based or state-based events.</p>
- <p>In some cases, a <a class="def" href="#glossary-host-language">host language</a> <span class="may">may</span> define attributes or even attribute values which add to or change the native
+ <p>In some cases, a <a class="def" href="#glossary-host-language">host language</a> MAY define attributes or even attribute values which add to or change the native
<a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation behavior</a> of an element.
For example, ARIA [<cite><a class="informative" href="#ref-ARIA">ARIA</a></cite>] defines values for the <code class="attr">role</code> attribute that add semantics
to the element to which it is applied, for purposes of enhanced accessibility. In such cases, if the <a class="def" href="#glossary-host-language">host language</a>
does not explicitly define the <a class="def" href="#glossary-activation-trigger">activation trigger</a> or <a class="def" href="#glossary-activation-behavior">activation
- behavior</a>, the content author <span class="must">must</span> provide the mechanics of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> (via an event listener)
+ behavior</a>, the content author MUST provide the mechanics of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> (via an event listener)
or <a class="def" href="#glossary-activation-behavior">activation behavior</a> (such as calling an ECMAScript function) for that element when applying that attribute
or attribute value.</p>
@@ -865,16 +864,16 @@
<p>If the instance of the <a class="def" href="#glossary-activation-trigger">activation trigger</a> is not an event of <a class="def" href="#glossary-event-type">event
type</a> <a class="eventtype" href="#event-type-click"><code>click</code></a> (that is, when it does not result from a user's activation of a button or link
- using a mouse or equivalent pointing device), the implementation <span class="must">must</span> synthesize and dispatch an event of <a class="def" href="#glossary-event-type">event type</a> <a
+ 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>
- <span class="must">must</span> be set to the <a class="def" href="#glossary-event-target">event target</a> (normally, the currently focused element), and the event <span class="must">must</span> simulate a <em>left
- click</em> (i.e., the <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> attribute value <span class="must">must</span> be <code>0</code>, and the <a href="#events-MouseEvent-buttons">
- <code>MouseEvent.buttons</code></a> attribute value <span class="must">must</span> be <code>1</code>). Other context information of such a simulated <a class="eventtype" href="#event-type-click">
+ 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">
<code>click</code></a> event is implementation dependent, but for historical purposes, the interface for the <a class="eventtype" href="#event-type-click"><code>click</code></a>
- event <span class="must">must</span> be the <a href="#events-MouseEvent"><code>MouseEvent interface</code></a>, regardless of the actual device used to activate the element. Preventing
+ event MUST be the <a href="#events-MouseEvent"><code>MouseEvent interface</code></a>, regardless of the actual device used to activate the element. Preventing
the <a class="def" href="#glossary-default-action">default action</a> of the <a class="def" href="#glossary-activation-trigger">activation trigger</a>, such as
- with the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a>, <span class="must">must</span> stop the initiation of the <a class="def" href="#glossary-activation-behavior">
+ with the <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a>, MUST stop the initiation of the <a class="def" href="#glossary-activation-behavior">
activation behavior</a>.</p>
<div class="example">
@@ -885,7 +884,7 @@
<a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event.</p>
</div>
- <p>Implementations <span class="must">must</span> dispatch the synthesized <a class="eventtype" href="#event-type-click"><code>click</code></a> event as described above even if they do not
+ <p>Implementations MUST dispatch the synthesized <a class="eventtype" href="#event-type-click"><code>click</code></a> event as described above even if they do not
normally dispatch such an event (e.g., when activation is requested by a voice command, since this specification does not address <a class="def" href="#glossary-event-type">
event types</a> for voice input).</p>
@@ -893,15 +892,15 @@
using a mouse click or a mouse double click.</p>
<p>Implementations which support the <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event
- type</a> <span class="should">should</span> also dispatch a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event as a <a class="def" href="#glossary-default-action">
+ type</a> SHOULD also dispatch a <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> event as a <a class="def" href="#glossary-default-action">
default action</a> of a <a class="eventtype" href="#event-type-click"><code>click</code></a> event which is associated with an <a class="def" href="#glossary-activation-trigger">
- activation trigger</a>. However, such implementations <span class="should">should</span> only initiate the associated <a class="def" href="#glossary-activation-behavior">activation behavior</a>
+ activation trigger</a>. However, such implementations SHOULD only initiate the associated <a class="def" href="#glossary-activation-behavior">activation behavior</a>
once for any given occurrence of an <a class="def" href="#glossary-activation-trigger">activation trigger</a>.</p>
<div class="example">
<div class="example-title">Example</div>
<p>The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a>
- <a class="def" href="#glossary-event-type">event type</a> is <span class="required">required</span> to be supported for XForms [<cite><a class="informative" href="#ref-xforms">XFORMS</a></cite>],
+ <a class="def" href="#glossary-event-type">event type</a> is REQUIRED to be supported for XForms [<cite><a class="informative" href="#ref-xforms">XFORMS</a></cite>],
which is intended for implementation within a <a class="def" href="#glossary-host-language">host language</a>. In a scenario where a plugin or script-based implementation
of XForms is intended for installation in a native implementation of this specification which does not support the <a class="eventtype" href="#event-type-DOMActivate">
<code>DOMActivate</code></a> <a class="def" href="#glossary-event-type">event type</a>, the XForms <a class="def" href="#glossary-user-agent">user agent</a>
@@ -942,7 +941,7 @@
<p>The following is the typical sequence of events when a focused element is activated by a key event (with only pertinent events listed):</p>
<ol>
- <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (<span class="must">must</span> be a key which can activate the element, such as the <a href="#key-Enter"><code
+ <li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (MUST be a key which can activate the element, such as the <a href="#key-Enter"><code
class="key">'Enter'</code></a> or <a href="#key-Spacebar"><code class="key">'Spacebar'</code></a> key, or the element is not activated)</li>
<li><a class="eventtype" href="#event-type-click"><code>click</code></a> (<a class="def" href="#glossary-default-action">default action</a>; synthesized; <code>trusted="false"
@@ -994,11 +993,11 @@
<section id="event-interfaces">
<h1>Basic Event Interfaces</h1>
- <p>The interfaces described in this section are fundamental to DOM Level 3 Events and <span class="must">must</span> always be supported by the implementation.</p>
-
- <p>The event types defined in this specification derive from these basic interfaces, and <span class="must">must</span> inherit all of the attributes, methods, and constants of the interfaces
- they derive from. Event types defined in other specifications <span class="may">may</span> similarly inherit from these basic interfaces or other interfaces defined in this specification,
- or <span class="may">may</span> define their own interfaces. The following chart describes the inheritance structure of interfaces defined in this specification.</p>
+ <p>The interfaces described in this section are fundamental to DOM Level 3 Events and MUST always be supported by the implementation.</p>
+
+ <p>The event types defined in this specification derive from these basic interfaces, and MUST inherit all of the attributes, methods, and constants of the interfaces
+ they derive from. Event types defined in other specifications MAY similarly inherit from these basic interfaces or other interfaces defined in this specification,
+ or MAY define their own interfaces. The following chart describes the inheritance structure of interfaces defined in this specification.</p>
<div class="figure" style="text-align: center">
<object type="image/svg+xml" data="images/event-inheritance.svg" width="960" height="230">
@@ -1047,9 +1046,9 @@
<dt>readonly attribute DOMString type</dt>
<dd>
<p>The name of the event type. <a href="#conf-specs">Specifications that define events</a>, <a href="#conf-authors">content authors</a>, and <a href="#conf-author-tools">
- authoring tools</a> <span class="must">must</span> use case-sensitive event type names.</p>
-
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</p>
+ authoring tools</a> MUST use case-sensitive event type names.</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>
<dt>readonly attribute EventTarget? target</dt>
@@ -1057,7 +1056,7 @@
<p>Used to retrieve the <a class="def" href="#glossary-event-target">event target</a> associated with the <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 <span class="must">must</span> be <code>null</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>null</code>.</p>
</dd>
<dt>readonly attribute EventTarget? currentTarget</dt>
@@ -1065,7 +1064,7 @@
<p>Used to retrieve the <a class="def" href="#glossary-current-event-target">current event target</a> whose <a href="#events-EventListener"><code>EventListeners</code></a>
are currently being processed. This is particularly useful during the capture and bubbling phases.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>null</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>null</code>.</p>
</dd>
<dt>readonly attribute unsigned short eventPhase</dt>
@@ -1073,24 +1072,24 @@
<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 <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute boolean bubbles</dt>
<dd>
- <p>Used to indicate whether or not an event is a bubbling event. If the event can bubble the value <span class="must">must</span> be <code>true</code>, otherwise the value <span class="must">must</span> be
+ <p>Used to indicate whether or not an event is a bubbling event. If the event can bubble the value MUST be <code>true</code>, otherwise the value MUST be
<code>false</code>.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute boolean cancelable</dt>
<dd>
<p>Used to indicate whether or not an event can have its <a class="def" href="#glossary-default-action">default action</a> prevented (see also <a href="#event-flow-default-cancel">
- Default actions and cancelable events</a>). If the <a class="def" href="#glossary-default-action">default action</a> can be prevented the value <span class="must">must</span> be <code>true</code>,
- otherwise the value <span class="must">must</span> be <code>false</code>.</p>
-
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ Default actions and cancelable events</a>). If the <a class="def" href="#glossary-default-action">default action</a> can be prevented the value MUST be <code>true</code>,
+ otherwise the value MUST be <code>false</code>.</p>
+
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
<p class="note"><strong>Note:</strong> Use <code>Event.defaultPrevented</code> to see whether a cancelable event has beened cancelled or not.</p>
</dd>
@@ -1112,11 +1111,11 @@
<dt>void preventDefault()</dt>
<dd>
- <p>When this method is invoked, the event <span class="must">must</span> be canceled, meaning any <a class="def" href="#glossary-default-action">default actions</a> normally taken by the implementation
- as a result of the event <span class="mustnot">must not</span> occur (see also <a href="#event-flow-default-cancel">Default actions and cancelable events</a>). Default actions which occur prior
+ <p>When this method is invoked, the event MUST be canceled, meaning any <a class="def" href="#glossary-default-action">default actions</a> normally taken by the implementation
+ as a result of the event MUST NOT occur (see also <a href="#event-flow-default-cancel">Default actions and cancelable events</a>). Default actions which occur prior
to the event's dispatch (see <a href="#event-flow-default-cancel">Default actions and cancelable events</a>) are reverted. Calling this method for a non-cancelable
- event <span class="must">must</span> have no effect. If an event has more than one <a class="def" href="#glossary-default-action">default action</a>, each cancelable <a class="def" href="#glossary-default-action">
- default action</a> <span class="must">must</span> be canceled.</p>
+ event MUST have no effect. If an event has more than one <a class="def" href="#glossary-default-action">default action</a>, each cancelable <a class="def" href="#glossary-default-action">
+ default action</a> MUST be canceled.</p>
<p class="note"><strong>Note:</strong> This method does not stop the event propagation; use <a href="#events-event-type-stopPropagation">
<code>Event.stopPropagation()</code></a> or <a href="#events-event-type-stopImmediatePropagation"><code>Event.stopImmediatePropagation()</code></a> for that effect.</p>
@@ -1126,14 +1125,14 @@
<dd>
<p>Initializes attributes of an <code>Event</code>. The <code>Event</code> could have been created through the <a href="#events-DocumentEvent-createEvent">
<code>DocumentEvent.createEvent</code></a> method or by the implementation in response to a user action. For any <code>Event</code> created with the
- <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent</code></a> method, this method <span class="must">must</span> be called before the <code>Event</code>
+ <a href="#events-DocumentEvent-createEvent"><code>DocumentEvent.createEvent</code></a> method, this method MUST be called before the <code>Event</code>
is dispatched via the <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent()</code></a> method. If the method is called several
times before invoking <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent</code></a>, only the final invocation takes precedence.
If this method is called during an invocation of <a href="#events-EventTarget-dispatchEvent"><code>EventTarget.dispatchEvent</code></a>, this method
- <span class="must">must</span> do nothing and return immediately. If called from a subclass of the <code>Event</code> interface only the values specified in
+ MUST do nothing and return immediately. If called from a subclass of the <code>Event</code> interface only the values specified in
this method are modified, all other attributes are left unchanged.</p>
- <p>This method <span class="must">must</span> also reset the event object's internal-propagation and default-action-prevention states. This allows an event object to be "reset"
+ <p>This method MUST also reset the event object's internal-propagation and default-action-prevention states. This allows an event object to be "reset"
before being dispatched multiple times.</p>
<div class="example">
@@ -1145,7 +1144,7 @@
</div>
<p class="warning" id="warning-initEvent-untrusted"><strong>Warning!</strong> For security reasons, events modified using <a href="#events-event-type-initEvent"><code>
- Event.initEvent()</code></a> <span class="must">must</span> have a <code class="attribute-name"><a href="#events-event-type-isTrusted">isTrusted</a></code> attribute value of <code>false</code>.
+ Event.initEvent()</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>Authoring Note:</strong> <a class="def" href="#trusted-events">Trusted events</a> can have their <a class="def" href="#glossary-event-type">
@@ -1193,11 +1192,11 @@
<dd>
<p class="intro-dom">Introduced in DOM Level 3</p>
- <p>Used to indicate whether this event has been cancelled or not. <code>Event.defaultPrevented</code> <span class="must">must</span> return true if both <a href="#events-event-type-canCancel">
+ <p>Used to indicate whether this event has been cancelled or not. <code>Event.defaultPrevented</code> MUST return true if both <a href="#events-event-type-canCancel">
<code>Event.cancelable</code></a> is <code>true</code> and <a href="#events-event-type-preventDefault"><code>Event.preventDefault()</code></a> has been called for
- this event. Otherwise this attribute <span class="must">must</span> return <code>false</code>.</p>
-
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ this event. Otherwise this attribute MUST return <code>false</code>.</p>
+
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
<p class="note"><strong>Note:</strong> Calling <a href="#events-event-type-initEvent"><code>Event.initEvent()</code></a> after an event has been dispatched will reset
the internal default-prevented state of the event.</p>
@@ -1210,7 +1209,7 @@
<p>Used to indicate whether this event was generated by the <a class="def" href="#glossary-user-agent">user agent</a> (trusted) or by script (untrusted). See <a
href="#trusted-events">trusted events</a> for more details.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
</dl>
</section>
@@ -1220,7 +1219,7 @@
<p class="intro-dom">Introduced in DOM Level 2</p>
- <p>The <a href="#events-CustomEvent"><code>CustomEvent</code></a> interface is the <span class="recommended">recommended</span> interface for application-specific event types. Unlike the <a href="#events-Event">
+ <p>The <a href="#events-CustomEvent"><code>CustomEvent</code></a> interface is the RECOMMENDED interface for application-specific event types. Unlike the <a href="#events-Event">
<code>Event</code></a> interface, it allows applications to provide contextual information about the event type.</p>
<p class="note"><strong>Authoring Note:</strong> Use a prefix string on the event type name for application-specific event types to avoid clashes with future general-purpose
@@ -1237,7 +1236,7 @@
<dd>
<p>Specifies some detail information about the <a href="#events-Event"><code>Event</code></a>.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>null</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>null</code>.</p>
</dd>
</dl>
</section>
@@ -1254,7 +1253,7 @@
(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 <span class="must">must</span> be implemented by all <a class="def" href="#glossary-event-target">event targets</a> and target ancestors,
+ <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,
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>
@@ -1289,19 +1288,19 @@
<dt>EventListener? listener</dt>
<dd>
- <p>The <code>listener</code> parameter <span class="must">must</span> be an object that implements the <a href="#events-EventListener"><code>EventListener</code></a> interface or a function.
- If <code>listener</code> is a function then it <span class="must">must</span> be used as the callback for the event; otherwise, if <code>listener</code> implements <a href="#events-EventListener">
- <code>EventListener</code></a>, then its <a href="#events-EventListener-handleEvent">handleEvent</a> method <span class="must">must</span> be used as the callback.</p>
+ <p>The <code>listener</code> parameter MUST be an object that implements the <a href="#events-EventListener"><code>EventListener</code></a> interface or a function.
+ If <code>listener</code> is a function then it MUST be used as the callback for the event; otherwise, if <code>listener</code> implements <a href="#events-EventListener">
+ <code>EventListener</code></a>, then its <a href="#events-EventListener-handleEvent">handleEvent</a> method MUST be used as the callback.</p>
</dd>
<dt>optional boolean useCapture = false</dt>
<dd>
<p>If true, <code>useCapture</code> indicates that the user wishes to add the event listener for the <a class="def" href="#glossary-capture-phase">capture</a>
and <a class="def" href="#glossary-target-phase">target</a> phases only, i.e., this event listener will not be triggered during the <a class="def"
- href="#glossary-bubbling-phase"> bubbling</a> phase. If <code>false</code>, the event listener <span class="must">must</span> only be triggered during the <a class="def"
+ href="#glossary-bubbling-phase"> bubbling</a> phase. If <code>false</code>, the event listener MUST only be triggered during the <a class="def"
href="#glossary-target-phase">target</a> and <a class="def" href="#glossary-bubbling-phase">bubbling</a> phases.</p>
- <p>This parameter <span class="must">must</span> be optional. If not provided, the <a href="#events-EventTarget-addEventListener">EventTarget.addEventListener</a> method <span class="must">must</span> behave as if <a
+ <p>This parameter MUST be optional. If not provided, the <a href="#events-EventTarget-addEventListener">EventTarget.addEventListener</a> method MUST behave as if <a
href="#addEventListener_useCapture"><code class="parameter-name">useCapture</code></a> were specified to be <code>false</code>.</p>
<p class="note" id="addEventListener_useCapture-author"><strong>Authoring Note:</strong> The <a href="#events-EventTarget-addEventListener"><code class="parameter-name">
@@ -1332,14 +1331,14 @@
<dt>optional boolean useCapture = false</dt>
<dd>
<p>Specifies whether the <a href="#events-EventListener"><code>EventListener</code></a> being removed was registered for the capture phase or not. Implementations
- <span class="must">must</span> treat the same listener that was registered twice with both <code>useCapture</code> true and <code>useCapture</code> false as independent registrations, and
+ MUST treat the same listener that was registered twice with both <code>useCapture</code> true and <code>useCapture</code> false as independent registrations, and
remove them independently.</p>
<p class="note"><strong>Authoring Note:</strong> If a listener was registered twice, once for the capture and target phases and once for the target and bubbling phases,
this represents two unique registrations. Removal of an event listener registered for the capture and target phases does not affect the same event listener registered
for the target and bubbling phases, and vice versa.</p>
- <p>This parameter <span class="must">must</span> be optional. If not provided, the <a href="#events-EventTarget-removeEventListener">EventTarget.removeEventListener</a> method <span class="must">must</span> behave as if <a
+ <p>This parameter MUST be optional. If not provided, the <a href="#events-EventTarget-removeEventListener">EventTarget.removeEventListener</a> method MUST behave as if <a
href="#removeEventListener_useCapture"><code class="parameter-name">useCapture</code></a> were specified to be <code>false</code>.</p>
<p class="note"><strong>Authoring Note:</strong> The <a href="#removeEventListener_useCapture"><code class="parameter-name">useCapture</code></a> parameter was manditory in DOM2
@@ -1352,14 +1351,14 @@
<dd>
<p><em>Modified in DOM Level 3</em></p>
- <p>Dispatches an event into the implementation's event model. The <a class="def" href="#glossary-event-target">event target</a> of the event <span class="must">must</span> be the <code>EventTarget</code>
+ <p>Dispatches an event into the implementation's event model. The <a class="def" href="#glossary-event-target">event target</a> of the event MUST be the <code>EventTarget</code>
object on which <code>dispatchEvent</code> is called.</p>
<p>If after the event object finishes propagating through the DOM event flow its <a href="#events-event-type-defaultPrevented"><code>Event.defaultPrevented</code></a>
attribute is <code>false</code>, then this method returns <code>true</code>. Otherwise this method returns <code>false</code>.</p>
<p class="warning"><strong>Warning!</strong> For security reasons, events dispatched using <a href="#events-EventTarget-dispatchEvent">
- <code>EventTarget.dispatchEvent()</code></a> <span class="must">must</span> have a <code class="attribute-name"><a href="#events-event-type-isTrusted">isTrusted</a></code> attribute value
+ <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
@@ -1399,16 +1398,16 @@
after they have completed using the listener.</p>
<p>Copying a <code>Node</code>, with methods such as <code>Node.cloneNode</code> or <code>Range.cloneContents</code> [<cite><a class="informative"
- href="#references-DOMRange">DOM Range</a></cite>], <span class="mustnot">must not</span> copy the event listeners attached to it.
+ href="#references-DOMRange">DOM Range</a></cite>], MUST NOT copy the event listeners attached to it.
Event listeners can be attached to the newly created <code>Node</code> afterwards, if so desired.</p>
<p>Moving a <code>Node</code>, with methods such as <code>Document.adoptNode</code>, <code>Node.appendChild</code>, or <code>Range.extractContents</code>
- [<cite><a class="informative" href="#references-DOMRange">DOM Range</a></cite>], <span class="mustnot">must not</span> cause the event listeners attached to it to be removed or un-registered.</p>
+ [<cite><a class="informative" href="#references-DOMRange">DOM Range</a></cite>], MUST NOT cause the event listeners attached to it to be removed or un-registered.</p>
<dl class="idl" title="interface EventListener">
<dt>void handleEvent()</dt>
<dd>
- <p>This method <span class="must">must</span> be called whenever an event occurs of the event type for which the <code>EventListener</code> interface was registered.</p>
+ <p>This method MUST be called whenever an event occurs of the event type for which the <code>EventListener</code> interface was registered.</p>
<dl class="parameters">
<dt>Event event</dt>
@@ -1426,7 +1425,7 @@
<p class="intro-dom">Introduced in DOM Level 2</p>
<p>The <code>DocumentEvent</code> interface provides a mechanism by which the user can create an <a href="#events-Event"><code>Event</code></a> object of a type supported
- by the implementation. The <code>DocumentEvent</code> interface <span class="must">must</span> be implemented on the same object that implements the <code>Document</code> interface.</p>
+ by the implementation. The <code>DocumentEvent</code> interface MUST be implemented on the same object that implements the <code>Document</code> interface.</p>
<dl class="idl" title="Document implements DocumentEvent">
</dl>
@@ -1491,7 +1490,7 @@
</table>
<p class="warning"><strong>Warning!</strong> For security reasons, events generated using <a href="#events-DocumentEvent-createEvent">
- <code>DocumentEvent.createEvent("Event")</code></a> <span class="must">must</span> have a <code class="attribute-name"><a href="#events-event-type-isTrusted">isTrusted</a></code> attribute
+ <code>DocumentEvent.createEvent("Event")</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>
</dd>
</dl>
@@ -1507,14 +1506,14 @@
<section id="event-types">
<h2>Event Types</h2>
- <p>Each event <span class="must">must</span> be associated with a type, called <em>event type</em> and available as the <a href="#events-event-type-type"><code class="interface-attribute">type</code></a>
- attribute on the event object. The event type <span class="must">must</span> be of type <code>DOMString</code>.</p>
+ <p>Each event MUST be associated with a type, called <em>event type</em> and available as the <a href="#events-event-type-type"><code class="interface-attribute">type</code></a>
+ attribute on the event object. The event type MUST be of type <code>DOMString</code>.</p>
<section id="event-types-list">
<h3>List of DOM3 Event Types</h3>
<p>Depending on the level of DOM support, or the devices used for display (e.g., screen) or interaction (e.g., mouse, keyboard, touch screen, or voice), these event
types can be generated by the implementation. When used with an [<cite><a class="informative" href="#references-XML">XML 1.0</a></cite>] or
- [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] application, the specifications of those languages <span class="may">may</span> restrict the
+ [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] application, the specifications of those languages MAY restrict the
semantics and scope (in particular the possible <a class="def" href="#glossary-event-target">event targets</a>) associated
with an event type. Refer to the specification defining the language used in order to find those restrictions or to find event types that are
not defined in this document.</p>
@@ -1937,14 +1936,14 @@
<dd>
<p>The <code>view</code> attribute identifies the <code>AbstractView</code> from which the event was generated.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>null</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>null</code>.</p>
</dd>
<dt>readonly attribute long detail</dt>
<dd>
<p>Specifies some detail information about the <a href="#events-Event"><code>Event</code></a>, depending on the type of event.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>// Deprecated in DOM Level 3</dt>
@@ -1974,7 +1973,7 @@
<dt>AbstractView? viewArg</dt>
<dd>
- <p>Specifies <a href="#events-UIEvent-view"><code>UIEvent.view</code></a>. This value <span class="may">may</span> be <code>null</code>.</p>
+ <p>Specifies <a href="#events-UIEvent-view"><code>UIEvent.view</code></a>. This value MAY be <code>null</code>.</p>
</dd>
<dt>long detailArg</dt>
@@ -2036,13 +2035,13 @@
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a button, link, or other state-changing element is activated. Refer to
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a button, link, or other state-changing element is activated. Refer to
<a href="#event-flow-activation">Activation triggers and behavior</a> for more details.</p>
<p class="warning" id="DOMActivate-deprecated"><strong>Warning!</strong> The <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> <a
class="def" href="#glossary-event-type">event type</a> is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">
deprecates</a> the use of this event type in favor of the related <a class="def" href="#glossary-event-type">event type</a> <a class="eventtype" href="#event-type-click">
- <code>click</code></a>. Other specifications <span class="may">may</span> define and maintain their own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a>
+ <code>click</code></a>. Other specifications MAY define and maintain their own <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a>
<a class="def" href="#glossary-event-type">event type</a> for backwards compatibility.</p>
<p class="note" id="DOMActivate-click"><strong>Note:</strong> While <a class="eventtype" href="#event-type-DOMActivate"><code>DOMActivate</code></a> and <a class="eventtype"
@@ -2105,9 +2104,9 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when the DOM implementation finishes loading the resource (such as the document)
- and any dependent resources (such as images, style sheets, or scripts). Dependent resources that fail to load <span class="mustnot">must not</span> prevent this event from firing if the resource
- that loaded them is still accessible via the DOM. If this event type is dispatched, implementations are <span class="required">required</span> to dispatch this event at least on the <code>Document</code>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when the DOM implementation finishes loading the resource (such as the document)
+ and any dependent resources (such as images, style sheets, or scripts). Dependent resources that fail to load MUST NOT prevent this event from firing if the resource
+ that loaded them is still accessible via the DOM. If this event type is dispatched, implementations are REQUIRED to dispatch this event at least on the <code>Document</code>
node.</p>
<p class="note"><strong>Note:</strong> for legacy reasons, <a class="eventtype" href="#event-type-load"><code>load</code></a> events for resources inside
@@ -2166,9 +2165,9 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when the DOM Implementation removes from the environment the resource (such
- as the document) or any dependent resources (such as images, style sheets, scripts). The document <span class="must">must</span> be unloaded after the dispatch of this event type. If this
- event type is dispatched, implementations are <span class="required">required</span> to dispatch this event at least on the <code>Document</code> node.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when the DOM Implementation removes from the environment the resource (such
+ as the document) or any dependent resources (such as images, style sheets, scripts). The document MUST be unloaded after the dispatch of this event type. If this
+ event type is dispatched, implementations are REQUIRED to dispatch this event at least on the <code>Document</code> node.</p>
</dd>
</dl>
</div>
@@ -2222,7 +2221,7 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when the loading of a resource has been aborted, such as by a user canceling
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when the loading of a resource has been aborted, such as by a user canceling
the load while it is still in progress.</p>
</dd>
</dl>
@@ -2277,7 +2276,7 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a resource failed to load, or has been loaded but cannot be interpreted
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a resource failed to load, or has been loaded but cannot be interpreted
according to its semantics, such as an invalid image, a script execution error, or non-well-formed XML.</p>
</dd>
</dl>
@@ -2332,12 +2331,12 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a user selects some text. This event is dispatched after the selection
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a user selects some text. This event is dispatched after the selection
has occurred.</p>
<p>This specification does not provide contextual information to access the selected text. Where applicable, a <a class="def" href="#glossary-host-language">host
- language</a> <span class="should">should</span> define rules for how a user <span class="may">may</span> select content (with consideration for international language conventions), at what point the <a class="eventtype"
- href="#event-type-select"><code>select</code></a> event is dispatched, and how a content author <span class="may">may</span> access the user-selected content.</p>
+ language</a> SHOULD define rules for how a user MAY select content (with consideration for international language conventions), at what point the <a class="eventtype"
+ href="#event-type-select"><code>select</code></a> event is dispatched, and how a content author MAY access the user-selected content.</p>
<p class="note"><strong>Note:</strong> In order to access to user-selected content, content authors will use native capabilities of the <a
class="def" href="#glossary-host-language">host languages</a>, such as the <code>Document.getSelection()</code> method of the <a href="https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html#selections">
@@ -2400,15 +2399,15 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a document view has been resized. This event type is dispatched after
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a document view has been resized. This event type is dispatched after
all effects for that occurrence of resizing of that particular <a class="def" href="#glossary-event-target">event target</a> have been executed by the <a class="def"
href="#glossary-user-agent">user agent</a>.</p>
- <p><a class="def" href="#glossary-user-agent">User agents</a> which support continuous reflow of the document's layout during user-initiated resizing <span class="must">must</span> dispatch
+ <p><a class="def" href="#glossary-user-agent">User agents</a> which support continuous reflow of the document's layout during user-initiated resizing MUST dispatch
this event synchronously after each reflow of the document.</p>
- <p>The <a class="def" href="#glossary-defaultView"><code>defaultView</code></a> object <span class="should">should</span> always be resizable. A <a class="def" href="#glossary-host-language">
- host language</a> <span class="may">may</span> define certain elements to be resizable, and under what conditions (e.g., specific elements like <code><iframe></code>, or elements
+ <p>The <a class="def" href="#glossary-defaultView"><code>defaultView</code></a> object SHOULD always be resizable. A <a class="def" href="#glossary-host-language">
+ host language</a> MAY define certain elements to be resizable, and under what conditions (e.g., specific elements like <code><iframe></code>, or elements
with particular characteristics like width and height); however, this specification does not define the behavior for elements.</p>
<p class="note"><strong>Note:</strong> The <a class="eventtype" href="#event-type-resize"><code>resize</code></a> event is distinct from the
@@ -2470,10 +2469,10 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a document view or an element has been scrolled. This event type is dispatched
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a document view or an element has been scrolled. This event type is dispatched
after the scroll has occurred.</p>
- <p id="scroll-document">When dispatched on the <code>Document</code> element, this event type <span class="must">must</span> bubble to the <a class="def" href="#glossary-defaultView"><code>
+ <p id="scroll-document">When dispatched on the <code>Document</code> element, this event type MUST bubble to the <a class="def" href="#glossary-defaultView"><code>
defaultView</code></a> object.</p>
</dd>
</dl>
@@ -2510,9 +2509,9 @@
<dd>
<p>Used to identify a secondary <a href="#events-EventTarget"><code>EventTarget</code></a> related to a Focus event, depending on the type of event.</p>
- <p>For security reasons with nested browsing contexts, when tabbing into or out of a nested context, the relevant EventTarget <span class="should">should</span> be <code>null</code>.</p>
-
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>null</code>.</p>
+ <p>For security reasons with nested browsing contexts, when tabbing into or out of a nested context, the relevant EventTarget SHOULD be <code>null</code>.</p>
+
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>null</code>.</p>
</dd>
</dl>
@@ -2543,22 +2542,22 @@
<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 <span class="may">may</span> 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.
+ 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 <span class="must">must</span> only be part of the document or documents in the window, never a part of the browser or operating system,
+ 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,
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> <span class="may">may</span> define specific elements which might receive focus, the conditions under which an element <span class="may">may</span> receive focus, the means by which
- focus <span class="may">may</span> 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
+ 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),
- but not by tabbing to it. Documents <span class="may">may</span> contain multiple focus rings. Other specifications <span class="may">may</span> define a more complex focus model than is described in this specification,
+ 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>
@@ -2615,8 +2614,8 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses
- focus. The focus <span class="must">must</span> be taken from the element before the dispatch of this event type. This event type is similar to <a class="eventtype" href="#event-type-focusout">
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses
+ focus. The focus MUST be taken from the element before the dispatch of this event type. This event type is similar to <a class="eventtype" href="#event-type-focusout">
<code>focusout</code></a>, but is dispatched after focus is shifted, and does not bubble.</p>
</dd>
</dl>
@@ -2673,8 +2672,8 @@
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives
- focus. The focus <span class="must">must</span> be given to the element before the dispatch of this event type. This event type <span class="must">must</span> be dispatched after the event type <a class="eventtype"
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives
+ focus. The focus 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
@@ -2732,8 +2731,8 @@
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses
- focus. The focus <span class="must">must</span> be taken from the element before the dispatch of this event type. This event type <span class="must">must</span> be dispatched after the event type <a class="eventtype"
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> loses
+ focus. The focus 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
@@ -2795,8 +2794,8 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives
- focus. The focus <span class="must">must</span> be given to the element before the dispatch of this event type. This event type is similar to <a class="eventtype" href="#event-type-focusIn">
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> receives
+ focus. The focus MUST be given to the element before the dispatch of this event type. This event type is similar to <a class="eventtype" href="#event-type-focusIn">
<code>focusin</code></a>, but is dispatched after focus is shifted, and does not bubble.</p>
</dd>
</dl>
@@ -2855,8 +2854,8 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about
- to receive focus. This event type <span class="must">must</span> be dispatched before the element is given focus. The <a class="def" href="#glossary-event-target">event target</a> <span class="must">must</span>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about
+ to receive focus. This event type MUST be dispatched before the element is given focus. The <a class="def" href="#glossary-event-target">event target</a> MUST
be the element which is about to receive focus. This event type is similar to <a class="eventtype" href="#event-type-focus"><code>focus</code></a>, but is dispatched
before focus is shifted, and does bubble.</p>
@@ -2921,8 +2920,8 @@
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about
- to lose focus. This event type <span class="must">must</span> be dispatched before the element loses focus. The <a class="def" href="#glossary-event-target">event target</a> <span class="must">must</span> be the
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when an <a class="def" href="#glossary-event-target">event target</a> is about
+ to lose focus. This event type MUST be dispatched before the element loses focus. The <a class="def" href="#glossary-event-target">event target</a> MUST be the
element which is about to lose focus. This event type is similar to <a class="eventtype" href="#event-type-blur"><code>blur</code></a>, but is dispatched before
focus is shifted, and does bubble.</p>
</dd>
@@ -2961,35 +2960,35 @@
<dd>
<p>The horizontal coordinate at which the event occurred relative to the origin of the screen coordinate system.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute long screenY</dt>
<dd>
<p>The vertical coordinate at which the event occurred relative to the origin of the screen coordinate system.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute long clientX</dt>
<dd>
<p>The horizontal coordinate at which the event occurred relative to the viewport associated with the event.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute long clientY</dt>
<dd>
<p>The vertical coordinate at which the event occurred relative to the viewport associated with the event.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute boolean ctrlKey</dt>
<dd>
<p>Refer to the <a href="#events-KeyboardEvent-ctrlKey"><code>KeyboardEvent.ctrlKey</code></a> attribute.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute boolean shiftKey</dt>
@@ -3006,22 +3005,22 @@
<dd>
<p>Refer to the <a href="#events-KeyboardEvent-metaKey"><code>KeyboardEvent.metaKey</code></a> attribute.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute unsigned short button</dt>
<dd>
- <p>During mouse events caused by the depression or release of a mouse button, <code>button</code> <span class="must">must</span> be used to indicate which pointer device button changed state.</p>
- <p>The value of the <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> attribute <span class="must">must</span> be as follows:</p>
+ <p>During mouse events caused by the depression or release of a mouse button, <code>button</code> MUST be used to indicate which pointer device button changed state.</p>
+ <p>The value of the <a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> attribute MUST be as follows:</p>
<ul>
- <li><code>0</code> <span class="must">must</span> 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
+ <li><code>0</code> MUST indicate the primary button of the device (in general, the left button or the only button on single-button devices, used to activate a user
interface control or select text) or the un-initialized value.</li>
- <li><code>1</code> <span class="must">must</span> indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).</li>
- <li><code>2</code> <span class="must">must</span> indicate the secondary button (in general, the right button, often used to display a context menu).</li>
+ <li><code>1</code> MUST indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).</li>
+ <li><code>2</code> MUST indicate the secondary button (in general, the right button, often used to display a context menu).</li>
</ul>
- <p>Some pointing devices provide or simulate more buttons, and values higher than <code>2</code> <span class="may">may</span> be used to represent such buttons.</p>
+ <p>Some pointing devices provide or simulate more buttons, and values higher than <code>2</code> MAY be used to represent such buttons.</p>
<p class="note"><strong>Note:</strong> The value of <code>button</code> is not updated for events not caused by the depression/release of a mouse button. In these
scenarios, take care not to interpret the value <code>0</code> as the left button, but rather as the <a class="def" href="#glossary-un-initialized-value">un-initialized
@@ -3030,12 +3029,12 @@
<p class="note"><strong>Authoring Note:</strong> Some <a class="def" href="#glossary-default-action">default actions</a> related to events such as
<a class="eventtype"><code>mousedown</code></a> and <a class="eventtype"><code>mouseup</code></a> depend on the specific mouse button in use.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute unsigned short buttons</dt>
<dd>
- <p>During any mouse events, <code>buttons</code> <span class="must">must</span> be used to indicate which combination of mouse buttons are
+ <p>During any mouse events, <code>buttons</code> MUST be used to indicate which combination of mouse buttons are
currently being pressed, expressed as a bitmask.</p>
<p class="note"><strong>Note:</strong> Though similarly named, the values for the <code>buttons</code> attribute and the <a href="#events-MouseEvent-button"><code>button</code></a>
@@ -3043,17 +3042,17 @@
<a class="eventtype"><code>mouseup</code></a> event handlers, whereas the <code>buttons</code> attribute reflects the state of the mouse's buttons for any
trusted <code>MouseEvent</code> object (while it is being dispatched), because it can represent the "no button currently active" state (0).</p>
- <p>The value of the <a href="#events-MouseEvent-buttons"><code>MouseEvent.buttons</code></a> attribute <span class="must">must</span> be as follows:</p>
+ <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> <span class="must">must</span> indicates no button is currently active.</li>
- <li><code>1</code> <span class="must">must</span> 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
+ <li><code>0</code> MUST indicates no button is currently active.</li>
+ <li><code>1</code> MUST indicate the primary button of the device (in general, the left button or the only button on single-button devices, used to activate a user
interface control or select text).</li>
- <li><code>2</code> <span class="must">must</span> indicate the secondary button (in general, the right button, often used to display a context menu), if present.</li>
- <li><code>4</code> <span class="must">must</span> indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).</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>
+ <li><code>4</code> MUST indicate the auxiliary button (in general, the middle button, often combined with a mouse wheel).</li>
</ul>
- <p>Some pointing devices provide or simulate more buttons. To represent such buttons, the value <span class="must">must</span> be doubled for each successive button (in the binary series <code>
+ <p>Some pointing devices provide or simulate more buttons. To represent such buttons, the value MUST be doubled for each successive button (in the binary series <code>
8</code>, <code>16</code>, <code>32</code>, ... ).</p>
<p class="note" id="buttons-mask"><strong>Note:</strong> Because the sum of any set of button values is a unique number, a content author can use a bitwise operation
@@ -3064,14 +3063,14 @@
<p class="note"><strong>Authoring Note: </strong>Some <a class="def" href="#glossary-default-action">default actions</a> related to events such as
<a class="eventtype"><code>mousedown</code></a> and <a class="eventtype"><code>mouseup</code></a> depend on the specific mouse button in use.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute EventTarget? relatedTarget</dt>
<dd>
<p>Used to identify a secondary <a href="#events-EventTarget"><code>EventTarget</code></a> related to a UI event, depending on the type of event.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>null</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>null</code>.</p>
</dd>
<dt>// Deprecated in DOM Level 3</dt>
@@ -3156,7 +3155,7 @@
<dt>EventTarget? relatedTargetArg</dt>
<dd>
- <p>Specifies <a href="#events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a>. This value <span class="may">may</span> be <code>null</code>.</p>
+ <p>Specifies <a href="#events-MouseEvent-relatedTarget"><code>MouseEvent.relatedTarget</code></a>. This value MAY be <code>null</code>.</p>
</dd>
</dl>
</dd>
@@ -3182,7 +3181,7 @@
</dl>
</section>
- <p id="current-click-count">Implementations <span class="must">must</span> maintain the <em>current click count</em> when generating mouse events. This <span class="must">must</span> be a non-negative integer indicating
+ <p id="current-click-count">Implementations MUST maintain the <em>current click count</em> when generating mouse events. This MUST be a non-negative integer indicating
the number of consecutive clicks of a pointing device button within a specific time. The delay after which the count resets is specific to the
environment configuration.</p>
@@ -3258,12 +3257,12 @@
<ol>
<li><a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a></li>
- <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (<span class="optional">optional</span>, multiple events, some limits)</li>
+ <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (OPTIONAL, multiple events, some limits)</li>
<li><a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a></li>
<li><a class="eventtype" href="#event-type-click"><code>click</code></a></li>
- <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (<span class="optional">optional</span>, multiple events, some limits)</li>
+ <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (OPTIONAL, multiple events, some limits)</li>
<li><a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a></li>
- <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (<span class="optional">optional</span>, multiple events, some limits)</li>
+ <li><a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a> (OPTIONAL, multiple events, some limits)</li>
<li><a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a></li>
<li><a class="eventtype" href="#event-type-click"><code>click</code></a></li>
<li><a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a></li>
@@ -3275,16 +3274,16 @@
href="#event-type-dblclick"><code>dblclick</code></a> event will be implementation-, device-, and platform-specific. This tolerance can aid users that have physical
disabilities like unsteady hands when these users interact with a pointing device.</p>
- <p>Each implementation will determine the appropriate hysteresis tolerance, but in general <span class="should">should</span> fire <a class="eventtype" href="#event-type-click"><code>click</code></a>
+ <p>Each implementation will determine the appropriate hysteresis tolerance, but in general SHOULD fire <a class="eventtype" href="#event-type-click"><code>click</code></a>
and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a> events when the event target of the associated <a class="eventtype"
href="#event-type-mousedown"><code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events is the same element with no
<a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> or <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>
- events intervening, and <span class="should">should</span> fire <a class="eventtype" href="#event-type-click"><code>click</code></a> and <a class="eventtype" href="#event-type-dblclick">
+ events intervening, and SHOULD fire <a class="eventtype" href="#event-type-click"><code>click</code></a> and <a class="eventtype" href="#event-type-dblclick">
<code>dblclick</code></a> events on the nearest common ancestor when the event targets of the associated <a class="eventtype" href="#event-type-mousedown">
<code>mousedown</code></a> and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events are different.</p>
<p>If the <a class="def" href="#glossary-event-target">event target</a> (e.g. the target element) is removed from the DOM during the mouse events sequence, the remaining
- events of the sequence <span class="mustnot">must not</span> be fired on that element.</p>
+ events of the sequence MUST NOT be fired on that element.</p>
<div class="example">
<div class="example-title">Example</div>
@@ -3300,7 +3299,7 @@
</section>
<p>The Mouse event types are listed below. In the case of nested elements, mouse event types are always targeted at the most deeply nested element. Ancestors of the
- targeted element <span class="may">may</span> use bubbling to obtain notification of mouse events which occur within its descendent elements.</p>
+ targeted element MAY use bubbling to obtain notification of mouse events which occur within its descendent elements.</p>
<!-- click -->
<div class="event-definition">
@@ -3343,7 +3342,7 @@
<li><a href="#events-event-type-target"><code class="attribute-name">Event.target</code></a>: <a class="def" href="#glossary-topmost-event-target">topmost event target</a></li>
<li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code>defaultView</code></a></li>
<li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: indicates the <a href="#current-click-count">current click count</a>;
- the attribute value <span class="must">must</span> be <code>1</code> when the user begins this action and increments by <code>1</code> for each click.</li>
+ the attribute value MUST be <code>1</code> when the user begins this action and increments by <code>1</code> for each click.</li>
<li><a href="#events-MouseEvent-screenX"><code class="attribute-name">MouseEvent.screenX</code></a>: value based on the pointer position on the screen</li>
<li><a href="#events-MouseEvent-screenY"><code class="attribute-name">MouseEvent.screenY</code></a>: value based on the pointer position on the screen</li>
<li><a href="#events-MouseEvent-clientX"><code class="attribute-name">MouseEvent.clientX</code></a>: value based on the pointer position within the viewport</li>
@@ -3365,17 +3364,17 @@
</tr>
</table>
- <p>The <a class="eventtype" href="#event-type-click"><code>click</code></a> event type <span class="must">must</span> be dispatched on the <a class="def" href="#glossary-topmost-event-target">
+ <p>The <a class="eventtype" href="#event-type-click"><code>click</code></a> event type MUST be dispatched on the <a class="def" href="#glossary-topmost-event-target">
topmost event target</a> indicated by the pointer, when the user presses down and releases the pointer button, or otherwise activates the pointer in a manner that
- simulates such an action. The actuation method of the mouse button depends upon the pointer device and the environment configuration, e.g., it <span class="may">may</span> depend on
+ simulates such an action. The actuation method of the mouse button depends upon the pointer device and the environment configuration, e.g., it MAY depend on
the screen location or the delay between the press and release of the pointing device button.</p>
- <p>The <a class="eventtype" href="#event-type-click"><code>click</code></a> event <span class="may">may</span> be preceded by the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>
+ <p>The <a class="eventtype" href="#event-type-click"><code>click</code></a> event MAY be preceded by the <a class="eventtype" href="#event-type-mousedown"><code>mousedown</code></a>
and <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> events on the same element, disregarding changes between other node types (e.g., text
- nodes). Depending upon the environment configuration, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event <span class="may">may</span> be dispatched if one or
+ nodes). Depending upon the environment configuration, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event MAY be dispatched if one or
more of the event types <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, <a class="eventtype" href="#event-type-mousemove"><code>mousemove</code></a>,
and <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a> occur between the press and release of the pointing device button. The <a class="eventtype"
- href="#event-type-click"><code>click</code></a> event <span class="may">may</span> also be followed by the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>
+ href="#event-type-click"><code>click</code></a> event MAY also be followed by the <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>
event.</p>
<div class="example">
@@ -3388,7 +3387,7 @@
</p>
</div>
- <p>In addition to being associated with pointer devices, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type <span class="must">must</span> be dispatched as
+ <p>In addition to being associated with pointer devices, the <a class="eventtype" href="#event-type-click"><code>click</code></a> event type MUST be dispatched as
part of an element activation, as described in <a href="#event-flow-activation">Activation triggers and behavior</a>.</p>
<p class="note"><strong>Note:</strong> For maximum accessibility, content authors are encouraged to use the <a class="eventtype" href="#event-type-click">
@@ -3407,16 +3406,16 @@
MouseEvent.buttons</code></a> value is <code>1</code>):
<ul>
<li>If the <a class="def" href="#glossary-event-target">event target</a> has associated activation behavior, the <a class="def" href="#glossary-default-action">default
- action</a> <span class="must">must</span> be to execute that activation behavior (see <a href="#event-flow-activation">Activation triggers and behavior</a>).</li>
-
- <li>If the <a class="def" href="#glossary-event-target">event target</a> is focusable, the <a class="def" href="#glossary-default-action">default action</a> <span class="must">must</span> be
+ action</a> MUST be to execute that activation behavior (see <a href="#event-flow-activation">Activation triggers and behavior</a>).</li>
+
+ <li>If the <a class="def" href="#glossary-event-target">event target</a> is focusable, the <a class="def" href="#glossary-default-action">default action</a> MUST be
to give that element document focus.</li>
</ul>
</li>
<li><em>Right click</em> (<a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>1</code>, <a href="#events-MouseEvent-buttons"><code>
MouseEvent.buttons</code></a> value is <code>2</code>):
<ul>
- <li>The <a class="def" href="#glossary-default-action">default action</a> <span class="must">must</span> be to provide a context menu of options related to that <a class="def" href="#glossary-event-target">
+ <li>The <a class="def" href="#glossary-default-action">default action</a> MUST be to provide a context menu of options related to that <a class="def" href="#glossary-event-target">
event target</a>.</li>
</ul>
</li>
@@ -3424,9 +3423,9 @@
MouseEvent.buttons</code></a> value is <code>4</code>):
<ul>
<li>If the <a class="def" href="#glossary-event-target">event target</a> has associated activation behavior, the <a class="def" href="#glossary-default-action">default
- action</a> <span class="must">must</span> be to execute that activation behavior in an alternate fashion (such as opening a link in a new tab or window).</li>
-
- <li>If the <a class="def" href="#glossary-event-target">event target</a> has no associated activation behavior, a user agent <span class="may">may</span> assign a custom <a class="def" href="#glossary-default-action">
+ action</a> MUST be to execute that activation behavior in an alternate fashion (such as opening a link in a new tab or window).</li>
+
+ <li>If the <a class="def" href="#glossary-event-target">event target</a> has no associated activation behavior, a user agent MAY assign a custom <a class="def" href="#glossary-default-action">
default action</a> such as an alternate scrolling or panning mode.</li>
</ul>
</li>
@@ -3497,10 +3496,10 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device button is clicked twice over an element. The definition
- of a double click depends on the environment configuration, except that the event target <span class="must">must</span> be the same between <a class="eventtype" href="#event-type-mousedown">
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device button is clicked twice over an element. The definition
+ of a double click depends on the environment configuration, except that the event target MUST be the same between <a class="eventtype" href="#event-type-mousedown">
<code>mousedown</code></a>, <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a>, and <a class="eventtype" href="#event-type-dblclick"><code>dblclick</code></a>.
- This event type <span class="must">must</span> be dispatched after the event type <a class="eventtype" href="#event-type-click"><code>click</code></a> if a click and double click occur simultaneously,
+ This event type MUST be dispatched after the event type <a class="eventtype" href="#event-type-click"><code>click</code></a> if a click and double click occur simultaneously,
and after the event type <a class="eventtype" href="#event-type-mouseup"><code>mouseup</code></a> otherwise.</p>
<p class="note"><strong>Note:</strong> Canceling the <a class="eventtype" href="#event-type-click"><code>click</code></a> event does not affect the firing
@@ -3517,8 +3516,8 @@
<li><em>Left click</em> (<a href="#events-MouseEvent-button"><code>MouseEvent.button</code></a> value is <code>0</code>, <a href="#events-MouseEvent-buttons"><code>
MouseEvent.buttons</code></a> value is <code>1</code>):
<ul>
- <li>If the <a class="def" href="#glossary-event-target">event target</a> is selectable, the <a class="def" href="#glossary-default-action">default action</a> <span class="must">must</span>
- be to select part or all of the selectable content; subsequent clicks <span class="may">may</span> select additional selectable portions of that content.</li>
+ <li>If the <a class="def" href="#glossary-event-target">event target</a> is selectable, the <a class="def" href="#glossary-default-action">default action</a> MUST
+ be to select part or all of the selectable content; subsequent clicks MAY select additional selectable portions of that content.</li>
</ul>
</li>
</ul>
@@ -3590,7 +3589,7 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device button is pressed over an element.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device button is pressed over an element.</p>
<p class="note"><strong>Note: </strong>Many implementations use the <a class="eventtype"><code>mousedown</code></a> event to begin a variety of contextually dependent <a class="def"
href="#glossary-default-action">default actions</a>. These default actions can be prevented if this event is canceled. Some of these default actions could include: beginning
@@ -3664,9 +3663,9 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device is moved onto the boundaries of an element or one of
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device is moved onto the boundaries of an element or one of
its descendent elements. This event type is similar to <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a>, but differs in that it does
- not bubble, and <span class="mustnot">must not</span> be dispatched when the pointer device moves from an element onto the boundaries of one of its descendent elements.</p>
+ not bubble, and MUST NOT be dispatched when the pointer device moves from an element onto the boundaries of one of its descendent elements.</p>
<p class="note"><strong>Note:</strong> There are similarities between this event type and the CSS <a href="http://www.w3.org/TR/CSS2/selector.html#dynamic-pseudo-classes"
title="Selectors"><code>:hover</code> pseudo-class</a> <a href="#references-CSS2">[CSS2.1]</a>. See also the <a class="eventtype" href="#event-type-mouseleave"><code>
@@ -3738,9 +3737,9 @@
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device is moved off of the boundaries of an element and all
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device is moved off of the boundaries of an element and all
of its descendent elements. This event type is similar to <a class="eventtype" href="#event-type-mouseout"><code>mouseout</code></a>, but differs in that does
- not bubble, and that it <span class="mustnot">must not</span> be dispatched until the pointing device has left the boundaries of the element and the boundaries of all of its children.</p>
+ not bubble, and that it MUST NOT be dispatched until the pointing device has left the boundaries of the element and the boundaries of all of its children.</p>
<p class="note"><strong>Note:</strong> There are similarities between this event type and the CSS <a href="http://www.w3.org/TR/CSS2/selector.html#dynamic-pseudo-classes"
title="Selectors"><code>:hover</code> pseudo-class</a> <a href="#references-CSS2">[CSS2.1]</a>. See also the <a class="eventtype" href="#event-type-mouseenter"><code>
@@ -3811,9 +3810,9 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device is moved while it is over an element. The frequency
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device is moved while it is over an element. The frequency
rate of events while the pointing device is moved is implementation-, device-, and platform-specific, but multiple consecutive <a class="eventtype" href="#event-type-mousemove">
- <code>mousemove</code></a> events <span class="should">should</span> be fired for sustained pointer-device movement, rather than a single event for each instance of mouse movement. Implementations
+ <code>mousemove</code></a> events SHOULD be fired for sustained pointer-device movement, rather than a single event for each instance of mouse movement. Implementations
are encouraged to determine the optimal frequency rate to balance responsiveness with performance.</p>
<p class="note"><strong>Authoring Note: </strong>In some implementation environments, such as a browser, <a class="eventtype"><code>mousemove</code></a> events can continue
@@ -3886,8 +3885,8 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device is moved off of the boundaries of an element. This
- event type is similar to <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>, but differs in that does bubble, and that it <span class="must">must</span> be dispatched
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device is moved off of the boundaries of an element. This
+ event type is similar to <a class="eventtype" href="#event-type-mouseleave"><code>mouseleave</code></a>, but differs in that does bubble, and that it MUST be dispatched
when the pointer device moves from an element onto the boundaries of one of its descendent elements.</p>
<p class="note"><strong>Note:</strong> See also the <a class="eventtype" href="#event-type-mouseover"><code>mouseover</code></a> event type.</p>
@@ -3960,8 +3959,8 @@
</tbody>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device is moved onto the boundaries of an element. This event
- type is similar to <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a>, but differs in that it bubbles, and that it <span class="must">must</span> be dispatched
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device is moved onto the boundaries of an element. This event
+ type is similar to <a class="eventtype" href="#event-type-mouseenter"><code>mouseenter</code></a>, but differs in that it bubbles, and that it MUST be dispatched
when the pointer device moves onto the boundaries of an element whose ancestor element is the <a class="def" href="#glossary-event-target">event target</a> for
the same event listener instance.</p>
@@ -4033,7 +4032,7 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a pointing device button is released over an element.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a pointing device button is released over an element.</p>
<p class="note"><strong>Note: </strong>Many implementations will invoke a context menu as the default action of this event if the right mouse button is being released.</p>
@@ -4065,9 +4064,9 @@
mouse wheel software can support acceleration (the faster the wheel is rotated/moved, the greater the delta of each measurement) or even sub-pixel rotation measurements.
Because of this, authors can not assume a given rotation amount in one user agent will produce the same delta value in all user agents.</p>
- <p>The sign (positive or negative) of the values of the deltaX, deltaY, and deltaZ attributes <span class="must">must</span> be consistent between multiple dispatches of the
+ <p>The sign (positive or negative) of the values of the deltaX, deltaY, and deltaZ attributes MUST be consistent between multiple dispatches of the
<a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event while the motion of the actual wheel device is rotating/moving in the same direction. If a user agent scrolls as the
- default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event then the sign of the delta <span class="should">should</span> be given by a right-hand coordinate system where positive X,
+ default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event then the sign of the delta SHOULD be given by a right-hand coordinate system where positive X,
Y, and Z axes are directed towards the right-most edge, bottom-most edge, and farthest depth (away from the user) of the document, respectively.</p>
<p class="note"><strong>Note:</strong> Individual user agents can (depending on their environment and hardware configuration) interpret the same physical user interaction
@@ -4092,45 +4091,45 @@
<dt>const unsigned long DOM_DELTA_PIXEL = 0x00</dt>
<dd>
- <p>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> <span class="must">must</span> be pixels. This is the most typical case in most operating system and implementation
+ <p>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> MUST be pixels. This is the most typical case in most operating system and implementation
configurations.</p>
</dd>
<dt>const unsigned long DOM_DELTA_LINE = 0x01</dt>
<dd>
- <p>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> <span class="must">must</span> be individual lines of text. This is the case for many form controls.</p>
+ <p>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> MUST be individual lines of text. This is the case for many form controls.</p>
</dd>
<dt>const unsigned long DOM_DELTA_PAGE = 0x02</dt>
<dd>
- <p>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> <span class="must">must</span> be pages, either defined as a single screen or as a demarcated page.</p>
+ <p>The units of measurement for the <a href="#glossary-delta"><code>delta</code></a> MUST be pages, either defined as a single screen or as a demarcated page.</p>
</dd>
<dt>readonly attribute double deltaX</dt>
<dd>
- <p>In user agents where the default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event is to scroll, the value <span class="must">must</span> be the measurement along
+ <p>In user agents where the default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event is to scroll, the value MUST be the measurement along
the x-axis (in pixels, lines, or pages) to be scrolled in the case where the event is not cancelled. Otherwise, this is an implementation-specific
measurement (in pixels, lines, or pages) of the movement of a wheel device around the x-axis.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute double deltaY</dt>
<dd>
- <p>In user agents where the default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event is to scroll, the value <span class="must">must</span> be the measurement along
+ <p>In user agents where the default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event is to scroll, the value MUST be the measurement along
the y-axis (in pixels, lines, or pages) to be scrolled in the case where the event is not cancelled. Otherwise, this is an implementation-specific
measurement (in pixels, lines, or pages) of the movement of a wheel device around the y-axis.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute double deltaZ</dt>
<dd>
- <p>In user agents where the default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event is to scroll, the value <span class="must">must</span> be the measurement along
+ <p>In user agents where the default action of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event is to scroll, the value MUST be the measurement along
the z-axis (in pixels, lines, or pages) to be scrolled in the case where the event is not cancelled. Otherwise, this is an implementation-specific
measurement (in pixels, lines, or pages) of the movement of a wheel device around the z-axis.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
<dt>readonly attribute unsigned long deltaMode</dt>
@@ -4138,10 +4137,10 @@
<p>The <code>deltaMode</code> attribute contains an indication of the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values.
The default value is <a href="#events-DOM_DELTA_PIXEL"><code class="constant-name">DOM_DELTA_PIXEL</code></a> (pixels).</p>
- <p>This attribute <span class="must">must</span> be set to one of the DOM_DELTA constants to indicate the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values. The precise measurement
+ <p>This attribute MUST be set to one of the DOM_DELTA constants to indicate the units of measurement for the <a href="#glossary-delta"><code>delta</code></a> values. The precise measurement
is specific to device, operating system, and application configurations.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
</dd>
</dl>
@@ -4225,13 +4224,13 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a mouse wheel has been rotated around any axis, or when an equivalent
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a mouse wheel has been rotated around any axis, or when an equivalent
input device (such as a mouse-ball, certain tablets or touchpads, etc.) has emulated such an action. Depending on the platform and input device, diagonal wheel
- deltas <span class="may">may</span> be delivered either as a single <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event with multiple non-zero axes or as separate <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a>
+ deltas MAY be delivered either as a single <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event with multiple non-zero axes or as separate <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a>
events for each non-zero axis.</p>
<p>The typical <a class="def" href="#glossary-default-action">default action</a> of the <a class="eventtype" href="#event-type-wheel"><code>wheel</code></a> event
- type is to scroll (or in some cases, zoom) the document by the indicated amount. If this event is canceled, the implementation <span class="mustnot">must not</span> scroll or zoom the document
+ type is to scroll (or in some cases, zoom) the document by the indicated amount. If this event is canceled, the implementation MUST NOT scroll or zoom the document
(or perform whatever other implementation-specific default action is associated with this event type).</p>
<p class="note"><strong>Note:</strong> In some <a class="def" href="#glossary-user-agent">user agents</a>, or with some input devices, the speed that the wheel has been
@@ -4276,7 +4275,7 @@
<dt>const unsigned long DOM_KEY_LOCATION_STANDARD = 0x00</dt>
<dd>
- <p>The key activation <span class="mustnot">must not</span> be distinguished as the left or right version of the key, and did not originate from the numeric keypad (or did not originate with
+ <p>The key activation MUST NOT be distinguished as the left or right version of the key, and did not originate from the numeric keypad (or did not originate with
a virtual key corresponding to the numeric keypad).</p>
<div class="example">
@@ -4337,27 +4336,27 @@
<dt>readonly attribute DOMString char</dt>
<dd>
- <p><code>char</code> holds the character value of the key pressed. If the key press has a printed representation, then the value <span class="must">must</span> be a non-empty Unicode character
+ <p><code>char</code> holds the character value of the key pressed. If the key press has a printed representation, then the value MUST be a non-empty Unicode character
string, conforming to the <a href="#key-algorithm">algorithm for determining the key value</a> defined in this specification. For a key associated with a macro
to insert multiple characters, the value of the <code>char</code> attribute will hold the entire sequence of characters. For a key which does not have a character
- representation, the value <span class="must">must</span> be the <a class="def" href="#glossary-empty-string">empty string</a>.</p>
+ 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
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 <span class="must">must</span> be <code>""</code> (the empty string).</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>
<dt>readonly attribute DOMString key</dt>
<dd>
- <p><code>key</code> holds the key value of the key pressed. If the value is has a printed representation, it <span class="must">must</span> match the value of the <a href="#events-KeyboardEvent-char">
- <code>KeyboardEvent.char</code></a> attribute; if the value is a control key which has no printed representation, it <span class="must">must</span> be one of the key values defined in the
+ <p><code>key</code> holds the key value of the key pressed. If the value is has a printed representation, it MUST match the value of the <a href="#events-KeyboardEvent-char">
+ <code>KeyboardEvent.char</code></a> attribute; if the value is a control key which has no printed representation, it MUST be one of the key values defined in the
<a href="#keys-keyvalues">key values set</a>, as determined by the <a href="#key-algorithm">algorithm for determining the key value</a>. Implementations that are
- unable to identify a key <span class="must">must</span> use the key value <a href="#key-Unidentified"><code class="key">'Unidentified'</code></a>.</p>
+ 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>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</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>
<dt>readonly attribute unsigned long location</dt>
@@ -4365,31 +4364,31 @@
<p>The <code>location</code> attribute contains an indication of the location of the key on the device, as described in <a href="#events-ID-KeyboardEvent-KeyLocationCode">
Keyboard event types</a>.</p>
- <p>This attribute <span class="must">must</span> be set to one of the DOM_KEY_LOCATION constants to indicate the location of a key on the device. In case a DOM implementation wishes to provide a new location value, a
- value different from the defined constant values <span class="must">must</span> be used.</p>
-
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>0</code>.</p>
+ <p>This attribute MUST be set to one of the DOM_KEY_LOCATION constants to indicate the location of a key on the device. In case a DOM implementation wishes to provide a new location value, a
+ value different from the defined constant values MUST be used.</p>
+
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>0</code>.</p>
</dd>
<dt>readonly attribute boolean ctrlKey</dt>
<dd>
<p><code>true</code> if the <a href="#key-Control"><code class="key">'Control'</code></a> (control) key modifier was active.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute boolean shiftKey</dt>
<dd>
<p><code>true</code> if the shift (Shift) key modifier was active.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute boolean altKey</dt>
<dd>
<p><code>true</code> if the <a href="#key-Alt"><code class="key">'Alt'</code></a> (alternative) or <code>Option</code> key modifier was active.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute boolean metaKey</dt>
@@ -4398,24 +4397,24 @@
<p class="note"><strong>Note:</strong> The <code>'Command'</code> key modifier on Macintosh systems is represented using this key modifier.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute boolean repeat</dt>
<dd>
- <p><code>true</code> if the key has been pressed in a sustained manner. Holding down a key <span class="must">must</span> result in the repeating the events
+ <p><code>true</code> if the key has been pressed in a sustained manner. Holding down a key MUST result in the repeating the events
<a class="eventtype" href="#event-type-keydown"><code>keydown</code></a>, <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a>
(when supported by the user agent) in this order, at a rate determined by the system configuration. For mobile devices which have <em>long-key-press</em>
- behavior, the first key event with a <a href="#events-KeyboardEvent-repeat">repeat</a> attribute value of <code>'true'</code> <span class="must">must</span> serve as an
- indication of a <em>long-key-press</em>. The length of time that the key <span class="must">must</span> be pressed in order to begin repeating is configuration-dependent.</p>
-
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>false</code>.</p>
+ behavior, the first key event with a <a href="#events-KeyboardEvent-repeat">repeat</a> attribute value of <code>'true'</code> MUST serve as an
+ indication of a <em>long-key-press</em>. The length of time that the key MUST be pressed in order to begin repeating is configuration-dependent.</p>
+
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
<dt>readonly attribute DOMString locale</dt>
<dd>
<p>The <code>locale</code> <code>DOMString</code> attribute contains a BCP-47 tag [<a href="#ref-BCP-47">BCP-47</a>] indicating the locale for which the keyboard originating
- the event is configured, e.g. <code>"en-US"</code>. The <code>locale</code> <span class="may">may</span> be the <a class="def" href="#glossary-empty-string">empty string</a> when inapplicable
+ the event is configured, e.g. <code>"en-US"</code>. The <code>locale</code> MAY be the <a class="def" href="#glossary-empty-string">empty string</a> when inapplicable
or unknown, e.g. when this information is not exposed by the underlying platform.</p>
<p class="note"><strong>Note:</strong> <code>locale</code> does not necessarily indicate the locale of the data or the context in which
@@ -4423,7 +4422,7 @@
will still indicate French. Nor can it be used to definitively calculate the <q>physical</q> or <q>virtual</q> key associated with the event, or the character
printed on that key.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</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>
<dt>boolean getModifierState()</dt>
@@ -4445,7 +4444,7 @@
<a href="#key-Shift"><code class="key">'Shift'</code></a>
<a href="#key-SymbolLock"><code class="key">'SymbolLock'</code></a>, and
<a href="#key-OS"><code class="key">'OS'</code></a>
- User agents <span class="may">may</span> support additional implementation-specific modifier keys depending on the environment.</p>
+ User agents MAY support additional implementation-specific modifier keys depending on the environment.</p>
<p>Returns <code>true</code> if it is a modifier key and the modifier is activated, <code>false</code> otherwise.</p>
@@ -4484,7 +4483,7 @@
<li><a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> (only for keys which produce a <a class="def" href="#glossary-character-value">character
value</a>)</li>
- <li>If the key is depressed for a sustained period, the following events <span class="may">may</span> repeat at an environment-dependent rate: <!-- and the key should seek counseling -->
+ <li>If the key is depressed for a sustained period, the following events MAY repeat at an environment-dependent rate: <!-- and the key should seek counseling -->
<ul>
<li><a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> (with <a href="#events-KeyboardEvent-repeat">repeat</a> attribute set to <code>
true</code>)</li>
@@ -4503,7 +4502,7 @@
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
- is often an HTML <code>input</code> element or a textual element which is editable, but <span class="may">may</span> be an element defined by the <a class="def" href="#glossary-host-language">
+ 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
is in focus, the event target will be the root element.</p>
@@ -4579,32 +4578,32 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a key is pressed down. The <a class="eventtype" href="#event-type-keydown">
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a key is pressed down. The <a class="eventtype" href="#event-type-keydown">
<code>keydown</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This
- event type <span class="must">must</span> be generated after the <a class="def" href="#glossary-key-mapping">key mapping</a>. This event type <span class="must">must</span> be dispatched before the <a class="eventtype"
+ event type MUST be generated after the <a class="def" href="#glossary-key-mapping">key mapping</a>. This event type MUST be dispatched before the <a class="eventtype"
href="#event-type-keypress"><code>keypress</code></a> and <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> events event associated with the
same key.</p>
<p>The default action of the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event depends upon the key:</p>
<ul>
- <li>if the key is associated with a character, the default action <span class="must">must</span> 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 <span class="must">must</span>
+ <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 <span class="must">must</span> 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 <span class="must">must</span> 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
- current focus is on a state-changing element, the default action <span class="must">must</span> be to dispatch a <a class="eventtype" href="#event-type-click"><code>click</code></a> event,
+ 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>
</ul>
- <p>If this event is canceled, the associated event types <span class="mustnot">must not</span> be dispatched, and the associated actions <span class="mustnot">must not</span> be performed.</p>
+ <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">
<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
@@ -4677,11 +4676,11 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a key is pressed down, if and only if that key normally produces a <a
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a key is pressed down, if and only if that key normally produces a <a
class="def" href="#glossary-character-value">character value</a>. The <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event type is device
- dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This event type <span class="must">must</span> be generated after the <a class="def"
- href="#glossary-key-mapping">key mapping</a>. It <span class="mustnot">must not</span> be fired when using an <a class="def" href="#glossary-ime">input method editor</a>. This event type
- <span class="must">must</span> 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">
+ dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This event type MUST be generated after the <a class="def"
+ href="#glossary-key-mapping">key mapping</a>. It MUST NOT be fired when using an <a class="def" href="#glossary-ime">input method editor</a>. This event type
+ MUST be dispatched after the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event and before the <a class="eventtype" href="#event-type-keyup">
<code>keyup</code></a> event associated with the same key.</p>
<p class="note"><strong>Note:</strong> the <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> event is traditionally associated with detecting a
@@ -4755,9 +4754,9 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a key is released. The <a class="eventtype" href="#event-type-keyup">
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a key is released. The <a class="eventtype" href="#event-type-keyup">
<code>keyup</code></a> event type is device dependent and relies on the capabilities of the input devices and how they are mapped in the operating system. This
- event type <span class="must">must</span> be generated after the <a class="def" href="#glossary-key-mapping">key mapping</a>. This event type <span class="must">must</span> be dispatched after the <a class="eventtype"
+ event type MUST be generated after the <a class="def" href="#glossary-key-mapping">key mapping</a>. This event type MUST be dispatched after the <a class="eventtype"
href="#event-type-keydown"><code>keydown</code></a> and <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a> events event associated with
the same key.</p>
@@ -4788,7 +4787,7 @@
for relevent event ordering.</p>
<p>Not all <a class="def" href="#glossary-ime">IME</a> systems or devices expose the necessary data to the DOM, so the active composition string (the <q>Reading Window</q>
- or <q>candidate selection menu option</q>) might not be available through this interface, in which case the selection <span class="may">may</span> be represented by the <a class="def" href="#glossary-empty-string">
+ or <q>candidate selection menu option</q>) might not be available through this interface, in which case the selection MAY be represented by the <a class="def" href="#glossary-empty-string">
empty string</a>.</p>
<section id="interface-CompositionEvent">
@@ -4807,18 +4806,18 @@
<dl class="idl" title="interface CompositionEvent : UIEvent">
<dt>readonly attribute DOMString? data</dt>
<dd>
- <p><code>data</code> holds the value of the characters generated by an input method. This <span class="may">may</span> be a single Unicode character or a non-empty sequence of Unicode characters
- [<cite><a class="normative" href="#references-Unicode">Unicode</a></cite>]. Characters <span class="should">should</span> be normalized as defined by the Unicode normalization form <em>NFC</em>,
- defined in [<cite><a class="normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute <span class="may">may</span> be null or contain the <a class="def" href="#glossary-empty-string">
+ <p><code>data</code> holds the value of the characters generated by an input method. This MAY be a single Unicode character or a non-empty sequence of Unicode characters
+ [<cite><a class="normative" href="#references-Unicode">Unicode</a></cite>]. Characters SHOULD be normalized as defined by the Unicode normalization form <em>NFC</em>,
+ defined in [<cite><a class="normative" href="#references-UnicodeNormalization">UAX #15</a></cite>]. This attribute MAY be null or contain the <a class="def" href="#glossary-empty-string">
empty string</a>.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</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>
<dt>readonly attribute DOMString locale</dt>
<dd>
<p>The <code>locale</code> <code>DOMString</code> attribute contains a BCP-47 tag [<a href="#ref-BCP-47">BCP-47</a>] indicating the locale for which the IME originating
- the event is configured, e.g. <code>"ja"</code>, <code>"zh-Hans"</code>, <code>"ko"</code>. <span class="may">May</span> be the <a class="def" href="#glossary-empty-string">empty string</a>
+ the event is configured, e.g. <code>"ja"</code>, <code>"zh-Hans"</code>, <code>"ko"</code>. MAY be the <a class="def" href="#glossary-empty-string">empty string</a>
when inapplicable or unknown, e.g. when this information is not exposed by the underlying platform or application.</p>
<p class="note"><strong>Note:</strong> <code>locale</code> does not necessarily indicate the locale of the data or the context in
@@ -4826,7 +4825,7 @@
will still indicate French, even though the data is actually English. Similarly, an IME application could fail to distinguish between the locale of Chinese and
Kanji characters.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</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>
</dl>
@@ -4910,18 +4909,18 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition
system</a> is 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 <span class="may">may</span> rely upon the capabilities of the text conversion system and how it is
+ 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 <span class="may">may</span> send this event type without keyboard events. Some implemenations <span class="may">may</span> populate the
+ but speech or handwriting recognition systems MAY send this event type without keyboard events. Some implemenations MAY populate the
<a href="#events-CompositionEvent-data"><code>data</code></a> attribute of the <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> event
with the text currently selected in the document (for editing and replacement); otherwise, the value of the <a href="#events-CompositionEvent-data"><code>data</code></a>
- attribute <span class="must">must</span> be the <a class="def" href="#glossary-empty-string">empty string</a>.</p>
-
- <p>This event <span class="must">must</span> be dispatched immediately before a <a class="def" href="#glossary-text-composition-system">text composition system</a> begins a new composition session, and
+ 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
before the DOM is modified due to the composition process. The default action of this event is for the <a class="def" href="#glossary-text-composition-system">text
- composition system</a> to start a new composition session. If this event is canceled, the <a class="def" href="#glossary-text-composition-system">text composition system</a> <span class="should">should</span>
+ composition system</a> to start a new composition session. If this event is canceled, the <a class="def" href="#glossary-text-composition-system">text composition system</a> SHOULD
discard the current composition session.</p>
<p class="note"><strong>Note: </strong>Canceling the <a class="eventtype" href="#event-type-compositionstart"><code>compositionstart</code></a> <em>event type</em> is distinct
@@ -4977,14 +4976,14 @@
<li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code>defaultView</code></a></li>
<li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>0</code></li>
<li><a href="#events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: the string comprising the current results of the composition
- session, which <span class="may">may</span> be the <a class="def" href="#glossary-empty-string">empty string</a> if the content has been deleted</li>
+ session, which MAY be the <a class="def" href="#glossary-empty-string">empty string</a> if the content has been deleted</li>
<li><a href="#events-CompositionEvent-locale"><code class="attribute-name">CompositionEvent.locale</code></a>: the language code for the composition event, if available;
otherwise, the <a class="def" href="#glossary-empty-string">empty string</a></li>
</ul>
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="should">should</span> dispatch this event during a composition session when a <a class="def" href="#glossary-text-composition-system">
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> SHOULD dispatch this event during a composition session when a <a class="def" href="#glossary-text-composition-system">
text composition system</a> updates its active text passage with a new character, which is added to the string in <a href="#events-CompositionEvent-data"><code>CompositionEvent.data</code></a>.
Some <a class="def" href="#glossary-text-composition-system">text composition systems</a> might not expose this information to the DOM, in which case this event will not fire
during the composition process. If the composition session is canceled, this event will be fired immediately before the <a class="eventtype" href="#event-type-compositionend">
@@ -5036,14 +5035,14 @@
<li><a href="#events-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>: <a class="def" href="#glossary-defaultView"><code>defaultView</code></a></li>
<li><a href="#events-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>: <code>0</code></li>
<li><a href="#events-CompositionEvent-data"><code class="attribute-name">CompositionEvent.data</code></a>: the string comprising the final result of the composition
- session, which <span class="may">may</span> be the <a class="def" href="#glossary-empty-string">empty string</a> if the content has been deleted or if the composition process has been canceled</li>
+ session, which MAY be the <a class="def" href="#glossary-empty-string">empty string</a> if the content has been deleted or if the composition process has been canceled</li>
<li><a href="#events-CompositionEvent-locale"><code class="attribute-name">CompositionEvent.locale</code></a>: the language code for the composition event, if available;
otherwise, the <a class="def" href="#glossary-empty-string">empty string</a></li>
</ul>
</td>
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a <a class="def" href="#glossary-text-composition-system">text composition
system</a> completes or cancels the current composition session.</p>
<p>This event is dispatched immediately after the <a class="def" href="#glossary-text-composition-system">text composition system</a> completes the composition session
@@ -5104,12 +5103,12 @@
<dt>readonly attribute Node? relatedNode</dt>
<dd>
- <p><code>relatedNode</code> <span class="must">must</span> be used to identify a secondary node related to a mutation event. For example, if a mutation event is dispatched to a node indicating
+ <p><code>relatedNode</code> MUST be used to identify a secondary node related to a mutation event. For example, if a mutation event is dispatched to a node indicating
that its parent has changed, the <code>relatedNode</code> will be the changed parent. If an event is instead dispatched to a subtree indicating a node was changed
- within it, the <code>relatedNode</code> <span class="must">must</span> be the changed node. In the case of the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
+ within it, the <code>relatedNode</code> MUST be the changed node. In the case of the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
event it indicates the <code>Attr</code> node which was modified, added, or removed.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>null</code>.</p>
+ <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>null</code>.</p>
</dd>
<dt>readonly attribute DOMString prevValue</dt>
@@ -5118,7 +5117,7 @@
events, and of the <code>CharacterData</code> node in <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a>
events.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</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>
<dt>readonly attribute DOMString newValue</dt>
@@ -5127,7 +5126,7 @@
events, and of the <code>CharacterData</code> node in <a class="eventtype" href="#event-type-DOMCharacterDataModified"><code>DOMCharacterDataModified</code></a>
events.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</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>
<dt>readonly attribute DOMString attrName</dt>
@@ -5135,7 +5134,7 @@
<p><code>attrName</code> indicates the name of the changed <code>Attr</code> node in a <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
event.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> be <code>""</code> (the empty string).</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>
<dt>readonly attribute unsigned short attrChange</dt>
@@ -5143,7 +5142,7 @@
<p><code>attrChange</code> indicates the type of change which triggered the <a class="eventtype" href="#event-type-DOMAttrModified"><code>DOMAttrModified</code></a>
event. The values can be <code>MODIFICATION</code>, <code>ADDITION</code>, or <code>REMOVAL</code>.</p>
- <p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute <span class="must">must</span> 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>.</p>
<p class="warning"><strong>Warning:</strong> There is no defined constant for the attrChange value of 0 (the un-initialized value).</p>
</dd>
@@ -5174,25 +5173,25 @@
<dt>DOMString prevValueArg</dt>
<dd>
- <p>Specifies <a href="#events-MutationEvent-prevValue"><code>MutationEvent.prevValue</code></a>. This value <span class="may">may</span> be the <a class="def" href="#glossary-empty-string">
+ <p>Specifies <a href="#events-MutationEvent-prevValue"><code>MutationEvent.prevValue</code></a>. This value MAY be the <a class="def" href="#glossary-empty-string">
empty string</a>.</p>
</dd>
<dt>DOMString newValueArg</dt>
<dd>
- <p>Specifies <a href="#events-MutationEvent-newValue"><code>MutationEvent.newValue</code></a>. This value <span class="may">may</span> be the <a class="def" href="#glossary-empty-string">empty
+ <p>Specifies <a href="#events-MutationEvent-newValue"><code>MutationEvent.newValue</code></a>. This value MAY be the <a class="def" href="#glossary-empty-string">empty
string</a>.</p>
</dd>
<dt>DOMString attrNameArg</dt>
<dd>
- <p>Specifies <a href="#events-MutationEvent-attrName"><code>MutationEvent.attrName</code></a>. This value <span class="may">may</span> be the <a class="def" href="#glossary-empty-string">empty
+ <p>Specifies <a href="#events-MutationEvent-attrName"><code>MutationEvent.attrName</code></a>. This value MAY be the <a class="def" href="#glossary-empty-string">empty
string</a>.</p>
</dd>
<dt>unsigned short attrChangeArg</dt>
<dd>
- <p>Specifies <a href="#events-MutationEvent-attrChange"><code>MutationEvent.attrChange</code></a>. This value <span class="may">may</span> be <code>0</code>.</p>
+ <p>Specifies <a href="#events-MutationEvent-attrChange"><code>MutationEvent.attrChange</code></a>. This value MAY be <code>0</code>.</p>
</dd>
</dl>
@@ -5256,8 +5255,8 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event after an <code>Attr.value</code> has been modified and after an <code>Attr</code>
- node has been added to or removed from an <code>Element</code>. The <a class="def" href="#glossary-event-target">event target</a> of this event <span class="must">must</span> be the <code>Element</code>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event after an <code>Attr.value</code> has been modified and after an <code>Attr</code>
+ node has been added to or removed from an <code>Element</code>. The <a class="def" href="#glossary-event-target">event target</a> of this event MUST be the <code>Element</code>
node where the change occurred. It is implementation dependent whether this event type occurs when the children of the <code>Attr</code> node are changed in ways
that do not affect the value of <code>Attr.value</code>.</p>
@@ -5318,8 +5317,8 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event after <code>CharacterData.data</code> or <code>ProcessingInstruction.data</code>
- 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 <span class="must">must</span>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event after <code>CharacterData.data</code> or <code>ProcessingInstruction.data</code>
+ 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>
@@ -5383,10 +5382,10 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event type when a node other than an <code>Attr</code> node has been added as a child
- of another node. A <a class="def" href="#glossary-user-agent">user agent</a> <span class="may">may</span> dispatch this event when an <code>Attr</code> node has been added to an <code>Element</code>
- node (see <a href="#DOMNodeInserted-attr">note</a> below). This event <span class="must">must</span> be dispatched after the insertion has taken place. The <a class="def" href="#glossary-event-target">
- event target</a> of this event <span class="must">must</span> be the node being inserted.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event type when a node other than an <code>Attr</code> node has been added as a child
+ of another node. A <a class="def" href="#glossary-user-agent">user agent</a> MAY dispatch this event when an <code>Attr</code> node has been added to an <code>Element</code>
+ node (see <a href="#DOMNodeInserted-attr">note</a> below). This event MUST be dispatched after the insertion has taken place. The <a class="def" href="#glossary-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>
event type instead.</p>
@@ -5451,11 +5450,11 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a node has been inserted into a document, either through direct insertion
- of the node or insertion of a subtree in which it is contained; a <a class="def" href="#glossary-user-agent">user agent</a> <span class="may">may</span> treat an <code>Attr</code>
- node as part of an <code>Element</code>'s subtree. This event <span class="must">must</span> be dispatched after the insertion has taken place. The <a class="def" href="#glossary-event-target">
- event target</a> of this event <span class="must">must</span> 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> <span class="must">must</span> occur before this event type.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a node has been inserted into a document, either through direct insertion
+ of the node or insertion of a subtree in which it is contained; a <a class="def" href="#glossary-user-agent">user agent</a> MAY treat an <code>Attr</code>
+ node as part of an <code>Element</code>'s subtree. This event MUST be dispatched after the insertion has taken place. The <a class="def" href="#glossary-event-target">
+ 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>
event type is defined in this specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the
@@ -5518,10 +5517,10 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a node other than an <code>Attr</code> node is being removed from its
- parent node. A <a class="def" href="#glossary-user-agent">user agent</a> <span class="may">may</span> dispatch this event when an <code>Attr</code> node is being removed from its <code>ownerElement</code>
- (see <a href="#DOMNodeRemoved-attr">note</a> below). This event <span class="must">must</span> be dispatched before the removal takes place. The <a class="def" href="#glossary-event-target">
- event target</a> of this event <span class="must">must</span> be the node being removed.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a node other than an <code>Attr</code> node is being removed from its
+ parent node. A <a class="def" href="#glossary-user-agent">user agent</a> MAY dispatch this event when an <code>Attr</code> node is being removed from its <code>ownerElement</code>
+ (see <a href="#DOMNodeRemoved-attr">note</a> below). This event MUST be dispatched before the removal takes place. The <a class="def" href="#glossary-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>
event type instead.</p>
@@ -5587,11 +5586,11 @@
</tr>
</table>
- <p>A <a class="def" href="#glossary-user-agent">user agent</a> <span class="must">must</span> dispatch this event when a node is being removed from a document, either through direct removal
- of the node or removal of a subtree in which it is contained; a <a class="def" href="#glossary-user-agent">user agent</a> <span class="may">may</span> treat an <code>Attr</code>
- node as part of an <code>Element</code>'s subtree. This event <span class="must">must</span> be dispatched before the removal takes place. The <a class="def" href="#glossary-event-target">event
- target</a> of this event type <span class="must">must</span> 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> <span class="must">must</span> occur before this event type.</p>
+ <p>A <a class="def" href="#glossary-user-agent">user agent</a> MUST dispatch this event when a node is being removed from a document, either through direct removal
+ of the node or removal of a subtree in which it is contained; a <a class="def" href="#glossary-user-agent">user agent</a> MAY treat an <code>Attr</code>
+ node as part of an <code>Element</code>'s subtree. This event MUST be dispatched before the removal takes place. The <a class="def" href="#glossary-event-target">event
+ 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>
event type instead.</p>
@@ -5656,10 +5655,10 @@
</tr>
</table>
- <p>This is a general event for notification of all changes to the document. It can be used instead of the more specific mutation and mutation name events. It <span class="may">may</span> be
- dispatched after a single modification to the document or, at the implementation's discretion, after multiple changes have occurred. The latter case <span class="should">should</span> generally
- be used to accommodate multiple changes which occur either simultaneously or in rapid succession. The target of this event <span class="must">must</span> be the lowest common parent of the
- changes which have taken place. This event <span class="must">must</span> be dispatched after any other events caused by the mutation(s) have occurred.</p>
+ <p>This is a general event for notification of all changes to the document. It can be used instead of the more specific mutation and mutation name events. It MAY be
+ dispatched after a single modification to the document or, at the implementation's discretion, after multiple changes have occurred. The latter case SHOULD generally
+ 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
specification for reference and completeness, but this specification <a class="def" href="#glossary-deprecated">deprecates</a> the use of this event type.</p>
@@ -5714,7 +5713,7 @@
'8'</code>, or <code class="glyph">'ш'</code>), or names or symbols which indicate that key's function (such as an upward-pointing arrow <code class="glyph">⇧</code> indicating
<code class="key">'Shift'</code>, or the string <code>'Enter'</code>). Keys are often referred to by this marking (e.g., <q>Press the <code>
'Shift'</code> and <code>'F'</code> keys.</q>). However, the visual appearance of the key has no bearing on its digital representation, and
- in many configurations <span class="may">may</span> be completely inaccurate; even the control and function keys, such as <code>'Enter'</code>, <span class="may">may</span> be mapped to different
+ in many configurations MAY be completely inaccurate; even the control and function keys, such as <code>'Enter'</code>, MAY be mapped to different
functionality, or even mapped as character keys.</p>
<p>For historical reasons, the character keys are typically marked with the capital-letter equivalents of the character value they produce, e.g., the <code>
@@ -5743,11 +5742,11 @@
Latin Capital Letter A). If the keyboard layout mapping is switched to a Serbian (Cyrillic) mapping, pressing the same key will produce the character <code class="glyph">
'љ'</code> (<code class="char">'\u0459'</code>, Cyrillic Small Letter LJE).</p>
- <p>However, the physical layout of the keys <span class="may">may</span> be of interest to content authors developing games or other applications in which the location of the keys has an ergonomic
+ <p>However, the physical layout of the keys MAY be of interest to content authors developing games or other applications in which the location of the keys has an ergonomic
relationship as the desired user interface controls, with little or no attention paid to the representational value of the key itself. For example, many games
might use the keys <code class="key">'A'</code>, <code class="key">'S'</code>, <code class="key">'D'</code>, and <code class="key">'W'</code> for <code class="key">
- 'left'</code>, <code class="key">'down'</code>, <code class="key">'right'</code>, and <code class="key">'up'</code> respectively. Content authors <span class="should">should</span>
- provide a means for the user to assign such controller keys to a custom setting appropriate to their keyboard configurations. Implementations <span class="may">may</span> provide a means
+ 'left'</code>, <code class="key">'down'</code>, <code class="key">'right'</code>, and <code class="key">'up'</code> respectively. Content authors SHOULD
+ provide a means for the user to assign such controller keys to a custom setting appropriate to their keyboard configurations. Implementations MAY provide a means
for the user to more comprehensively map the keyboard to their customized keyboard layout, but this is beyond the scope of this specification.</p>
<p class="note"><strong>Note:</strong> Don't confuse key values with <em>scan codes</em>, which are the low-level hexadecimal signals produced for each key
@@ -5815,18 +5814,18 @@
<p>Virtual keyboards are software-based sets of keys, in a variety of different arrangements, commonly found on touch-screen devices; they are often modal, with the
ability to switch between different dynamic sets of keys, such as alphabetic, numeric, or symbolic keys. Because of the lack of physical constraints, these keyboards
- <span class="may">may</span> present the widest range of characters, including emoticons and other symbols, and <span class="may">may</span> have keys not represented by Unicode [<a href="#references-Unicode">Unicode</a>]
- or by the <a href="#key-values">key values set</a> defined in this specification. Wherever possible, however, virtual keyboards <span class="should">should</span> produce the normal range
+ MAY present the widest range of characters, including emoticons and other symbols, and MAY have keys not represented by Unicode [<a href="#references-Unicode">Unicode</a>]
+ or by the <a href="#key-values">key values set</a> defined in this specification. Wherever possible, however, virtual keyboards SHOULD produce the normal range
of keyboard events and values, for ease of authoring and compatibility with existing content.</p>
<p>Chording keyboards, also know as chorded keysets or chord keyboards, are key input devices which produce values by pressing several keys in combination or sequence,
- normally to simulate a full range of characters or commands on a reduced set of keys, often for single-handed use. A chording keyboard <span class="may">may</span> have additional mode
+ normally to simulate a full range of characters or commands on a reduced set of keys, often for single-handed use. A chording keyboard MAY have additional mode
keys to switch between key values, and the number and type of keys pressed to produce a key value will vary, but the final key values produced by such keyboards
- <span class="should">should</span> match the range of key values described in this specification.</p>
+ SHOULD match the range of key values described in this specification.</p>
<p>For these and other alternative modal keyboards, the key values <a href="#key-Alphanumeric"><code class="key">'Alphanumeric'</code></a>, <a href="#key-CapsLock">
<code class="key">'CapsLock'</code></a>, <a href="#key-NumLock"><code class="key">'NumLock'</code></a>, and <a href="#key-SymbolLock"><code class="key">
- 'SymbolLock'</code></a> are <span class="recommended">recommended</span> for the keys which switch between different modes.</p>
+ 'SymbolLock'</code></a> are RECOMMENDED for the keys which switch between different modes.</p>
</section>
@@ -5838,7 +5837,7 @@
<h2>Key Values</h2>
<p>A key value is a <code>DOMString</code> that can be used to indicate any given key on a keyboard, regardless of position or state, by the value it produces. These
- key values <span class="may">may</span> be used as return values for keyboard events generated by the implementation, or as input values by the content author to specify desired input (such
+ key values MAY be used as return values for keyboard events generated by the implementation, or as input values by the content author to specify desired input (such
as for keyboard shortcuts). This specification defines a set of common key values (called the <a href="#key-values">Key Values Set</a>), and rules for production
of new key values.</p>
@@ -5851,7 +5850,7 @@
<p>Key values can also be used by content authors in string comparisons, as values for markup attributes (such as the HTML <code>accesskey</code>) in conforming <a
class="def" href="#glossary-host-language">host languages</a>, or for other related purposes. A conforming <a class="def" href="#glossary-host-language">host language</a>
- <span class="should">should</span> allow content authors to use either of the two equivalent string values for a key value: the <a class="def" href="#glossary-character-value">character value</a>,
+ SHOULD allow content authors to use either of the two equivalent string values for a key value: the <a class="def" href="#glossary-character-value">character value</a>,
or the <a class="def" href="#glossary-key-value">key value</a>.</p>
<p class="note"><strong>Note:</strong> While implementations will use the most relevant value for a key independently of the platform or keyboard layout mappings,
@@ -5877,10 +5876,10 @@
and <a href="#events-DOM_KEY_LOCATION_RIGHT"><code class="constant-name">DOM_KEY_LOCATION_RIGHT</code></a>) or <code class="key">'8'</code> key value (normally
distinguished by the <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a> values <a href="#events-DOM_KEY_LOCATION_STANDARD"><code class="constant-name">
DOM_KEY_LOCATION_STANDARD</code></a> and <a href="#events-DOM_KEY_LOCATION_NUMPAD"><code class="constant-name">DOM_KEY_LOCATION_NUMPAD</code></a>), and user-configured
- custom keyboard layouts <span class="may">may</span> duplicate any key value in multiple key-state scenarios (note that <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>
+ custom keyboard layouts MAY duplicate any key value in multiple key-state scenarios (note that <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>
is intended for standard keyboard layouts, and cannot always indicate a meaningful distinction).</p>
- <p>Similarly, a given key event state <span class="may">may</span> have different key values. For most keys which represent characters, such as the letter <code class="glyph">'m'</code> or the question
+ <p>Similarly, a given key event state MAY have different key values. For most keys which represent characters, such as the letter <code class="glyph">'m'</code> or the question
mark (<code class="glyph">'?'</code>), the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> and <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a>
attributes will be the same. However, for <em>printing control characters</em>, such as the backspace/back key, the <em>character value</em> is distinct from the
<em>key value</em>, with different values for the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> and <a href="#events-KeyboardEvent-char"><code>
@@ -5959,7 +5958,7 @@
a certain code block (range of code points), using a regular expression like <code>\p{InCyrillic}</code>.</p>
</div>
- <p>To facilitate this, implementations <span class="should">should</span> support Unicode range detection using regular expressions, in a manner such as the Perl Compatible Regular Expressions
+ <p>To facilitate this, implementations SHOULD support Unicode range detection using regular expressions, in a manner such as the Perl Compatible Regular Expressions
(PCRE) [<a href="#references-pcre">PCRE</a>].</p>
</section>
@@ -6040,9 +6039,9 @@
<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 <span class="may">may</span> reverse the sequence, with the
+ always follow the handwriting sequence, with the combining character trailing the corresponding letter, typical deadkey input MAY reverse the sequence, with the
combining character before the corresponding letter; for example, the word <em>naïve</em>, using the combining diacritic <em>¨</em>, would be represented sequentially
- in Unicode as <em>nai¨ve</em>, but <span class="may">may</span> be typed <em>na¨ive</em>. The sequence of keystrokes <code class="char">'\u0302'</code> (Combining Circumflex Accent key) and <code class="char">'\u0065'</code>
+ in Unicode as <em>nai¨ve</em>, but MAY be typed <em>na¨ive</em>. The sequence of keystrokes <code class="char">'\u0302'</code> (Combining Circumflex Accent key) and <code class="char">'\u0065'</code>
(key marked with the Latin Small Letter E) will likely produce (on a PC/AT french keyboard using a french mapping and without any modifier activated) the Unicode
character <code class="glyph">'ê'</code> (Latin Small Letter E With Circumflex), as preferred by the Unicode Normalization Form <em>NFC</em>:</p>
@@ -6093,7 +6092,7 @@
<code>compositionend</code></a> event in most <a class="def" href="#glossary-ime">IME</a> systems). Keyboard events cannot be used to determine the current
state of the input method editor, which can be obtained through the <a href="#events-CompositionEvent-data"><code>data</code></a> attribute of the <a href="#events-compositionevents">
CompositionEvent</a> interface. Additionally, <a class="def" href="#glossary-ime">IME</a> systems and devices vary in their functionality, and in which keys
- are used for activating that functionality, such that the <code class="key">'Convert'</code> and <code class="key">'Accept'</code> keys <span class="may">may</span> be represented
+ are used for activating that functionality, such that the <code class="key">'Convert'</code> and <code class="key">'Accept'</code> keys MAY be represented
by other available keys. Keyboard events correspond to the events generated by the input device after the keyboard layout mapping.</p>
<p class="note"><strong>Note:</strong> In some implementations or system configurations, some key events, or their values, might be suppressed
@@ -6101,7 +6100,7 @@
<p>The following example describes a possible sequence of keys to generate the Unicode character <code class="glyph">'市'</code> (Kanji character, part of CJK Unified Ideographs) using Japanese
input methods. This example assumes that the input method editor is activated and in the Japanese-Romaji input mode. The keys <code class="key">'Convert'</code>
- and <code class="key">'Accept'</code> <span class="may">may</span> be replaced by others depending on the input device in use and the configuration of the IME, e.g., it can be respectively
+ and <code class="key">'Accept'</code> MAY be replaced by others depending on the input device in use and the configuration of the IME, e.g., it can be respectively
<code class="char">'\u0020'</code> (Space key) and <code class="key">'Enter'</code>.</p>
<p class="note"><strong>Note:</strong> <code class="glyph">'詩'</code> (<q>poem</q>) and <code class="glyph">'市'</code> (<q>city</q>) are homophones, both
@@ -6173,7 +6172,7 @@
<code>KanjiMode</code>, <code>Katakana</code>, and <code>RomanCharacters</code>. When one of these keys is pressed, and no <a class="def" href="#glossary-ime">IME</a>
is currently active, the appropriate <a class="def" href="#glossary-ime">IME</a> is expected to be activated in the mode indicated by the key (if available); if
an <a class="def" href="#glossary-ime">IME</a> is already active when the key is pressed, the active <a class="def" href="#glossary-ime">IME</a> might change to
- the indicated mode, or a different <a class="def" href="#glossary-ime">IME</a> might be launched, or the might <span class="may">may</span> be ignored, on a device- and application-specific
+ the indicated mode, or a different <a class="def" href="#glossary-ime">IME</a> might be launched, or the might MAY be ignored, on a device- and application-specific
basis.</p>
<p>This specification also defines other keys which are intended for operation specifically with <a class="def" href="#glossary-ime">input method editors</a>: <code>
@@ -6190,7 +6189,7 @@
<h3>Default actions and cancelable keyboard events</h3>
<p>Canceling the <a class="def" href="#glossary-default-action">default action</a> of a <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event
- <span class="mustnot">must not</span> affect its respective <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event, but it <span class="must">must</span> prevent the respective <a class="eventtype"
+ MUST NOT affect its respective <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event, but it MUST prevent the respective <a class="eventtype"
href="#event-type-keypress"><code>keypress</code></a> event (if supported) from being generated. The following example describes a possible sequence of keys
to generate the Unicode character Q (Latin Capital Letter Q) on a PC/AT US keyboard using a US mapping:</p>
@@ -6212,7 +6211,7 @@
</ol>
</div>
- <p>If the key is a modifier key, the keystroke <span class="must">must</span> still be taken into account for the modifiers states. The following example describes a possible sequence of keys
+ <p>If the key is a modifier key, the keystroke MUST still be taken into account for the modifiers states. The following example describes a possible sequence of keys
to generate the Unicode character Q (Latin Capital Letter Q) on a PC/AT US keyboard using a US mapping:</p>
<div class="example">
@@ -6233,7 +6232,7 @@
</div>
<p>If the key is part of a sequence of several keystrokes, whether it is a <a class="def" href="#glossary-dead-key">dead key</a> or it is contributing to an Input
- Method Editor sequence, the keystroke <span class="must">must</span> be ignored (not taken into account) only if the <a class="def" href="#glossary-default-action">default action</a> is
+ Method Editor sequence, the keystroke MUST be ignored (not taken into account) only if the <a class="def" href="#glossary-default-action">default action</a> is
canceled on the <a class="eventtype" href="#event-type-keydown"><code>keydown</code></a> event. Canceling a <a class="def" href="#glossary-dead-key">dead key</a>
on a <a class="eventtype" href="#event-type-keyup"><code>keyup</code></a> event has no effect on <a class="eventtype" href="#event-type-keypress"><code>keypress</code></a>
events (if supported). The following example uses the keystrokes <code class="char">'\u0302'</code> (Combining Circumflex Accent key) and the key marked <code class="key">
@@ -6260,9 +6259,9 @@
<p><strong>This section is normative.</strong></p>
- <p>The list of key values contained in this specification is not exhaustive, and input devices <span class="may">may</span> have to define their own key values. Consider the current function
+ <p>The list of key values contained in this specification is not exhaustive, and input devices MAY have to define their own key values. Consider the current function
of the key (i.e., with modifiers), taking into consideration the keyboard layout mapping in use, to determine if the key is represented by the set of defined key
- values, if a corresponding Unicode character exists from which a key value <span class="may">may</span> be derived, or if a new key value <span class="must">must</span> be defined. The following algorithm determines
+ values, if a corresponding Unicode character exists from which a key value MAY be derived, or if a new key value MUST be defined. The following algorithm determines
the <em>key value</em> and <em>character value</em> to use:</p>
<ol class="algo" id="key-algorithm">
@@ -6270,15 +6269,15 @@
<ol class="algo">
<li>If there exists an appropriate character in the <a href="#keys-keyvalues">key values set</a>, then:
<ol class="algo">
- <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute <span class="must">must</span> be a string consisting of the <em>key value</em> of that character; and</li>
- <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute <span class="must">must</span> be a string consisting of the <em>char value</em> of that character.</li>
+ <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute MUST be a string consisting of the <em>key value</em> of that character; and</li>
+ <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute MUST be a string consisting of the <em>char value</em> of that character.</li>
</ol>
</li>
<li>If there is no appropriate key value in the <a href="#keys-keyvalues">key values set</a>, and there exists an appropriate <a class="def" href="#glossary-unicode-code-point">
Unicode code point</a>, then:
<ol class="algo">
- <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute <span class="must">must</span> be a string consisting of the <em>char value</em> of that character; and</li>
- <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute <span class="must">must</span> be a string consisting of the <em>char value</em> of that character.</li>
+ <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute MUST be a string consisting of the <em>char value</em> of that character; and</li>
+ <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute MUST be a string consisting of the <em>char value</em> of that character.</li>
</ol>
</li>
</ol>
@@ -6287,15 +6286,15 @@
<ol class="algo">
<li>If there exists an appropriate key value in the <a href="#keys-keyvalues">key values set</a>, then:
<ol class="algo">
- <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute <span class="must">must</span> be a string consisting of the <em>key value</em> of that character; and</li>
- <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute <span class="must">must</span> be the <a class="def" href="#glossary-empty-string">empty string</a>.</li>
+ <li>the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute MUST be a string consisting of the <em>key value</em> of that character; and</li>
+ <li>the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> attribute MUST be the <a class="def" href="#glossary-empty-string">empty string</a>.</li>
</ol>
</li>
- <li>If there is no appropriate key value in the <a href="#keys-keyvalues">key values set</a>, then a key value <span class="must">must</span> be devised. The key value <span class="should">should</span> be as human friendly
- as possible and <span class="must">must</span> not contain whitespace characters. The value <span class="must">must</span> be composed only of characters in the ranges
+ <li>If there is no appropriate key value in the <a href="#keys-keyvalues">key values set</a>, then a key value MUST be devised. The key value SHOULD be as human friendly
+ as possible and MUST not contain whitespace characters. The value MUST be composed only of characters in the ranges
(<abbr title="0-9"><code class="char">'\u0030'</code>..<code class="char">'\u0039'</code></abbr>),
(<abbr title="A-Z"><code class="char">'\u0041'</code>..<code class="char">'\u005A'</code></abbr>), or
- (<abbr title="a-z"><code class="char">'\u0061'</code>..<code class="char">'\u007A'</code></abbr>), and <span class="must">must</span> begin with a character in the range
+ (<abbr title="a-z"><code class="char">'\u0061'</code>..<code class="char">'\u007A'</code></abbr>), and MUST begin with a character in the range
(<abbr title="A-Z"><code class="char">'\u0041'</code>..<code class="char">'\u005A'</code></abbr>).
</li>
</ol>
@@ -6326,21 +6325,21 @@
<section id="key-values">
<h3>Key Values Set</h3>
- <p>This section defines a list of key values which implementations <span class="must">must</span> support, at a minimum, in addition to support for the full range of Unicode [<a href="#references-Unicode">Unicode</a>]
- codepoints. Implementations <span class="may">may</span> support additional key values, in a manner conforming to the <a href="#keys-Guide">guidelines for selecting and defining key values</a>.
+ <p>This section defines a list of key values which implementations MUST support, at a minimum, in addition to support for the full range of Unicode [<a href="#references-Unicode">Unicode</a>]
+ codepoints. Implementations MAY support additional key values, in a manner conforming to the <a href="#keys-Guide">guidelines for selecting and defining key values</a>.
Each key value defines one or both of the following: a <a class="def" href="#glossary-character-value">character value</a> and a <a class="def" href="#glossary-key-value">
- key value</a>. The <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute of an event <span class="must">must</span> always contain one of these control key
+ key value</a>. The <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute of an event MUST always contain one of these control key
or character values (even if the value is <a href="#key-Unidentified"><code class="key">'Unidentified'</code></a>), and the <a href="#events-KeyboardEvent-char">
- <code>KeyboardEvent.char</code></a> attribute <span class="must">must</span> have a value if the key represents a printable character. If the key represents one of the set of printable
+ <code>KeyboardEvent.char</code></a> attribute MUST have a value if the key represents a printable character. If the key represents one of the set of printable
control characters which has a Unicode character entry, such as the tab key, the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> attribute
- <span class="must">must</span> have the key value (e.g., <a href="#key-Tab"><code class="key">'Tab'</code></a>), while the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a>
- attribute <span class="must">must</span> have the Unicode character value equivalent (e.g., <a href="#key-U-0009"><code class="char">'\u0009'</code></a>). This affords content authors
+ MUST have the key value (e.g., <a href="#key-Tab"><code class="key">'Tab'</code></a>), while the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a>
+ attribute MUST have the Unicode character value equivalent (e.g., <a href="#key-U-0009"><code class="char">'\u0009'</code></a>). This affords content authors
the opportunity to deal with the key as a control key or as direct input into the text stream.</p>
- <p>Implementations that are unable to identify a key <span class="must">must</span> use the key value <a href="#key-Unidentified"><code class="key">'Unidentified'</code></a>.</p>
-
- <p class="warning"><strong>Warning!</strong> Conforming implementations <span class="must">must</span> only use this key value when there is no way for the implementation to detect the key value;
- exposing only this value <span class="mustnot">must not</span> indicate a conforming implementation.</p>
+ <p>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="warning"><strong>Warning!</strong> Conforming implementations MUST only use this key value when there is no way for the implementation to detect the key value;
+ exposing only this value MUST NOT indicate a conforming implementation.</p>
<p>The <a class="def" href="#glossary-key-value">key values</a> defined in this specification are based in part on the sets of keycodes from the <code>java.awt.event.KeyEvent</code>
interface of the Java Platform, Standard Edition 6 API Specification [<cite><a class="informative" href="#references-KeyEvent">KeyEvent for Java</a></cite>], and
@@ -6356,7 +6355,7 @@
are not distinguished from other numerical key values in this set; a content author could use the <a href="#events-KeyboardEvent-location"><code>KeyboardEvent.location</code></a>
attribute to discover if a key originated from the numeric keypad.</p>
- <p>Future versions of this specification <span class="may">may</span> include key values not included here, which have become common since the publication of this specification.</p>
+ <p>Future versions of this specification MAY include key values not included here, which have become common since the publication of this specification.</p>
<p>In the following list, character values for printing control characters are described as a character escape, for convenience, using the JavaScript notation for
escapes.</p>
@@ -6380,9 +6379,9 @@
<section id="key-values-list">
<h4>Key Values List</h4>
<p>The following list contains the normative list of case-sensitive key values, their character values (where applicable), an informative description of typical usage,
- and an informative categorization. A conforming implementation of the <a href="#events-KeyboardEvent">KeyboardEvent</a> interface <span class="must">must</span> support at least this set
+ and an informative categorization. A conforming implementation of the <a href="#events-KeyboardEvent">KeyboardEvent</a> interface MUST support at least this set
of values for use in the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> and <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a>
- attributes, though not all values <span class="may">may</span> be available on all platforms or devices.</p>
+ attributes, though not all values MAY be available on all platforms or devices.</p>
<table class="data-table">
<tr>
@@ -7775,12 +7774,12 @@
<code>initMutationEvent</code>.</p>
</div>
- <p>Due in part to the length of time in the development of this standard, some implementations <span class="may">may</span> have taken a dependency on a set of initializer methods that were
+ <p>Due in part to the length of time in the development of this standard, some implementations MAY have taken a dependency on a set of initializer methods that were
formerly defined in this specification. For completeness, these legacy event intializers are described in this Appendix.</p>
<p>The initialization of new derived event objects becomes easier with the introduction of event constructors in
[<a href="#references-UIEvents">UI Events</a>]. Event constructors
- are a new mechanism for initializing the event object's attributes that allows authors to pick-and-choose which of all the possible event attributes <span class="should">should</span> be initialized to
+ are a new mechanism for initializing the event object's attributes that allows authors to pick-and-choose which of all the possible event attributes SHOULD be initialized to
a value. For the omitted values, a suitable default is applied.</p>
<p>This specification does not require a conforming implementation to support event constructors. Likewise it does not require a conforming implementation to support
@@ -7912,7 +7911,7 @@
<dd><p>Refer to the <a href="#events-event-type-initUIEvent"><code>UIEvent.initUIEvent()</code></a> method for a description of this parameter.</p></dd>
<dt>EventTarget? relatedTargetArg</dt>
- <dd><p>Specifies <a href="#events-FocusEvent-relatedTarget"><code>FocusEvent.relatedTarget</code></a>. This value <span class="may">may</span> be <code>null</code>.</p></dd>
+ <dd><p>Specifies <a href="#events-FocusEvent-relatedTarget"><code>FocusEvent.relatedTarget</code></a>. This value MAY be <code>null</code>.</p></dd>
</dl>
</dd>
</dl>
@@ -8183,8 +8182,8 @@
Additionally, these attributes are not suitable for international usage, or accessibility concerns.</p>
<p>Therefore, this specification does not normatively define the <code class="attribute-name">charCode</code>, <code class="attribute-name">keyCode</code>, or <code
- class="attribute-name">which</code> attributes on the <a href="#events-KeyboardEvent">KeyboardEvent</a> interface, though they <span class="may">may</span> be present in <a class="def" href="#glossary-user-agent">
- user agents</a> for compatibility with legacy content. Authors <span class="should">should</span> use the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> and <a href="#events-KeyboardEvent-key">
+ class="attribute-name">which</code> attributes on the <a href="#events-KeyboardEvent">KeyboardEvent</a> interface, though they MAY be present in <a class="def" href="#glossary-user-agent">
+ user agents</a> for compatibility with legacy content. Authors SHOULD use the <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a> and <a href="#events-KeyboardEvent-key">
<code>KeyboardEvent.key</code></a> attributes instead of the <code class="attribute-name">charCode</code> and <code class="attribute-name">keyCode</code>
attributes, respectively.</p>
@@ -8225,8 +8224,8 @@
<p><code class="attribute-name">keyCode</code> holds a system- and implementation-dependent numerical code signifying the unmodified identifier associated with the
key pressed. Unlike the <a href="#events-KeyboardEvent-key"><code>KeyboardEvent.key</code></a> or <a href="#events-KeyboardEvent-char"><code>KeyboardEvent.char</code></a>
attributes, the set of possible values are not normatively defined in this specification; typically, these value of the <code class="attribute-name">keyCode</code>
- <span class="should">should</span> represent the decimal codepoint in ASCII [<a href="#ref-rfc20">RFC20</a>][<a href="#ref-US-ASCII">US-ASCII</a>] or Windows 1252 [<a href="#ref-WIN1252">WIN1252</a>],
- but <span class="may">may</span> be drawn from a different appropriate character set. Implementations that are unable to identify a key use the key value <code class="key">'0'</code>.</p>
+ SHOULD represent the decimal codepoint in ASCII [<a href="#ref-rfc20">RFC20</a>][<a href="#ref-US-ASCII">US-ASCII</a>] or Windows 1252 [<a href="#ref-WIN1252">WIN1252</a>],
+ but MAY be drawn from a different appropriate character set. Implementations that are unable to identify a key use the key value <code class="key">'0'</code>.</p>
<p>See <a href="#legacy-key-models">Legacy key models</a> for more details on how to determine the values for <code class="attribute-name">keyCode</code>.</p>
</dd>
@@ -8246,7 +8245,7 @@
<h2>Legacy key models</h2>
<p><em>This section is informative</em></p>
- <p>Implementations differ on which values are exposed on these attributes for different event types. An implementation <span class="may">may</span> choose to expose both virtual key codes
+ <p>Implementations differ on which values are exposed on these attributes for different event types. An implementation MAY choose to expose both virtual key codes
and character codes in the <code class="attribute-name">keyCode</code> property (<em>conflated model</em>), or report separate <code class="attribute-name">keyCode</code>
and <code class="attribute-name">charCode</code> properties (<em>split model</em>).</p>
@@ -8375,7 +8374,7 @@
<h3>Optionally fixed virtual key codes</h3>
<p><em>This section is informative</em></p>
- <p>The following punctuation characters <span class="may">may</span> change virtual codes between keyboard layouts, but reporting these values will likely be more compatible with legacy content
+ <p>The following punctuation characters MAY change virtual codes between keyboard layouts, but reporting these values will likely be more compatible with legacy content
expecting US-English keyboard layout:</p>
<table class="data-table">
@@ -8490,7 +8489,7 @@
<section id="extending_events-Custom_Events">
<h2>Custom Events</h2>
- <p>A script author <span class="may">may</span> wish to define an application in terms of functional components, with event types that are meaningful to the application architecture. The
+ <p>A script author MAY wish to define an application in terms of functional components, with event types that are meaningful to the application architecture. The
content author can use the <a href="#events-CustomEvent"><code>CustomEvent</code></a> interface to create their own events appropriate to the level of abstraction
they are using.</p>
@@ -8513,7 +8512,7 @@
<section id="extending_events-Impl_Extensions">
<h2>Implementation-Specific Extensions</h2>
<p>While a new event is being designed and prototyped, or when an event is intended for implementation-specific functionality, it is desirable to distinguish it from
- standardized events. Implementors <span class="should">should</span> prefix event types specific to their implementations with a short string to distinguish it from the same event in other
+ standardized events. Implementors SHOULD prefix event types specific to their implementations with a short string to distinguish it from the same event in other
implementations and from standardized events. This is similar to the <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords" title="CSS 2.1: Syntax and basic data types">
vendor-specific keyword prefixes</a> in CSS, though without the dashes (<code>"-"</code>) used in CSS, since that can cause problems when used as an attribute
name in Javascript.</p>
@@ -8575,7 +8574,7 @@
<p>This appendix discusses security considerations for DOM Level 3 Events implementations. The discussion is limited to security issues that arise directly
from implementation of the event model, APIs and events defined in this specification. Implementations typically support other features like scripting languages,
- other APIs and additional events not defined in this document; these features constitute an unknown factor and are out of scope of this document. Implementers <span class="should">should</span>
+ other APIs and additional events not defined in this document; these features constitute an unknown factor and are out of scope of this document. Implementers SHOULD
consult the specifications of such features for their respective security considerations.</p>
<p>Many of the event types defined in this specification are dispatched in response to user actions. This allows malicious event listeners to gain access to information
@@ -8591,7 +8590,7 @@
system to prepare further attacks.</p>
<p>An implementation of DOM Level 3 Events alone is generally insufficient to perform attacks of this kind and the security considerations of the facilities that possibly
- support such attacks apply. For conformance with this specification, DOM implementations <span class="may">may</span> take reasonable steps to ensure that <a class="def" href="#glossary-DOM-application">
+ support such attacks apply. For conformance with this specification, DOM implementations MAY take reasonable steps to ensure that <a class="def" href="#glossary-DOM-application">
DOM applications</a> do not get access to confidential or sensitive information, for example, they might choose to dispatch no <a class="eventtype"><code>load</code></a>
events to nodes that attempt to embed resources on the local network.</p>
</section>