-
Notifications
You must be signed in to change notification settings - Fork 47.5k
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.
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
Synthetic KeyboardEvent should support KeyboardEvent.code #14102
Comments
Seems like Safari also supports this (looking at caniuse.com). Do you want to send a PR? 🙂 |
It seems like the |
@charliesmart We already have |
@philipp-spiess is right, |
I've created the PR to pass the This should also have a change in the docs. How do I go about updating those? Also, when I do would it make sense to comment on the partial lack of browser support? |
is there any updates on this? |
Is anyone working on this? Or can I take it? |
You can access the native event using |
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
The current synthetic keyboard event does not support the
KeyboardEvent.code
property.What is the expected behavior?
The synthetic keyboard event should pass along the
KeyboardEvent.code
property. This is currently in the WD of DOM Events but is part of replacingkeyCode
andcharCode
and is much more consistent and easy to use. This is currently only supported by FF and Chrome (CanIUse) so it may be a bit premature to fully integrate. HoweverkeyCode
,charCode
andwhich
are being deprecated so this will eventually need to be added.Edit: I spoke too quickly, CanIUse shows that FF, Chrome, Safari and Opera support it. IE, Edge and most mobile browsers do not.
The text was updated successfully, but these errors were encountered: