Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 3673751

Browse files
authored
Fix typo
1 parent fcfef6a commit 3673751

File tree

1 file changed

+1
-1
lines changed
  • 2-ui/2-events/01-introduction-browser-events

1 file changed

+1
-1
lines changed

‎2-ui/2-events/01-introduction-browser-events/article.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -446,7 +446,7 @@ HTML attributes are used sparingly, because JavaScript in the middle of an HTML
446446

447447
DOM properties are ok to use, but we can't assign more than one handler of the particular event. In many cases that limitation is not pressing.
448448

449-
The last way is the most flexible, but it is also the longest to write. There are few events that only work with it, for instance `transtionend` and `DOMContentLoaded` (to be covered). Also `addEventListener` supports objects as event handlers. In that case the method `handleEvent` is called in case of the event.
449+
The last way is the most flexible, but it is also the longest to write. There are few events that only work with it, for instance `transitionend` and `DOMContentLoaded` (to be covered). Also `addEventListener` supports objects as event handlers. In that case the method `handleEvent` is called in case of the event.
450450

451451
No matter how you assign the handler -- it gets an event object as the first argument. That object contains the details about what's happened.
452452

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /