Document Object Model (DOM) Level 3 Events Specification

1.1 Introduction

DOM Events is designed with two main goals. The first goal is the design of an event system which allows registration of event listeners and describes event flow through a tree structure. Additionally, the specification will provide standard modules of events for user interface control and document mutation notifications, including defined contextual information for each of these event modules.

The second goal of DOM Events is to provide a common subset of the current event systems used in DOM Level 0 browsers. This is intended to foster interoperability of existing scripts and content. It is not expected that this goal will be met with full backwards compatibility. However, the specification attempts to achieve this when possible.

1.1.1 Conformance

This specification is to be understood in the context of the DOM Level 3 Core specification [DOM Level 3 Core] and the general considerations for DOM implementations apply. For example, handling of namespace URIs is discussed in XML Namespaces, and behavior in exceptional circumstances (such as when a null argument is passed when null was not expected) is discussed under DOMException. For additional information about conformance, please see the DOM Level 3 Core specification [DOM Level 3 Core].

An implementation is DOM Level 3 Events conformant if it supports the Core module defined in [DOM Level 2 Core], the Event dispatch and DOM event flow mechanism and the interfaces with their associated semantics defined in Basic interfaces. An implementation conforms to a DOM Level 3 Events module if it conforms to DOM Level 3 Events, the event types defined in the module, and the modules the module depends upon (if any).

An implementation conforms to an event type if it conforms to its associated semantics and DOM interfaces. This includes that event objects that are generated by the implementation are generated as outlined in the tabular definition of the event type.

An implementation which does not conform to an event module can still implement the DOM interfaces associated with it. The DOM application can then create an event object using the DocumentEvent.createEvent() method and dispatch an event type associated with this interface using the EventTarget.dispatchEvent() method.

A DOM application may use the hasFeature(feature, version) method of the DOMImplementation interface with parameter values "Events" and "3.0" (respectively) to determine whether or not DOM Level 3 Events is supported by the implementation, and the implementation must return true. Since DOM Level 3 Events is built on top of DOM Level 2 Events [DOM Level 2 Events], an implementation that returns true for "Events" and "3.0" shall also return true for the parameters "Events" and "2.0". The same holds for the feature strings defined for the individual event modules as applicable. Refer to DOM Features in [DOM Level 3 Core] for additional information.

1.2 Event dispatch and DOM event flow

This section defines the event dispatch mechanism of the event model defined in this specification. Applications may dispatch event objects using the EventTarget.dispatchEvent() method, and implementations must dispatch event objects as if through this method. The behavior of this method depends on the event flow associated with the underlying object. An event flow describes how event objects propagate 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.

Figure: graphical representation of an event dispatched in a DOM tree using the DOM event flow [SVG 1.0 version]

Event objects are always dispatched to a node called the event target. At the beginning of the dispatch, implementations must first determine the event object's propagation path. The propagation path is an ordered list of event targets through which the object will pass. The last item in the list is the event target; the preceding items in the list are referred to as the target's ancestors, and the immediately preceding item as the target's parent. Once determined, the propagation path cannot be changed. As an example, in the DOM event flow event listeners might change the position of the target node in the document while the event object is being dispatched; such changes do not affect the propagation path. What if an element is removed from the document altogether? Is there different behavior if the event target is removed versus one of its ancestors?

As the next step the event object accomplishes one or more event phases. This specification defines the following event phases. Event objects accomplish them in the specified order using the partial propagation paths as defined below. A phase is skipped if it is not supported, or if the event object's propagation has been stopped. For example, if the Event.bubbles attribute is set to false, the bubble phase is skipped, and if Event.stopPropagation() has been called prior to the dispatch, all phases will be skipped.

The capture phase: the event object propagates through the target's ancestors to the target's parent. This phase is also known as the capturing phase. Event listeners registered for this phase can handle the event before it reaches its target.
The target phase: the event object has reached the event's target. This phase is also known as the at-target phase. Event listeners registered for this phase can handle the event once it has reached its target.
The bubble phase: the event object propagates through the target's ancestors in reverse order, starting with the target's parent. This phase is also known as the bubbling phase. Event listeners registered for this phase can handle the event after it has reached its target.

