Recently, I have been studying in depth the issues related to the capture and bubbling of events:
I have this understanding, I don’t know if it is right or not, you can take a look.
The event propagation mechanism is divided into three stages: capture stage, reaching target stage, and bubbling stage. I think the purpose of this propagation mechanism is to monitor whether an event occurs, what type of event it occurs, and where the event occurs. The so-called event capture means that the browser is looking for whether an event has occurred. As for the processing time after the event occurs, it is achieved by registering the event processing function and the last parameter of addEventListener().
But if I follow this idea, there will be such a problem.
For example, I have a piece of code like this
I use the capture method to handle events, and prevent the event from continuing to propagate in the event handling function. This seems natural, but my question is, if the event has stopped propagating, how does the browser know where the event occurred? How does it know that an event has occurred? If it doesn't know that an event has occurred, how can it execute the corresponding event handler?
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Your conflict is due to an incorrect understanding of the capture phase. Don’t be bothered by the name. Capturing and bubbling are on the same level. One works from the outside in and the other works from the inside out. So the event interrupt is interrupted during the propagation process, not before the propagation.
If you are talking about how to get it. I think the answer lies in JavaScript Event Loop
Links: https://developer.mozilla.org...
The code is executed by the browser for you, the event is detected by the browser, and then the browser helps you execute the event you specified.
So you ask, how does the browser know?
This is because JavaScript is a directive language. What is a directive language? That is, every JavaScript statement you write is an instruction to notify the browser to do something. For example, the simplest document.getElementById() actually notifies the browser to obtain the relevant DOM, rather than JavaScript itself. The same goes for event handling.
Click to execute
disableClickHandler, preventing event propagation, so...It doesn’t want to know.
It doesn’t know either.
It said it was lazy.