A small, fast delegated event library for JavaScript.
import {on, off, fire} from 'delegated-events';
// Listen for browser-generated events.
on('click', '.js-button', function(event) {
console.log('clicked', this);
});
// Listen for custom events triggered by your app.
on('robot:singularity', '.js-robot-image', function(event) {
console.log('robot', event.detail.name, this.src);
});
// Dispatch a custom event on an element.
var image = document.querySelector('.js-robot-image');
fire(image, 'robot:singularity', {name: 'Hubot'});The standard method of registering event handler functions is to directly bind the listener to the element.
// Find an element and bind a function directly to it.
var button = document.querySelector('.js-button');
button.addEventListener('click', function(event) {
console.log('clicked', event.target);
});If we have several clickable elements, listeners can be directly registered on them in a loop.
// Find all the buttons and attach a function to each of them.
var buttons = document.querySelectorAll('.js-button');
buttons.forEach(function(button) {
button.addEventListener('click', function(event) {
console.log('clicked', event.target);
});
});Directly binding event listeners to elements works great if the page doesn't change after it's initially loaded. However, if we dynamically add another button to the document, it won't receive a click event.
// No click handler is registered on the new element.
var button = document.createElement('button');
button.textContent = 'Push';
var list = document.querySelector('.js-button-list');
list.appendChild(button);A solution to this is to delegate the event handler up the tree to the parent element that contains all of the button children. When a button is clicked, the event bubbles up the tree until it reaches the parent, at which point the handler is invoked.
// Event handling delegated to a parent element.
var list = document.querySelector('.js-button-list');
list.addEventListener('click', function(event) {
console.log('clicked', event.target);
});However, now anything clicked inside the list will trigger this event
handler, not just clicks on buttons. So we add a selector check to determine
if a button generated the click event, rather than a span element, text, etc.
// Filter events by matching the element with a selector.
var list = document.querySelector('.js-button-list');
list.addEventListener('click', function(event) {
if (event.target.matches('.js-button')) {
console.log('clicked', event.target);
}
});Now we have something that works for any button element inside the list whether it was included in the initial HTML page or added dynamically to the document sometime later.
But what if the list element is added to the page dynamically?
If we delegate most events up to the global document, we no longer worry
about when elements are appended to the page—they will receive event listeners
automatically.
// Delegated click handling up to global document.
document.addEventListener('click', function(event) {
if (event.target.matches('.js-button')) {
console.log('clicked', event.target);
}
});Now that we've covered how browsers handle directly-bound and delegated events natively, let's look at what this library actually does.
The goals of this library are to:
- Provide shortcuts that make this common delegation pattern easy to use in web applications with hundreds of event listeners.
- Use the browser's native event system.
- Speed 🐎
Delegated event handling shortcuts (on, off, fire) are provided
so event handlers aren't required to test for matching elements
themselves. jQuery has great documentation on event delegation with selectors too.
Here's the same globally delegated handler as above but using on.
// Easy :)
on('click', '.js-button', function(event) {
console.log('clicked', event.target);
});To provide compatibility with older browsers, jQuery uses "synthetic" events. jQuery listens for the native browser event, wraps it inside a new event object, and proxies all function calls, with modifications, through to the native object.
All browsers now share a standard event system, so we can remove the extra layer of event handling to recover performance.
The delegated event system is written in vanilla JavaScript,
so it won't significantly increase download times (minified + gzip = 640 bytes).
It relies on a small SelectorSet
data structure to optimize selector matching against the delegated events.
A micro-benchmark to compare relative event handling performance is included
and can be run with npm run bench.
A fire shortcut function is provided to trigger custom events with
attached data objects.
on('validation:success', '.js-comment-input', function(event) {
console.log('succeeded for', event.detail.login);
});
var input = document.querySelector('.js-comment-input');
fire(input, 'validation:success', {login: 'hubot'});The standard way of doing this works well but is more verbose.
document.addEventListener('validation:success', function(event) {
if (event.target.matches('.js-comment-input')) {
console.log('succeeded for', event.detail.login);
}
});
var input = document.querySelector('.js-comment-input');
input.dispatchEvent(
new CustomEvent('validation:success', {
bubbles: true,
cancelable: true,
detail: {login: 'hubot'}
})
);If you're using TypeScript, you can maintain a list of custom event names that map to their specific types, making it easier to write type-safe code while using delegated events. Add the following snippet to a .d.ts file in your local project and alter the contents of CustomEventMap to list all the well-known events in your project:
// events.d.ts
interface CustomEventMap {
'my-event:foo': {
something: boolean
}
// When adding a new custom event to your code, add the event.name + event.detail type to this map!
}
// Do not change code below this line!
type CustomDelegatedEventListener<T> = (this: Element, ev: CustomEvent<T> & {currentTarget: Element}) => any
declare module 'delegated-events' {
export function fire<K extends keyof CustomEventMap>(target: Element, name: K, detail: CustomEventMap[K]): boolean
export function on<K extends keyof CustomEventMap>(
name: K,
selector: string,
listener: CustomDelegatedEventListener<CustomEventMap[K]>
): void
}
declare global {
interface Document {
addEventListener<K extends keyof CustomEventMap>(
type: K,
listener: (this: Document, ev: CustomEvent<CustomEventMap[K]>) => unknown,
options?: boolean | AddEventListenerOptions
): void
}
interface HTMLElement {
addEventListener<K extends keyof CustomEventMap>(
type: K,
listener: (this: HTMLElement, ev: CustomEvent<CustomEventMap[K]>) => unknown,
options?: boolean | AddEventListenerOptions
): void
}
}Now TypeScript is able to type-check your events in both delegated-events callsites and the standard addEventListener callsites:
fire(document.body, 'my-event:foo', {something: true})
on('my-event:foo', 'body', event => {
event.detail.something // typescript knows this is a boolean
})
document.addEventListener('my-event:foo', event => {
event.detail.something // typescript knows this is a boolean
})
document.body.addEventListener('my-event:foo', event => {
event.detail.something // typescript knows this is a boolean
})- Chrome
- Firefox
- Safari 6+
- Internet Explorer 9+
- Microsoft Edge
Internet Explorer requires polyfills for CustomEvent
and WeakMap.
npm run bootstrap
npm test
npm run bench
npm run browser
Distributed under the MIT license. See LICENSE for details.