Implementations let event objects accomplish an event phase by applying the following steps while there are pending event targets in the partial propagation path for this phase and the event object's propagation has not been stopped through Event.stopPropagation().

First, the implementation must determine the current target. This is the next pending event target in the partial propagation path, starting with the first. From the perspective of an event listener this is the event target the listener has been registered on.

Next, the implementation must determine the current target's candidate event listeners. This is the list of all event listeners that have been registered on the current target in their order of registration. Once determined, the candidate event listeners cannot be changed; adding or removing listeners does not affect the current target's candidate event listeners.

Finally, the implementation must process all candidate event listeners in order and trigger each listener if all the following conditions are met:

The event object's immediate propagation has not been stopped.
The listener has been registered for this event phase.
The listener has been registered for this event type.

An implementation shall trigger a listener by invoking the EventListener.handleEvent() method or an equivalent binding-specific mechanism.

As the final step of the event dispatch, for reasons of backwards compatibility, the implementation must reset the event object's internal-propagation and default-action-prevention states. This ensures that an event object may be properly dispatched multiple times while also allowing to prevent the event objects propagation or default actions prior to the event dispatch.

The model defined above applies regardless of the specific event flow associated with an event target. Each event flow defines how the propagation path is determined and which event phases are supported. The DOM event flow is an application of this model: the propagation path for a Node object is determined by its Node.parentNode chain, and all events accomplish the capture and target phases. Whether an event accomplishes the bubble phase is defined individually for each event type. An alternate application of this model can be found in [DOM Level 3 Load and Save].

The DOM event model is 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 will resume only after the event dispatch of the new event is completed.

1.3 Default actions and cancelable events

Event objects can have default actions associated with them. These are actions the implementation will perform in combination with the dispatch of the event object, usually after the dispatch has been completed, but in exceptional cases also immediately before the event is dispatched. An example is the [HTML 4.01] form element. When the user submits the form (e.g. by pressing on a submit button), the event submit is dispatched to the element and the default action for this event type is generally to send a request to a Web server with the parameters from the form.

Some event objects are cancelable, meaning the default action can be prevented from occuring, or, if the default action is carried out before the dispatch, its effect can be reversed. Whether an event object is cancelable is indicated by the Event.cancelable attribute. Event listeners can cancel default actions of cancelable event objects by invoking the Event.preventDefault() method, and determine whether an event has been canceled through the Event.defaultPrevented attribute while the object is being dispatched, or from the return value of the EventTarget.dispatchEvent() method for event objects dispatched by the DOM application itself.

This specification does not offer features to programatically query if an event object has any default action associated to it or associate new ones. It is expected that other specifications define what default actions, if any, are associated with certain event objects. Further, implementations may associate default actions with events as necessary and appropriate. As an example, an implementation may scroll a document view by a certain amount as default action of a mouse wheel event.

1.4 Activation requests and behavior

(This section is currently being rewritten.)

Event targets may have associated activation behavior that implementations perform in response to an activation request. As an example, the typical activiation behavior associated with hyperlinks is to follow the link. Activation requests are typically initiated by users through an input device.

In terms of this specification, the activation behavior of the event target is the default action of the event type DOMActivate. DOM applications should use this event type whenever they wish to make or react to an activation request.

Implementations dispatch the DOMActivate event as default action of a click event. This click event is either part of the activation request (e.g., a user requests activiation using a mouse), or synthesized by the implementation to accomodate legacy applications. Context information of such a click event is implementation dependent.

When implementations dispatch a synthesized click event, the expectation is that they do so as default action of another event type. For example, when a user activates a hyperlink using a keyboard, the click event would be dispatched as default action of the respective keyboard event.

