[kwin] [Bug 483809] Certain special keys on the virtual keyboard don't map to the correct key in Chrome
https://bugs.kde.org/show_bug.cgi?id=483809 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kclock/-/merge_requests/117 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483809] Certain special keys on the virtual keyboard don't map to the correct key in Chrome
https://bugs.kde.org/show_bug.cgi?id=483809 --- Comment #2 from Devin Lin --- Phosh's keyboard apparently uses https://wayland.app/protocols/virtual-keyboard-unstable-v1 for anything other than text-input-v3, I'm not sure how kwin does it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483809] Certain special keys on the virtual keyboard don't map to the correct key in Chrome
https://bugs.kde.org/show_bug.cgi?id=483809 --- Comment #1 from Devin Lin --- Starting the app (chromium/electron) with the --enable-wayland-ime and --ozone-platform-hint=auto flags fixes it. I suspect it's a bug with the vkbd when invoked on an app that doesn't support the text input protocols -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483809] Certain special keys on the virtual keyboard don't map to the correct key in Chrome
https://bugs.kde.org/show_bug.cgi?id=483809 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
