JavaScript Events and Event Delegation: Complete Guide

By Murat Bo · Published Jul 16, 2026 · Copy for AI · Markdown

JavaScript events let your code respond to user actions and browser changes, such as clicks, form submissions, key presses, and page loading. Event delegation is a pattern that makes event handling simpler and more efficient, especially when elements are created dynamically.

Quick answer: An event is a browser notification that something happened, and event delegation means attaching one listener to a parent element instead of separate listeners to each child. The parent handles events that bubble up from matching descendants.

1. What Are JavaScript Events?

Events are signals from the browser that something happened in the page or in the environment. Your JavaScript can listen for those signals and run code in response.

• User interactions like click, input, submit, and keydown.
• Browser lifecycle events like DOMContentLoaded and load.
• State and UI changes like scroll, resize, and focus.

An event listener is the function that runs when the event happens. Without listeners, the browser still produces events, but your code does nothing with them.

2. Why Event Delegation Matters

Event delegation uses the browser's event bubbling behavior to handle many similar elements with one listener. This is useful when you have lists, menus, tables, or any UI where elements may be added or removed after the page loads.

Instead of attaching 200 click listeners to 200 buttons, you can attach one listener to the container that holds them. That usually means less code, easier cleanup, and better behavior for dynamic content.

3. Basic Syntax

Listening for a single event

The most common way to handle an event is with addEventListener(). You give it the event name and a function to run.

button.addEventListener("click", (event) => {
  // Runs when the button is clicked
  console.log("Button clicked");
});

Uncaught ReferenceError: button is not defined

The first argument is the event type. The second argument is the handler function, and the browser passes an event object into that function.

Delegating the event to a parent

With delegation, you listen on the parent element and inspect event.target to see which child started the event.

list.addEventListener("click", (event) => {
  if (event.target.matches("button.remove")) {
    console.log("Remove button clicked");
  }
});

Uncaught ReferenceError: list is not defined

This works because the click event bubbles from the button up to the list container.

4. Step-by-Step Examples

Example 1: Button click handler

This example shows the simplest event listener: one element, one action.

const saveButton = document.querySelector("#save");

saveButton.addEventListener("click", () => {
  console.log("Saved!");
});

When the button is clicked, the handler runs immediately. This is the basic pattern used throughout the DOM.

Example 2: Form submission

Forms naturally emit a submit event. You often prevent the default page reload and handle the data yourself.

const form = document.querySelector("form");

form.addEventListener("submit", (event) => {
  event.preventDefault();
  console.log("Form submitted without reload");
});

The call to preventDefault() stops the browser from doing its built-in form submission behavior.

Example 3: Delegated clicks for a dynamic list

Delegation shines when items may be added later. The listener stays on the parent, so newly added buttons still work.

const todoList = document.querySelector(".todo-list");

todoList.addEventListener("click", (event) => {
  if (event.target.matches("button.delete")) {
    const item = event.target.closest("li");
    item.remove();
  }
});

The list container handles all delete button clicks, even for items inserted after the listener was attached.

Example 4: Keyboard interaction

Events are not only for mouse actions. Keyboard events are common in accessibility and shortcuts.

document.addEventListener("keydown", (event) => {
  if (event.key === "Escape") {
    console.log("Close modal");
  }
});

This pattern is often used to close dialogs, cancel menus, or implement shortcuts.

5. Practical Use Cases

• Handling click events on table rows, menu items, or card actions.
• Managing forms with validation, autosave, and custom submit behavior.
• Supporting infinite scroll or dynamically loaded content without reattaching listeners.
• Listening for keyboard shortcuts and accessibility interactions.
• Reducing duplicated listeners in large lists or data tables.

6. Common Mistakes

Mistake 1: Attaching listeners to elements that do not exist yet

New developers often attach a listener before the element is in the DOM or before it has been created. That means the variable may be null, so the listener cannot be attached.

Problem: If the selector does not find an element, calling addEventListener() on null throws a runtime error.

const modalButton = document.querySelector("#open-modal");

modalButton.addEventListener("click", () => {
  console.log("Open modal");
});

Fix: Run the code after the DOM is ready, or check that the element exists before using it.

document.addEventListener("DOMContentLoaded", () => {
  const modalButton = document.querySelector("#open-modal");

  if (modalButton) {
    modalButton.addEventListener("click", () => {
      console.log("Open modal");
    });
  }
});

The corrected version waits until the DOM is available, so the selector can find the button reliably.

Mistake 2: Expecting delegation to work without bubbling

Delegation depends on events reaching the parent. Some events bubble naturally, but others do not behave the same way in every situation, so the parent handler may never run.

Problem: If you listen on a parent for an event that does not reach it in the way you expect, your delegated handler will never fire.

const container = document.querySelector(".container");

container.addEventListener("focus", (event) => {
  if (event.target.matches("input")) {
    console.log("Input focused");
  }
});

Fix: Use an event that bubbles in the way you need, or listen with the right event strategy for that behavior.

const container = document.querySelector(".container");

container.addEventListener("focusin", (event) => {
  if (event.target.matches("input")) {
    console.log("Input focused");
  }
});

The corrected version uses an event that can be handled from the container in a delegated pattern.

Mistake 3: Confusing target with currentTarget

In delegated handlers, these two properties often point to different elements. target is the original element that triggered the event, while currentTarget is the element with the listener attached.