Implementations are required to dispatch the synthesized click event as described above even if they do not dispatch such an event (e.g., when activation is requested by a voice command, since this specification does not address event types for voice input).

Note: The activation of an event target is device dependent but is also application dependent, e.g. a link in a document can be activated using a mouse click or a mouse double click.

1.5 Event types

Each event is associated with a type, called event type and available as the type attribute on the event object. The event type is composed of a local name and a namespace URI as used in [DOM Level 3 Core]. All events defined in this specification are in no namespace.

1.5.1 Complete list of event types

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 [XML 1.0] or [HTML 4.01] application, the specifications of those languages may restrict the semantics and scope (in particular the possible target nodes) associated with an event type. Refer to the specification defining the language used in order to find those restrictions or to find event types that are not defined in this document.

The following table provides a non-normative summary of the event types defined in this specification. All event types are in no namespace and this specification refers to them by their local name only. All events will accomplish the capture and target phases, but not all of them will accomplish the bubbling phase (see also Event dispatch and DOM event flow). Some events are not cancelable (see Default actions and cancelable events). Some events will only be dispatched to a specific set of possible targets in the DOM event flow, specified using node types. Contextual information related to the event type is accessible using DOM interfaces.

type	Bubbling phase	Cancelable	Target node types	DOM interface
DOMActivate	Yes	Yes	`Element`	`UIEvent`
DOMFocusIn	Yes	No	`Element`	`UIEvent`
DOMFocusOut	Yes	No	`Element`	`UIEvent`
focus	No	No	`Element`	`UIEvent`
blur	No	No	`Element`	`UIEvent`
textInput	Yes	Yes	`Element`	`TextEvent`
click	Yes	Yes	`Element`	`MouseEvent`
dblclick	Yes	Yes	`Element`	`MouseEvent`
mousedown	Yes	Yes	`Element`	`MouseEvent`
mouseup	Yes	Yes	`Element`	`MouseEvent`
mouseover	Yes	Yes	`Element`	`MouseEvent`
mousemove	Yes	Yes	`Element`	`MouseEvent`
mouseout	Yes	Yes	`Element`	`MouseEvent`
keydown	Yes	Yes	`Element`	`KeyboardEvent`
keyup	Yes	Yes	`Element`	`KeyboardEvent`
wheel	Yes	Yes	`Document`, `Element`	`WheelEvent`
mousewheel	Yes	Yes	`Document`, `Element`	`MouseWheelEvent`
DOMSubtreeModified	Yes	No	`Document`, `DocumentFragment`, `Element`, `Attr`	`MutationEvent`
DOMNodeInserted	Yes	No	`Element`, `Attr`, `Text`, `Comment`, `CDATASection`, `DocumentType`, `EntityReference`, `ProcessingInstruction`	`MutationEvent`
DOMNodeRemoved	Yes	No	`Element`, `Attr`, `Text`, `Comment`, `CDATASection`, `DocumentType`, `EntityReference`, `ProcessingInstruction`	`MutationEvent`
DOMNodeRemovedFromDocument	No	No	`Element`, `Attr`, `Text`, `Comment`, `CDATASection`, `DocumentType`, `EntityReference`, `ProcessingInstruction`	`MutationEvent`
DOMNodeInsertedIntoDocument	No	No	`Element`, `Attr`, `Text`, `Comment`, `CDATASection`, `DocumentType`, `EntityReference`, `ProcessingInstruction`	`MutationEvent`
DOMAttrModified	Yes	No	`Element`	`MutationEvent`
DOMCharacterDataModified	Yes	No	`Text`, `Comment`, `CDATASection`, `ProcessingInstruction`	`MutationEvent`
DOMElementNameChanged	Yes	No	`Element`	`MutationNameEvent`
DOMAttributeNameChanged	Yes	No	`Element`	`MutationNameEvent`
load	No	No	`Document`, `Element`	`Event`
unload	No	No	`Document`, `Element`	`Event`
abort	Yes	No	`Element`	`Event`
error	Yes	No	`Element`	`Event`
select	Yes	No	`Element`	`Event`
change	Yes	No	`Element`	`Event`
submit	Yes	Yes	`Element`	`Event`
reset	Yes	Yes	`Element`	`Event`
resize	Yes	No	`Document`, `Element`	`UIEvent`
scroll	Yes	No	`Document`, `Element`	`UIEvent`

