JavaScript has been made to handle client side application, and therefore has been designed with this objective in mind. One of the principal particularity of client side is the presence of a user, needing a highly interactive interface for browsing. Consequently, JavaScript event managment has quickly become one of its strength.
Browser events
Event ?
An event can be seen as a signal that something has happened. All nodes from the DOM generate such signals. Below are some useful DOM events:
Mouse events
click – when the mouse clicks on an element (touchscreen devices generate it on a tap).
contextmenu – when the mouse right-clicks on an element.
mouseover
Form element events
submit – when the visitor submits a <form>.
focus – when the visitor focuses on an element in the form, e.g. on an <input>.
Document events
DOMContentLoaded – when the HTML is loaded and processed, DOM is fully built.
CSS events
transitionend - when a CSS-animation finishes.
When such actions are performed (e.g. a button is clicked), we say that the click event is fired (or dispatched).
Event handler
To react on events (i.e. catch a dispatched event) we can assign a handler – a function that runs in case of an event.
There is several ways to assign handlers to HTML elements. We will only see the more flexible and less error prone here: addEventListener (doc. ). As an example, lets say we have an HTML input button
To handle the click event, we first need to retrieve our HTML element (here the input) in our JavaScript code, then attach to it our handler.
Multiple call to addEventListener for a same HTML element will add the handlers. This means that you can stack several functions for one event!
Event object
When an event is dispatched, it is often in a specific context which is important to us in order to understand what was going on. For example, in the case of a mouse click, where was the coordinate of the mouse?
Usually, when an event happens, the browser create what it is called an event object. This object contains the details of the event and is passed as an argument to the handler.
Handler with an object
It is also possible to attach to a handler not a function but an object! The only prerequisite is that the object implements a handleEvent() method. The method also receives the event object.
We can also use a class to better organize our code, especially if we want to delegate the events. In the following example we listen the up and down of the mouse with a single object, and the event is then dispatched.
Creating event
JavaScript allows you to create and manually manage your own events, which prevent you to fully reimplement an event handler. They are called synthetic events, as opposed to the events fired by the browser itself.
These events are DOM events: they rely on the DOM API of your browser, and are considered as event targets (cf. ). They are not supposed to be events produced by your objects.
To create a new event, the Event constructor can be call
Then, this new type of event can be attached to any DOM elements, and listened to.
And to fire the event
You can also add custom data to the event by using the CustomEvent constructor
However, you will mostly rely on already existing events, such as 'click', 'drag', etc. The full list is accessible .
Bubbling events
The principle of bubbling events is the following:
When an event happens on an element, it first runs the handlers on it, then on its parent, then all the way up on other ancestors.
When, lets say, a click is made on <p>, the onclick event is run firstly on <p>, then <div>, then <form>. The process is called “bubbling”, because events “bubble” from the inner element up through parents like literally an air bubble in the water.
Target of the event
An interesting point is that an event handler on a parent element can always get the details about where the event actually happened.
The event.target property stores the most deeply nested element that cause the event, while event.currentTarget stores the element where the handler is (this, in the example below the form).
event.target – the deepest element that originated the event.
event.currentTarget (=this) – the current element that handles the event (the one that has the handler on it)
event.eventPhase
Patterns
All these previous notion, and mostly bubbling, allow us to implement powerful event handling patterns.
Event Delegation pattern
The idea behind the event delegation pattern, is that, when several elements on an HTML page are supposed to be handled in a similar fashion, we define a single handler on their common ancestor in charge of all these elements.
One can say that web component approach emphasize this pattern by making a specific type of component self-aware of its events. Check the for more information.
This is made possible because we have the event object with the target property, alowing us to see where the event actually took place in the page.
For example, imagine that we have a table, with various element inside each cell. The objective is to overlay the clicked cell.
Delegation pattern can also be used for other uses. For example, to match action in a menu. The trivial solution is to assign for each entry of the menu an handler on the click. But there is a more elegant solution to that using delegation.
For that, we will use HTML data attribute, attach the handler directly to the menu and rely on a menu object. All the logical operation will be performed directly in the object, which is a good way to structure your code.
HTML:
JS
Please note that this.onClick is bound to this in (1). That’s important, because otherwise this inside onClick would reference the DOM element (elem), not the Menu object, and this[action] would not be what we need (cf. ).
Behavior pattern
The behavior pattern rely both the delegation pattern and the data attribute of HTML. The idea behind this pattern is to assigne specific action to specific data-attribute, by using a top level delegation. In other words, we attach to the document itself a handler and verify the very existence of the attribute. It has thus two parts:
We add a custom attribute to an element that describes its behavior.
A document-wide handler tracks events, and if an event happens on an attributed element – performs the action.
Example of counter associate with data-counter:
You can use this approach for toggling visibility and elements on the page.
/ mouseout – when the mouse cursor comes over / leaves an element.
– the current phase (capturing=1, target=2, bubbling=3).
let obj = {
handleEvent(event) {
alert(event.type + " at " + event.currentTarget);
}
};
elem.addEventListener('click', obj);
class Menu {
handleEvent(event) {
let method = 'on' + event.type[0].toUpperCase() + event.type.slice(1); //we retrieve the name of the event, the we split to conserve the name for the function
this[method](event); //look here: calling the appropriate function according to event
}
onMousedown() {
elem.innerHTML = "Mouse button pressed";
}
onMouseup() {
elem.innerHTML += "...and released.";
}
}
let menu = new Menu();
elem.addEventListener('mousedown', menu);
elem.addEventListener('mouseup', menu);
var myCEvent = new CustomeEvent("custom", {detail : aVar.value, name : elem.name})
// access the data as usual in the handling function
function evtHandler(e)
{
console.log("Details are" + e.detail);
}
table.addEventListener('click',function(event) {
let td = event.target.closest('td'); // returns the nearest ancestor that matches the selector.
if (!td) return; // if the user did not click on a td, nothing to do
if (!table.contains(td)) return; // if there is nested table, the td could not be the td of the table we are interested in, so return
highlight(td); // highlight the cell, for example with selectedTd.classList.add('highlight');
});
