Event interface represents an event which takes place in the DOM.
An event can be triggered by the user action e.g. clicking the mouse button or tapping keyboard, or generated by APIs to represent the progress of an asynchronous task. It can also be triggered programmatically, such as by calling the
HTMLElement.click() method of an element, or by defining the event, then sending it to a specified target using
There are many types of events, some of which use other interfaces based on the main
Event itself contains the properties and methods which are common to all events.
Many DOM elements can be set up to accept (or "listen" for) these events, and execute code in response to process (or "handle") them. Event-handlers are usually connected (or "attached") to various HTML elements (such as
<span>, etc.) using
EventTarget.addEventListener(), and this generally replaces using the old HTML event handler attributes. Further, when properly added, such handlers can also be disconnected if needed using
Note: One element can have several such handlers, even for the exact same event—particularly if separate, independent code modules attach them, each for its own independent purposes. (For example, a webpage with an advertising-module and statistics-module both monitoring video-watching.)
When there are many nested elements, each with its own handler(s), event processing can become very complicated—especially where a parent element receives the very same event as its child elements because "spatially" they overlap so the event technically occurs in both, and the processing order of such events depends on the Event bubbling and capture settings of each handler triggered.
Below is a list of interfaces which are based on the main
Event interface, with links to their respective documentation in the MDN API reference.
Note that all event interfaces have names which end in "Event".
Eventobject, returning it to the caller.
A boolean value indicating whether or not the event bubbles up through the DOM.
A boolean value indicating whether the event is cancelable.
A boolean indicating whether or not the event can bubble across the boundary between the shadow DOM and the regular DOM.
A reference to the currently registered target for the event. This is the object to which the event is currently slated to be sent. It's possible this has been changed along the way through retargeting.
Indicates whether or not the call to
event.preventDefault()canceled the event.
Indicates which phase of the event flow is being processed. It is one of the following numbers:
Indicates whether or not the event was initiated by the browser (after a user click, for instance) or by a script (using an event creation method, for example).
A reference to the object to which the event was originally dispatched.
The time at which the event was created (in milliseconds). By specification, this value is time since epoch—but in reality, browsers' definitions vary. In addition, work is underway to change this to be a
The case-insensitive name indentifying the type of the event.
A historical alias to
Event.stopPropagation()that should be used instead. Setting its value to
truebefore returning from an event handler prevents propagation of the event.
The explicit original target of the event.
The original target of the event, before any retargetings.
A boolean value indicating whether the given event will bubble across through the shadow root into the standard DOM. Use
Returns the event's path (an array of objects on which listeners will be invoked). This does not include nodes in shadow trees if the shadow root was created with its
Cancels the event (if it is cancelable).
For this particular event, prevent all other listeners from being called. This includes listeners attached to the same element as well as those attached to elements that will be traversed later (during the capture phase, for instance).
Stops the propagation of events further along in the DOM.
|DOM Standard (DOM)|
BCD tables only load in the browser