As an example, the event load will trigger event listeners attached on Element nodes for that event and on the capture and target phases. This event cannot be cancelled. If an event listener for the load event is attached to a node other than Document or Element nodes, or if it is attached to the bubbling phase only, this event listener will not be triggered.

The event objects associated with the event types described above may contain context information. Refer to the description of the DOM interfaces for further information.

1.6 Basic interfaces

The interfaces described in this section are fundamental to DOM Level 3 Events and must always be supported by the implementation. Together they define the feature Events 3.0.

Interface Event (introduced in DOM Level 2)

The Event interface is used to provide contextual information about an event to the listener processing the event. An object which implements the Event interface is passed as the parameter to an EventListener. The object passed to the event listener may also implement derived interfaces that provide access to information directly relating to the type of event they represent.

To create an instance of the Event interface, use the DocumentEvent.createEvent("Event") method call.

IDL Definition

// Introduced in DOM Level 2:
interface Event {

  // PhaseType
  const unsigned short      CAPTURING_PHASE                = 1;
  const unsigned short      AT_TARGET                      = 2;
  const unsigned short      BUBBLING_PHASE                 = 3;

  readonly attribute DOMString       type;
  readonly attribute EventTarget     target;
  readonly attribute EventTarget     currentTarget;
  readonly attribute unsigned short  eventPhase;
  readonly attribute boolean         bubbles;
  readonly attribute boolean         cancelable;
  readonly attribute DOMTimeStamp    timeStamp;
  void               stopPropagation();
  void               preventDefault();
  void               initEvent(in DOMString eventTypeArg, 
                               in boolean canBubbleArg, 
                               in boolean cancelableArg);
  // Introduced in DOM Level 3:
  readonly attribute DOMString       namespaceURI;
  // Introduced in DOM Level 3:
  void               stopImmediatePropagation();
  // Introduced in DOM Level 3:
  readonly attribute boolean         defaultPrevented;
  // Introduced in DOM Level 3:
  void               initEventNS(in DOMString namespaceURIArg, 
                                 in DOMString eventTypeArg, 
                                 in boolean canBubbleArg, 
                                 in boolean cancelableArg);
};

Definition group PhaseType

An integer indicating which phase of the event flow is being processed as defined in Event dispatch and DOM event flow.

Defined Constants

AT_TARGET: The current event is in the target phase, i.e. it is being evaluated at the event target.
BUBBLING_PHASE: The current event phase is the bubbling phase.
CAPTURING_PHASE: The current event phase is the capture phase.

Attributes

bubbles of type boolean, readonly: Used to indicate whether or not an event is a bubbling event. If the event can bubble the value is true, otherwise the value is false.
cancelable of type boolean, readonly: Used to indicate whether or not an event can have its default action prevented (see also Default actions and cancelable events). If the default action can be prevented the value is true, otherwise the value is false.
currentTarget of type EventTarget, readonly: Used to indicate the EventTarget whose EventListeners are currently being processed. This is particularly useful during the capture and bubbling phases. When used with the Event dispatch and DOM event flow, this attribute contains the target node or a target ancestor.
defaultPrevented of type boolean, readonly, introduced in DOM Level 3: Used to indicate whether Event.preventDefault() has been called for this event.
eventPhase of type unsigned short, readonly: Used to indicate which phase of event flow is currently being accomplished.
namespaceURI of type DOMString, readonly, introduced in DOM Level 3: The namespace URI associated with this event at initialization time, or null if it is unspecified.
DOM Level 2 Events initialization methods, such as Event.initEvent(), set the value to null.
target of type EventTarget, readonly: Used to indicate the event target. This attribute contains the target node when used with the Event dispatch and DOM event flow.
timeStamp of type DOMTimeStamp, readonly: Used to specify the time at which the event was created in milliseconds relative to 1970-01-01T00:00:00Z. Due to the fact that some systems may not provide this information the value of timeStamp may be not available for all events. When not available, the value is 0.
type of type DOMString, readonly: The local name of the event type. The name must be an NCName as defined in [XML Namespaces 1.1] and is case-sensitive.

