What is event capturing?
Assesses fundamental understanding of JavaScript conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Event capturing is a phase of event propagation in which an event is first intercepted by the outermost ancestor element, then travels downward through the DOM hierarchy until it reaches the target (innermost) element.
To handle events during the capturing phase, you need to pass true as the third argument to the addEventListener method.
<div>
<button class="child">Hello</button>
</div>
<script>
const parent = document.querySelector("div");
const child = document.querySelector(".child");
// Capturing phase: parent listener (runs first)
parent.addEventListener("click", function () {
console.log("Parent (capturing)");
}, true); // `true` enables capturing
// Bubbling phase: child listener (runs after)
child.addEventListener("click", function () {
console.log("Child (bubbling)");
});
</script>
// Parent (capturing)
// Child (bubbling)
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.