Skip to content

Commit 5eb492e

Browse files
authored
Clarify order of bubble/capture handlers on the target
The way the edited paragraph was written, I initially thought the bubble handler on the target would be ran before the capture handler, which seemed odd. I believe this update clarifies the author's intention and describes better how the handler's actually work.
1 parent 144a2fe commit 5eb492e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

2-ui/2-events/02-bubbling-and-capturing/article.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ There are two possible values for that optional last argument:
145145

146146
Note that while formally there are 3 phases, the 2nd phase ("target phase": the event reached the element) is not handled separately: handlers on both capturing and bubbling phases trigger at that phase.
147147

148-
If one puts a handler on the target element -- it triggers last on the capturing state, and first on the bubbling stage.
148+
If one puts capturing and bubbling handlers on the target element, the capture handler triggers last in the capturing phase and the bubble handler triggers first in the bubbling phase.
149149

150150
Let's see it in action:
151151

0 commit comments

Comments
 (0)