Methods

initEvent

Initializes attributes of an Event created through the DocumentEvent.createEvent method. This method may only be called before the Event has been dispatched via the EventTarget.dispatchEvent() method. If the method is called several times before invoking EventTarget.dispatchEvent, only the final invocation takes precedence. This method has no effect if called after the event has been dispatched. If called from a subclass of the Event interface only the values specified in this method are modified, all other attributes are left unchanged.
This method sets the Event.type attribute to eventTypeArg, and Event.namespaceURI to null. To initialize an event with a namespace URI, use the Event.initEventNS() method.

Parameters

eventTypeArg of type DOMString: Specifies Event.type, the local name of the event type.
canBubbleArg of type boolean: Specifies Event.bubbles. This parameter overrides the intrinsic bubbling behavior of the event.
cancelableArg of type boolean: Specifies Event.cancelable. This parameter overrides the intrinsic cancelable behavior of the event.

No Return Value

No Exceptions

initEventNS introduced in DOM Level 3

Initializes attributes of an Event object. This method has the same behavior as Event.initEvent().

Parameters

namespaceURIArg of type DOMString: Specifies Event.namespaceURI, the namespace URI associated with this event, or null if no namespace.
eventTypeArg of type DOMString: Refer to the Event.initEvent() method for a description of this parameter.
canBubbleArg of type boolean: Refer to the Event.initEvent() method for a description of this parameter.
cancelableArg of type boolean: Refer to the Event.initEvent() method for a description of this parameter.

No Return Value

No Exceptions

preventDefault

Signifies that the event is to be canceled, meaning any default action normally taken by the implementation as a result of the event will not occur (see also Default actions and cancelable events). Calling this method for a non-cancelable event has no effect.

Note: This method does not stop the event propagation; use Event.stopPropagation() or Event.stopImmediatePropagation() for that effect.

No Parameters

No Return Value

No Exceptions

stopImmediatePropagation introduced in DOM Level 3

Prevents other event listeners from being triggered and, unlike Event.stopPropagation() its effect is immediate . Once it has been called, further calls to this method have no additional effect.

Note: This method does not prevent the default action from being invoked; use Event.preventDefault() for that effect.

No Parameters

No Return Value

No Exceptions

stopPropagation

Prevents other event listeners from being triggered but its effect is deferred until all event listeners attached on the Event.currentTarget have been triggered . Once it has been called, further calls to this method have no additional effect.

Note: This method does not prevent the default action from being invoked; use Event.preventDefault() for that effect.

No Parameters

No Return Value

No Exceptions

Interface CustomEvent (introduced in DOM Level 3)

The CustomEvent interface is the recommended interface for application-specific event types. Unlike the Event interface, it allows applications to provide contextual information about the event type. Application-specific event types should have an associated namespace to avoid clashes with future general-purpose event types.

To create an instance of the CustomEvent interface, use the DocumentEvent.createEvent("CustomEvent") method call.

IDL Definition

// Introduced in DOM Level 3:
interface CustomEvent : Event {
  readonly attribute DOMObject       detail;
  void               initCustomEventNS(in DOMString namespaceURIArg, 
                                       in DOMString typeArg, 
                                       in boolean canBubbleArg, 
                                       in boolean cancelableArg, 
                                       in DOMObject detailArg);
};

Attributes

detail of type DOMObject, readonly: Specifies some detail information about the Event.

Methods

initCustomEventNS

