DOM event listeners are JavaScript functions that wait for specific events (like clicks, key presses, or form submissions) to occur on HTML elements. When an event fires, it propagates through the DOM in three phases: capture phase (from window down to the target), target phase (at the element itself), and bubble phase (back up to window). Listeners can be attached to any phase using the addEventListener method's third parameter.

Browsers do not expose a standard JavaScript API to retrieve already-registered event listeners. The getEventListeners() method is only available in Chrome DevTools console, not in regular page scripts. This tool works by intercepting addEventListener and removeEventListener calls made after the tool loads, and by reading inline on* attributes (like onclick) which are always visible. For a complete view, use Chrome DevTools' Elements panel.

Event capturing (capture phase) travels from the window down through ancestor elements to the target element. Event bubbling travels from the target element back up through ancestors to window. By default, addEventListener listens in the bubbling phase. To listen during capture, pass true or {capture: true} as the third argument. Understanding this flow is crucial for debugging event handling issues and avoiding unexpected behavior in complex UIs.

Event listeners hold references to DOM elements and their callback functions. If an element is removed from the DOM but its event listener still references it (or the listener's closure holds a reference), the garbage collector cannot free that memory. This is especially common in SPAs. Always use removeEventListener when cleaning up, or use the {once: true} option for one-time listeners. The AbortController with {signal} is another modern approach to cleanly remove listeners.

A passive event listener (set via {passive: true}) tells the browser that the listener will not call preventDefault(). This allows the browser to optimize scrolling performance because it doesn't need to wait for the listener to finish before scrolling. Passive mode is especially important for touchstart, touchmove, wheel, and scroll events. Modern browsers treat touchstart and touchmove as passive by default for better mobile performance.

Common reasons: (1) The listener is attached to a parent element that's not yet in the DOM. (2) Another listener calls stopPropagation() or stopImmediatePropagation(), preventing yours from running. (3) The element is covered by another element (z-index or overlay), so clicks hit the wrong target. (4) The event type is wrong (e.g., change vs input). Use this inspector's live monitor to see which events actually fire and on which elements, helping you trace the issue.

Event delegation is a technique where you attach a single event listener to a parent element instead of individual listeners to each child. It leverages event bubbling: events from children bubble up to the parent, where you can check event.target to determine which child triggered the event. This is efficient for dynamic lists, tables, or any container with many children. It reduces memory usage and automatically handles newly added children without re-attaching listeners.

React uses synthetic events — a cross-browser wrapper around native events. Instead of attaching listeners to individual DOM elements, React attaches them at the root level and uses event delegation internally. This is why you may not see individual listeners on React-managed elements. Vue.js similarly uses event delegation in many cases. These framework-level listeners will still appear in the live event monitor, but the tracked listener count may not reflect framework-internal handlers.