jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Merge pull request #1827 from leviding/patch-12

Browse source 
Fix type error
This commit is contained in:
Alexey Pyltsyn 2020-03-29 05:53:44 +03:00 • committed by GitHub
commit be80c33c55
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

7
2-ui/3-event-details/1-mouse-events-basics/article.md
View file

@ -65,8 +65,8 @@ But if we track `mousedown` and `mouseup`, then we need it, because these events
There are the three possible values:
- `event.which == 1` -- the left button
- `event.which == 2` - the middle button
- `event.which == 3` - the right button
- `event.which == 2` -- the middle button
- `event.which == 3` -- the right button
The middle button is somewhat exotic right now and is very rarely used.
@ -116,8 +116,7 @@ For JS-code it means that we should check `if (event.ctrlKey || event.metaKey)`.
```
```warn header="There are also mobile devices"
Keyboard combinations are good as an addition to the workflow. So that if the visitor has a
keyboard -- it works. And if their device doesn't have it -- then there should be another way to do the same.
Keyboard combinations are good as an addition to the workflow. So that if the visitor has a keyboard -- it works. And if their device doesn't have it -- then there should be another way to do the same.
```
## Coordinates: clientX/Y, pageX/Y