GTK4 and input method.

[fxzxmicah]

https://github.com/flathub/com.google.ChromeDev/issues/117:

Google Chrome have IBus support on wayland when --gtk-version=4 is set as parameter (and --ozone-platform-hint=auto and/or --ozone-platform=wayland depending on the version). but IBus doesn't still work. that may be because the flatpak image doesn't have libgtk-4.so.

https://chromium.googlesource.com/chromium/src/+/23978dee2f47d915f79f2646822145aa021ad5a4

[fxzxmicah]

Maybe a build based on the org.gnome.Platform runtime is needed.

[vulpes2]

This is not a fix for mutter, but text-input-v1 support can be enabled in Chromium (and electron applications) with --enable-wayland-ime, which will fix IME support on compositors like Weston, KWin or Hyprland. For mutter there is an open merge request for it, but it's uncertain whether it will be merged or not. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3751

[fxzxmicah]

This is not a fix for mutter, but text-input-v1 support can be enabled in Chromium (and electron applications) with --enable-wayland-ime, which will fix IME support on compositors like Weston, KWin or Hyprland. For mutter there is an open merge request for it, but it's uncertain whether it will be merged or not. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3751

If that's the case, that's great.

[ivanjx]

is it available yet given that the MR is merged?

edit: sorry i meant to say that text-input-v3 support is merged into chromium.

[fxzxmicah]

Initial support for text-input-v3 in chromium should be there from M129 onwards, which can be enabled using the "Wayland text-input-v3" (#wayland-text-input-v3) experimental feature flag from chrome://flags or command line switches --enable-wayland-ime --wayland-text-input-version=3, provided ozone/wayland is enabled already.

[ivanjx]

i guess it is not in this flatpak yet but it seems to work fine in com.google.ChromeDev with the new experimental flags. not perfect but at least working.