Rivalry2

HTML Diff

0 added 0 removed

Original 2026-01-01

Modified 2026-02-21

1 Imagine we have two nested elements, each with aclickevent handler. If you click on an area of an external element that doesn't affect an internal one, then the handler bound to this external element will be executed.

2 If we click on the inner element, then the outer one will also be clicked on automatically, so both events will occur:

3 You may wonder in what order these events will happen after clicking the button. In general, an event will pass through the tree from the root, go to the deepest element triggered by the event, and then in the opposite direction.

4 The journey of an event up and down the tree is called itsstagesorphases. We will see more about that below.

5 <h2>Capturing</h2>

6 When an event has just occurred, it starts moving through the DOM tree, starting from the root node and going to the deepest one where the event occurred:

7 | | ---------------| |--------------- | div | | | | -----------| |----------- | | | button \ / | | | ------------------------- | | Event CAPTURING | ---------------------------------

8 At the capturing stage, we execute the handlers bound to this stage. The binding is regulated by the third parameter of the addEventListener function:

9 The value true binds handlers to the capturing stage. The following output will result:

10 Boom 2! Boom 1!

11 <h2>Bubbling</h2>

12 Once the capturing stage ends at thetargetelement, the bubbling stage begins:

13 / \ ---------------| |--------------- | div | | | | -----------| |----------- | | | button | | | | | ------------------------- | | Event BUBBLING | ---------------------------------

14 We imply this stage when we call addEventListener without specifying the third parameter:

15 At this stage, the handlers are executed from the inside out:

16 Boom 1! Boom 2!

17 <h2>Why?</h2>

18 Event bubbling is an important part of DOM behavior. Without it, it is impossible to implement events triggered on entire blocks, not just on the deepest elements.

19 The simplest example is a context menu. Another example could be tables arranged like in Microsoft Excel. These tables are huge, and adding events to each cell would create many identical handlers constantly added as the table grows. Besides the extra code, this strategy slows everything down if you work with many things. It's much easier to put one handler on the whole table.

20 <h2>W3C Model</h2>

21 According to the standard, most events go through both stages, first plunging into the depths of the tree and then rising to the very top. Programmers rarely use the capturing stage, so they hang most handlers on the bubbling one.

22 In the previous lesson, we saw the e.target object. It is the deepest element that the capture stage goes to.

23 The target element doesn't change during bubbling. It allows you to find out exactly where the event took place. In addition, the currentTarget object is also available; this is the element the handler is attached to. One or the other is used, depending on the situation:

24 Usually, the event should bubble to the end, but there are some situations where bubbling is undesirable.

25 There are two ways to do this:

26 <ul><li>event.stopPropagation() - stops bubbling, but gives all the handlers that are hovering over the current element a chance to refine</li>

27 <li>event.stopImmediatePropagation() - doesn't allow us to execute any more handlers</li>

28 </ul>Let's summarize. Interception is a mechanism for passing an event to a handler. During capturing or bubbling, the event passes from one element to another, and if there is a handler for this event in the element, it gets called.

29 In other words, the handler intercepts the event. And using the methods described above, we can stop the process of passing an event between elements.