Initializes attributes of a CustomEvent object. This method has the same behavior as Event.initEventNS().

Parameters

namespaceURIArg of type DOMString: Refer to the Event.initEventNS() method for a description of this parameter.
typeArg of type DOMString: Refer to the Event.initEventNS() method for a description of this parameter.
canBubbleArg of type boolean: Refer to the Event.initEventNS() method for a description of this parameter.
cancelableArg of type boolean: Refer to the Event.initEventNS() method for a description of this parameter.
detailArg of type DOMObject: Specifies CustomEvent.detail. This value may be null.

No Return Value

No Exceptions

Interface EventTarget (introduced in DOM Level 2)

The EventTarget interface is implemented by all the objects which could be event targets in an implementation which supports an event flow. The interface allows registration and removal of event listeners, and dispatch of events to an event target.

When used with the DOM event flow, this interface is implemented by all target nodes and target ancestors, i.e. all DOM Nodes 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 Node interface.

Invoking addEventListener or addEventListenerNS repeatedly on the same EventTarget with the same values for the parameters namespaceURI, type, listener, and useCapture has no effect. Doing so does not cause the EventListener to be called more than once and does not cause a change in the triggering order.

IDL Definition

// Introduced in DOM Level 2:
interface EventTarget {
  void               addEventListener(in DOMString type, 
                                      in EventListener listener, 
                                      in boolean useCapture);
  void               removeEventListener(in DOMString type, 
                                         in EventListener listener, 
                                         in boolean useCapture);
  // Modified in DOM Level 3:
  boolean            dispatchEvent(in Event evt)
                                        raises(EventException, 
                                               DOMException);
  // Introduced in DOM Level 3:
  void               addEventListenerNS(in DOMString namespaceURI, 
                                        in DOMString type, 
                                        in EventListener listener, 
                                        in boolean useCapture);
  // Introduced in DOM Level 3:
  void               removeEventListenerNS(in DOMString namespaceURI, 
                                           in DOMString type, 
                                           in EventListener listener, 
                                           in boolean useCapture);
};

Methods

addEventListener

Registers an event listener, depending on the useCapture parameter, on the capture phase of the DOM event flow or its target and bubbling phases. Invoking this method is equivalent to invoking addEventListenerNS with the same values for the parameters type, listener, and useCapture, and the value null for the parameter namespaceURI.

Parameters

type of type DOMString: Specifies the Event.type associated with the event for which the user is registering.
listener of type EventListener: The listener parameter takes an object implemented by the user which implements the EventListener interface and contains the method to be called when the event occurs.
useCapture of type boolean: If true, useCapture indicates that the user wishes to add the event listener for the capture phase only, i.e. this event listener will not be triggered during the target and bubbling phases. If false, the event listener will only be triggered during the target and bubbling phases.

No Return Value

No Exceptions

addEventListenerNS introduced in DOM Level 3

Registers an event listener, depending on the useCapture parameter, on the capture phase of the DOM event flow or its target and bubbling phases.

Parameters

namespaceURI of type DOMString: Specifies the Event.namespaceURI associated with the event for which the user is registering.
type of type DOMString: Refer to the EventTarget.addEventListener() method for a description of this parameter.
listener of type EventListener: Refer to the EventTarget.addEventListener() method for a description of this parameter.
useCapture of type boolean: Refer to the EventTarget.addEventListener() method for a description of this parameter.

No Return Value

No Exceptions

dispatchEvent modified in DOM Level 3

Dispatches an event into the implementation's event model. The event target of the event is the EventTarget object on which dispatchEvent is called.

Parameters

evt of type Event: The event to be dispatched.

Return Value

boolean

Indicates whether any of the listeners which handled the event called Event.preventDefault(). If Event.preventDefault() was called the returned value is false, else it is true.

Exceptions

EventException

UNSPECIFIED_EVENT_TYPE_ERR: Raised if the Event.type was not specified by initializing the event before dispatchEvent was called. Specification of the Event.type as null or an empty string will also trigger this exception.

