From d40fbffdaaa4f33397aaab562f01cce0354f1cca Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Sun, 7 Oct 2018 16:03:21 +0300 Subject: [PATCH] fix --- 2-ui/2-events/02-bubbling-and-capturing/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2-ui/2-events/02-bubbling-and-capturing/article.md b/2-ui/2-events/02-bubbling-and-capturing/article.md index 04f2b87a..287f74f2 100644 --- a/2-ui/2-events/02-bubbling-and-capturing/article.md +++ b/2-ui/2-events/02-bubbling-and-capturing/article.md @@ -187,7 +187,7 @@ There's a property `event.eventPhase` that tells us the number of the phase on w The event handling process: - When an event happens -- the most nested element where it happens gets labeled as the "target element" (`event.target`). -- Then the event first moves from the document root down the `event.target`, calling handlers assigned with `addEventListener(...., true)` on the way. +- Then the event first moves from the document root down to the `event.target`, calling handlers assigned with `addEventListener(...., true)` on the way. - Then the event moves from `event.target` up to the root, calling handlers assigned using `on` and `addEventListener` without the 3rd argument or with the 3rd argument `false`. Each handler can access `event` object properties: