# Over-delegating JavaScript events

DevFeed: [Over-delegating JavaScript events](<https://devfeed.tech/articles/over-delegating-javascript-events-32305.md>)

Original publisher: [Read original article](<https://jack.ofspades.com/over-delegating-javascript-events/>)

Author: Jack Tarantino

Published: 2016-01-27T03:33:40Z

Content type: tutorial

Language: en

Sources: [Jacopo Tarantino](<https://devfeed.tech/sources/jacopo-tarantino.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [interactive web experiences](<https://devfeed.tech/topics/interactive-web-experiences.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [scope](<https://devfeed.tech/tags/scope.md>), [triggers](<https://devfeed.tech/tags/triggers.md>)

## AI overview

The article explains that JavaScript event delegation is useful for handling events from many nodes with one listener, but delegating too high in the DOM can run unnecessary callbacks and allow events to affect unrelated components. It recommends scoping listeners to the nearest appropriate parent and stopping further propagation to reduce unintended behavior and overhead.

## Source excerpt

Delegating event listeners in JavaScript is generally a good practice. It allows us to create only one event listener for events that might be triggered on a variety of nodes and across multiple contexts. If we're just looking to listen for any given click on a page it would be