DISPATCH_REQUEST_ERR: Raised if the Event object is already being dispatched.

DOMException

NOT_SUPPORTED_ERR: Raised if the Event object has not been created using DocumentEvent.createEvent().

INVALID_CHARACTER_ERR: Raised if Event.type is not an NCName as defined in [XML Namespaces 1.1].

removeEventListener

Removes an event listener. Calling removeEventListener with arguments which do not identify any currently registered EventListener on the EventTarget has no effect. The Event.namespaceURI for which the user registered the event listener is implied and is null.

Parameters

type of type DOMString: Specifies the Event.type for which the user registered the event listener.
listener of type EventListener: The EventListener to be removed.
useCapture of type boolean: Specifies whether the EventListener being removed was registered for the capture phase or not. If a listener was registered twice, once for the capture phase and once for the target and bubbling phases, each must be removed separately. Removal of an event listener registered for the capture phase does not affect the same event listener registered for the target and bubbling phases, and vice versa.

No Return Value

No Exceptions

removeEventListenerNS introduced in DOM Level 3

Removes an event listener. Calling removeEventListenerNS with arguments which do not identify any currently registered EventListener on the EventTarget has no effect.

Parameters

namespaceURI of type DOMString: Specifies the Event.namespaceURI associated with the event for which the user registered the event listener.
type of type DOMString: Refer to the EventTarget.removeEventListener() method for a description of this parameter.
listener of type EventListener: Refer to the EventTarget.removeEventListener() method for a description of this parameter.
useCapture of type boolean: Refer to the EventTarget.removeEventListener() method for a description of this parameter.

No Return Value

No Exceptions

Interface EventListener (introduced in DOM Level 2)

The EventListener interface is the primary way for handling events. Users implement the EventListener interface and register their event listener on an EventTarget. The users should also remove their EventListener from its EventTarget after they have completed using the listener.

Copying a Node, with methods such as Node.cloneNode or Range.cloneContents, must not copy the event listeners attached to it. Event listeners must be attached to the newly created Node afterwards if so desired.

Moving a Node, with methods Document.adoptNode, Node.appendChild, or Range.extractContents, shall not affect the event listeners attached to it.

IDL Definition

// Introduced in DOM Level 2:
interface EventListener {
  void               handleEvent(in Event evt);
};

Methods

handleEvent

This method is called whenever an event occurs of the event type for which the EventListener interface was registered.

Parameters

evt of type Event: The Event contains contextual information about the event.

No Return Value

No Exceptions

Exception EventException introduced in DOM Level 2

Event operations may throw an EventException as specified in their method descriptions.

IDL Definition

// Introduced in DOM Level 2:
exception EventException {
  unsigned short   code;
};
// EventExceptionCode
const unsigned short      UNSPECIFIED_EVENT_TYPE_ERR     = 0;
// Introduced in DOM Level 3:
const unsigned short      DISPATCH_REQUEST_ERR           = 1;

Definition group EventExceptionCode

An integer indicating the type of error generated.

Defined Constants

DISPATCH_REQUEST_ERR, introduced in DOM Level 3.: If the Event object is already dispatched in the tree.
UNSPECIFIED_EVENT_TYPE_ERR: If the Event.type was not specified by initializing the event before the method was called. Specification of the Event.type as null or an empty string will also trigger this exception.

1.6.1 Event creation

In most cases, the events dispatched by the DOM Events implementation are also created by the implementation. It is however possible to simulate events such as mouse events by creating the Event objects and dispatch them using the DOM Events implementation.

Creating Event objects that are known to the DOM Events implementation is done using DocumentEvent.createEvent(). The application must then initialize the object by calling the appropriate initialization method before invoking EventTarget.dispatchEvent(). The Event objects created must be known by the DOM Events implementation; otherwise an event exception is thrown.

Interface DocumentEvent (introduced in DOM Level 2)

