-
Notifications
You must be signed in to change notification settings - Fork 13
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
Chromium doesn't accept some characters #31
Comments
Yep. Even worse - it looks like it sometimes works and sometimes does not. I remember attempting to read through the chromium input handling code last time it came up, but I just could not and gave up... Might either try later again or just implement the workaround. |
Someone on Mastodon pointed me to this comment: https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/244#note_1237206 Note, the URL bar empties itself when switching the keymap it seems. Other text fields don't. |
Okay, found a better workaround: ValveSoftware/gamescope@6764da3 |
@emersion It's not really obvious how to apply that workaround - does it work? If it does, could you apply it to the repo (any downsides)? |
I hit this problem as well and have a slightly different workaround. That has worked for me in terminals and in chrome (both in address bar and in text areas) |
Having an issue where wtype cannot type emojis into Discord or VSCode. This seems related? How can we apply the workaround? |
Works: "🐸", "!", ":", "a". Doesn't work: "é", "α", "#".
No idea why.
Workaround: ValveSoftware/gamescope@d09516b
The text was updated successfully, but these errors were encountered: