Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

toast.inputdevice: KeyboardEvent.keyCode vs KeyboardEvent.code #104

Open
CravateRouge opened this issue Oct 28, 2020 · 0 comments
Open

toast.inputdevice: KeyboardEvent.keyCode vs KeyboardEvent.code #104

CravateRouge opened this issue Oct 28, 2020 · 0 comments

Comments

@CravateRouge
Copy link
Contributor

Why do you use KeyboardEvent.keyCode that is deprecated and needs extra work in your examples (linking keyCodes to names in a collection) instead of using KeyboardEvent.code where you just have to use the key name to match the correct key?

I tested KeyboardEvent.code in a tv samsung 5.5 simulator and it works.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CravateRouge