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

redundant

Browse source
This commit is contained in:
joaquinelio 2022-01-08 19:55:36 -03:00 • committed by GitHub
parent 3c934b5a46
commit ecbb2b8379
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
2-ui/3-event-details/7-keyboard-events/article.md
View file

@ -107,7 +107,7 @@ So, `event.code` may match a wrong character for unexpected layout. Same letters
To reliably track layout-dependent characters, `event.key` may be a better way. To reliably track layout-dependent characters, `event.key` may be a better way.
On the other hand, `event.code` has the benefit of staying always the same, bound to the physical key location, even if the visitor changes languages. So hotkeys that rely on it work well even in case of a language switch. On the other hand, `event.code` has the benefit of staying always the same, bound to the physical key location. So hotkeys that rely on it work well even in case of a language switch.
Do we want to handle layout-dependant keys? Then `event.key` is the way to go. Do we want to handle layout-dependant keys? Then `event.key` is the way to go.