Test results on Ubuntu 26.04 (gnome-shell 50.1-0ubuntu1.5, mutter 50.1-0ubuntu2.4, fcitx5 5.1.19-1, fcitx5-unikey 5.1.10-1). "Patched" is the 5.1.19 IBus frontend rebuilt with only the preedit mode changed from 0 to 1, which is what upstream commit 10ca8e0c does for normal preedit. dbus-monitor confirms mode 0 before and mode 1 after.
Google Chrome, native Wayland, textarea; type "tieengs" (preedit "tiếng"), then click: - elsewhere in the same textarea: lost with stock 5.1.19, kept with patched. This is the case in the test plan. - on the desktop: kept with both. Chrome commits the composition itself when it loses focus. GNOME Text Editor (GTK 4), same word, click on the desktop: - lost with stock 5.1.19, and still lost with patched. So the fcitx5 change fixes the Chrome case in the test plan, but not GTK 4 apps losing focus by mouse click. Those keep the word on Fedora 45 (mutter 51.1, fcitx5 5.1.23), so the rest is likely on the mutter side. The 50.2 change "Implement support for version 2 of text_input_v3 protocol" (mutter!3600) is a candidate; I have not confirmed it. Same report from the engine side: https://github.com/fcitx/fcitx5-unikey/issues/54 ** Bug watch added: github.com/fcitx/fcitx5-unikey/issues #54 https://github.com/fcitx/fcitx5-unikey/issues/54 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172006 Title: Clicking in a Wayland-native Chromium/Electron window drops the word being composed (fixed upstream in fcitx5 5.1.20) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx5/+bug/2172006/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
