Course contentsShow
← Web Development
Lesson 722 of 2,98213. DOM EventsFree lesson

Event Target vs currentTarget

Distinguishing between event.target (where event originated) and event.currentTarget (where listener attached).

Event Target vs currentTarget

You'll learn: How to distinguish between the element that triggered an event and the element listening for it.

The Core Difference

When an event fires in the DOM, two important properties help you identify where the event came from:

  • event.target - the element where the event originated (the actual element clicked, typed into, etc.)
  • event.currentTarget - the element where the listener is attached (the element running the event handler)

These are often the same element, but they differ during event bubbling or event capturing.

A Real-World Analogy

Imagine you're at a concert. Someone shouts from the crowd:

  • event.target is the person who actually shouted
  • event.currentTarget is the security guard stationed at a specific section who heard it

The guard (currentTarget) always knows their post, but the shout (target) could come from anywhere in their section.

When They Differ

When you attach a listener to a parent element, clicking a child will cause:

document.querySelector('.parent').addEventListener('click', function(event) {
  console.log(event.target);        // The child element you actually clicked
  console.log(event.currentTarget); // The .parent element (where listener is)
});

If you click a <button> inside .parent, target is the button, but currentTarget remains .parent.

Why This Matters

This distinction is crucial for event delegation patterns (which we'll explore later) and for understanding which element you're actually interacting with versus which one is handling the event.

Key Takeaway: event.target tells you where the event originated; event.currentTarget tells you where the listener is attached—they're only the same when you click the exact element with the listener.