Problem: Using currentTarget to identify which child was clicked will usually give you the parent container, not the button or item you wanted.

list.addEventListener("click", (event) => {
  if (event.currentTarget.matches("button.remove")) {
    console.log("Remove clicked");
  }
});

Uncaught ReferenceError: list is not defined

Fix: Check event.target and then narrow it with matches() or closest().

list.addEventListener("click", (event) => {
  if (event.target.matches("button.remove")) {
    console.log("Remove clicked");
  }
});

Uncaught ReferenceError: list is not defined

This works because target identifies the actual clicked child, which is what delegation depends on.

7. Best Practices

Practice 1: Prefer delegation for repeated child elements

When many elements need the same behavior, delegation avoids duplicate listeners and keeps the code easier to maintain.

// Less preferred for large dynamic lists
document.querySelectorAll(".item button").forEach((button) => {
  button.addEventListener("click", handleRemove);
});

// Preferred when items may change
document.querySelector(".item-list").addEventListener("click", handleRemove);

One listener on the container is easier to update than many listeners on individual children.

Practice 2: Filter delegated events carefully

Always verify that the event came from the right child before acting on it. This prevents accidental behavior when the user clicks inside nested content.

menu.addEventListener("click", (event) => {
  const item = event.target.closest("button[data-action]");

  if (!item) return;

  console.log(item.dataset.action);
});

Uncaught ReferenceError: menu is not defined

Using closest() makes the handler more reliable when buttons contain icons or nested spans.

Practice 3: Remove listeners when you truly need per-element behavior

Not every interaction should be delegated. If an element has unique behavior or uses a non-bubbling pattern, direct listeners can be clearer.

const dialog = document.querySelector("dialog");

dialog.addEventListener("close", () => {
  console.log("Dialog closed");
});

Use the simpler model when delegation would make the code harder to understand or less accurate.

8. Limitations and Edge Cases

• Event delegation works best for events that bubble, such as click and input in common UI cases.
• Some interactions are easier to manage with direct listeners, especially when only one element should respond.
• event.target may be a nested child inside the element you care about, so closest() is often safer than checking only matches().
• Calling stopPropagation() in a child listener can prevent delegated handlers from running.
• Very large delegated containers can still require careful filtering logic to avoid accidental matches.
• Passive listeners, capture phase handlers, and shadow DOM can change how events behave compared with simple examples.

Tip: If your delegated code seems to work only sometimes, check whether another listener is stopping propagation or whether the clicked element is actually a nested child of the selector you expected.

9. Practical Mini Project

This small project builds a task list with one delegated click handler. It demonstrates the main strengths of event delegation: fewer listeners, support for dynamic items, and simple removal logic.

const input = document.querySelector("#task-input");
const addButton = document.querySelector("#add-task");
const taskList = document.querySelector("#tasks");

addButton.addEventListener("click", () => {
  const text = input.value.trim();

  if (text === "") return;

  const item = document.createElement("li");
  item.innerHTML = `<span>${text}</span> <button class="delete" type="button">Delete</button>`;
  taskList.append(item);
  input.value = "";
});

taskList.addEventListener("click", (event) => {
  if (!event.target.matches("button.delete")) return;

  const task = event.target.closest("li");
  task.remove();
});

This example uses direct listeners for the add button and delegated handling for the list because the list items are created dynamically. That split is often the most practical approach.

10. Key Points

• Events are browser notifications that let JavaScript react to user actions and page changes.
• addEventListener() is the standard way to register event handlers.
• Event delegation attaches one listener to a parent and uses bubbling to handle matching children.
• event.target identifies the source element, while currentTarget identifies the element with the listener.
• matches() and closest() help you safely filter delegated events.

11. Practice Exercise

Build a simple notification list that supports adding messages and dismissing them with one delegated click handler.

• Create an input, a button, and an empty list.
• When the button is clicked, add a new list item with a dismiss button.
• Use event delegation on the list so any current or future dismiss button works.

Expected output: Typing a message and clicking the add button inserts a new notification. Clicking dismiss removes only the notification that was clicked.

Hint: Put the click listener on the list element, then use event.target.matches("button.dismiss") or closest().

const messageInput = document.querySelector("#message");
const addNotificationButton = document.querySelector("#add-notification");
const notifications = document.querySelector("#notifications");

addNotificationButton.addEventListener("click", () => {
  const text = messageInput.value.trim();
  if (text === "") return;

  const li = document.createElement("li");
  li.innerHTML = `<span>${text}</span> <button class="dismiss" type="button">Dismiss</button>`;
  notifications.append(li);
  messageInput.value = "";
});

notifications.addEventListener("click", (event) => {
  if (!event.target.matches("button.dismiss")) return;

  const item = event.target.closest("li");
  item.remove();
});

This solution works because the list only needs one click listener, and every newly added dismiss button is handled automatically.

12. Final Summary

JavaScript events are the foundation of interactive web pages. They let your code respond to clicks, typing, submissions, and browser state changes in a structured way.

Event delegation builds on that foundation by using bubbling to manage many related elements through a single listener. That pattern is especially valuable for dynamic lists, menus, and other UIs that change over time.

Once you understand addEventListener(), event.target, bubbling, and delegation, you can write cleaner DOM code and avoid a lot of repetitive listener setup. A good next step is to practice filtering delegated events with matches() and closest() on a real interactive list.