-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
chrome+wayland text selection bug #668
Comments
I think the first one might be a chromium issue, because I failed to reproduce it in alacritty. Still not really sure because it's a terminal emulator and might have special processing when it comes to text selection. |
Currently unable to reproduce on latest clean installs of Note that I don't have much time to test this. It seems like I can't reproduce issues based on what @keighrim said. |
Just tested with brave, and got exactly the same errors OS: Arch Linux x86_64
Kernel: 6.8.8-arch1-1
Shell: bash 5.2.26
DE: KDE Plasma 6.0.4
WM: KWin (Wayland)
Terminal: konsole 24.2.2
---
$ pacman -Qs kime
local/kime-git 3.0.2.r9.gf82ce41-1
Korean IME
local/kime-git-debug 3.0.2.r9.gf82ce41-1
Detached debugging symbols for kime-git
$ git --git-dir ~/.cache/yay/kime-git/kime-git show | head -3
commit f82ce419f697d4f836e79bf6c3de074f35f96f23
Author: Janghyub Seo <[email protected]>
Date: Mon Apr 8 14:56:28 2024 +0900
$ pacman -Qs brave
local/brave-bin 1:1.65.126-1
Web browser that blocks ads and trackers by default (binary release)
$ cat ~/.config/brave-flags.conf
--ozone-platform=wayland
--enable-wayland-ime @ASerinYellsNotCute could you please confirm your brave is running on wayland, not x11/xwayland? |
Seems like I have misunderstood. It shows up "X11", not wayland. Sorry for the hesitation. |
Can confirm some other Wayland programs delete selected text when any key is pressed not just a-z, 0-9, backspace, delete. The issue only occurs when "kime-wayland" is running. Additional programs that do not work
I use kime 3.1.1, Arch 6.10.10, Sway 1.9-5 Not all native Wayland programs have this issue. However it looks like this could be an issue with kime? |
First off, here's my environment.
I had been using kime + chrome + xwayland for a while and it served me fine w.r.t. Hangul typing experience, but found that there was a PR (#659 ) recently merged for a better support for wayland native protocols, so I tried to install upstream (
kime-git
AUR package) and tested out. kime works pretty well in general with wayland-native chrome (--ozone-platform=wayland --enable-wayland-ime
), but not perfectly. I found two (one somewhat critical and one minor-ish) problems related to text selection, and I 'll try to describe them here. (They are observed in both English and Hangul modes)you
.you
.I'm not sure these are chrome bugs or kime bugs (or an unfixable technical or political limitation of the current wayland IM landscape). If this is indeed a chrome/chromium problem, could you point me to the right direction so that I can open a ticket on the chrome side?
Thanks for the great work by the way!
The text was updated successfully, but these errors were encountered: