-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Compose Web - KeyEvent mappings #3644
Labels
Comments
Thanks for the report! A reproducer:
Reproduced in Chrome, Windows 11. |
We have 2 issues here:
|
seem to be many issues with KeyEvents on web platform ! |
Reproduced with 1.5.0 and 1.6.0. But it works correctly in |
eymar
added a commit
to JetBrains/compose-multiplatform-core
that referenced
this issue
Apr 9, 2024
eymar
added a commit
to JetBrains/compose-multiplatform-core
that referenced
this issue
Apr 9, 2024
The test for: JetBrains/compose-multiplatform#3644 Also a test for onPreviewKeyEvent issue (JetBrains/compose-multiplatform#2296)
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Observing KeyEvents via the Modifier.onKeyEvent (or the like) function shows that the key "t" is mapped to KEY_UNKNOWN, and the key "6" to KEY_T. As far as I can tell, other keys seem fine.
Affected platforms
Versions
To Reproduce
Expected behavior
T key should map to KEY_T
6 key to KEY_6
The text was updated successfully, but these errors were encountered: