From ab7a1869b26903bfe76c4e277ca169f2f770d002 Mon Sep 17 00:00:00 2001 From: LeviDing Date: Sat, 28 Mar 2020 17:37:56 +0800 Subject: [PATCH] Update article.md --- 2-ui/3-event-details/1-mouse-events-basics/article.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/2-ui/3-event-details/1-mouse-events-basics/article.md b/2-ui/3-event-details/1-mouse-events-basics/article.md index 42f4b6f5..4a5ea641 100644 --- a/2-ui/3-event-details/1-mouse-events-basics/article.md +++ b/2-ui/3-event-details/1-mouse-events-basics/article.md @@ -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