The DocumentEvent interface provides a mechanism by which the user can create an Event object of a type supported by the implementation. If the feature "Events" is supported by the Document object, the DocumentEvent interface must be implemented on the same object. If the feature "+Events" is supported by the Document object, an object that supports the DocumentEvent interface must be returned by invoking the method Node.getFeature("+Events", "3.0") on the Document object.

IDL Definition

// Introduced in DOM Level 2:
interface DocumentEvent {
  Event              createEvent(in DOMString eventType)
                                        raises(DOMException);
  // Introduced in DOM Level 3:
  boolean            canDispatch(in DOMString namespaceURI, 
                                 in DOMString type);
};

Methods

canDispatch introduced in DOM Level 3

Tests if the implementation can generate events of a specified type.

Parameters

namespaceURI of type DOMString: Specifies the Event.namespaceURI of the event.
type of type DOMString: Specifies the Event.type of the event.

Return Value

boolean

true if the implementation can generate and dispatch this event type, false otherwise.

No Exceptions

createEvent

Creates an event object of the type specified.

Parameters

eventType of type DOMString

The eventType parameter specifies the name of the DOM Events interface to be supported by the created event object, e.g. "Event", "MouseEvent", "MutationEvent" and so on. If the Event is to be dispatched via the EventTarget.dispatchEvent() method the appropriate event initialization method must be called after creation in order to initialize the Event's values.

As an example, a user wishing to synthesize some kind of UIEvent would invoke DocumentEvent.createEvent("UIEvent"). The UIEvent.initUIEventNS() method could then be called on the newly created UIEvent object to set the specific type of user interface event to be dispatched, DOMActivate for example, and set its context information, e.g. UIEvent.detail in this example.

For backward compatibility reason, "UIEvents", "MouseEvents", "MutationEvents", and "HTMLEvents" feature names are valid values for the parameter eventType and represent respectively the interfaces "UIEvent", "MouseEvent", "MutationEvent", and "Event", and the characters 'a'..'z' are considered equivalent to the characters 'A'..'Z'.

Return Value

Event

The newly created event object.

Exceptions

DOMException

NOT_SUPPORTED_ERR: Raised if the implementation does not support the Event interface requested.

1.7 Event module definitions

The DOM Event Model allows a DOM implementation to support multiple modules of events. The model has been designed to allow addition of new event modules if required. The DOM will not attempt to define all possible events. For purposes of interoperability, the DOM defines a module of user interface

Document Object Model (DOM) Level 3 Events Specification

Version 1.0

Editor's Draft 28 June 2008

Abstract

Status of this document

Table of Contents

Expanded Table of Contents

W3C Copyright Notices and Licenses

W3C^® Document Copyright Notice and License

W3C^® Software Copyright Notice and License

W3C^® Short Software Notice

1. Document Object Model Events

Table of Contents

1.1 Introduction

1.1.1 Conformance

1.2 Event dispatch and DOM event flow

1.3 Default actions and cancelable events

1.4 Activation requests and behavior

1.5 Event types

1.5.1 Complete list of event types

1.6 Basic interfaces

1.6.1 Event creation

1.7 Event module definitions

Document Object Model (DOM) Level 3 Events Specification

Version 1.0

Editor's Draft 28 June 2008

Abstract

Status of this document

Table of Contents

Expanded Table of Contents

W3C Copyright Notices and Licenses

W3C® Document Copyright Notice and License

W3C® Software Copyright Notice and License

W3C® Short Software Notice

1. Document Object Model Events

Table of Contents

1.1 Introduction

1.1.1 Conformance

1.2 Event dispatch and DOM event flow

1.3 Default actions and cancelable events

1.4 Activation requests and behavior

1.5 Event types

1.5.1 Complete list of event types

1.6 Basic interfaces

1.6.1 Event creation

1.7 Event module definitions

W3C^® Document Copyright Notice and License

W3C^® Software Copyright Notice and License

W3C^® Short Software Notice