Skip to content

Commit 9d423c4

Browse files
committed
Update "Dispatching custom events" article
1 parent 87fb20d commit 9d423c4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

2-ui/2-events/05-dispatch-events/article.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ We can generate not only completely new events, that we invent for our own purpo
88

99
## Event constructor
1010

11-
Built-in event classes form a hierarchy, similar to DOM element classes. The root is the built-in [Event](http://www.w3.org/TR/dom/#event) class.
11+
Built-in event classes form a hierarchy, similar to DOM element classes. The root is the built-in [Event](https://dom.spec.whatwg.org/#events) class.
1212

1313
We can create `Event` objects like this:
1414

@@ -210,7 +210,7 @@ Please note: the event must have the flag `cancelable: true`, otherwise the call
210210

211211
## Events-in-events are synchronous
212212

213-
Usually events are processed in a queue. That is: if the browser is processing `onclick` and a new event occurs, e.g. mouse moved, then it's handling is queued up, corresponding `mousemove` handlers will be called after `onclick` processing is finished.
213+
Usually events are processed in a queue. That is: if the browser is processing `onclick` and a new event occurs, e.g. mouse moved, then its handling is queued up, corresponding `mousemove` handlers will be called after `onclick` processing is finished.
214214

215215
The notable exception is when one event is initiated from within another one, e.g. using `dispatchEvent`. Such events are processed immediately: the new event handlers are called, and then the current event handling is resumed.
216216

0 commit comments

Comments
 (0)