Text-input-v3 implementation in chromium does not work with sway

[q234rty]

• Sway Version:

  • sway version 1.10-dev-9a1c411ab (Aug 6 2024, branch 'master')
  • wlroots 4481c6b243e979ccee156c4e1a6dfbedcddc99c6

• Debug Log:

  • sway -d : https://0x0.st/XVa8.log
  • WAYLAND_DEBUG=1 logs for chromium: https://0x0.st/XVaK.log

• Description:

  • Run fcitx5 -d
  • Run a snapshot build of chromium with --ozone-platform=wayland --enable-wayland-ime --wayland-text-input-version=3 The build I have used has build number 1336936 and is available here
  • Try to input some text
  • Observe that the IME pops up but no text can be commited into chromium.
    I was inclined to report this to chromium but have found that other compositors such as kwin and labwc works, so I decided to report this here instead.

[ogarai]

I tried on arch + sway version 1.9 with fcitx5-anthy and in my case it seems to be working fine, except for the candidate selection popup which doesn't work on any app on sway.

Screencast.from.2024-08-06.16-52-49.webm

[q234rty]

I tried on arch + sway version 1.9 with fcitx5-anthy and in my case it seems to be working fine, except for the candidate selection popup which doesn't work on any app on sway.

Interesting, I can't reproduce your results at all, even if I switch to sway 1.9 and use fcitx5-anthy instead of fcitx5-chinese-addons.

Would be great if you can post full WAYLAND_DEBUG=1 logs for chromium in your setup.

[ogarai]

Would be great if you can post full WAYLAND_DEBUG=1 logs for chromium in your setup.

wl_debug.txt

[q234rty]

wl_debug.txt

Interesting, here's my logs on sway 1.9 for comparison:
wayland-debug-chromium.log
After the first xdg_activation_v1@25.activate event my logs have the following lines while your logs do not:

[ 960977.755]  -> wl_compositor@9.create_surface(new id wl_surface@40)
[ 960977.778]  -> wp_fractional_scale_manager_v1@23.get_fractional_scale(new id wp_fractional_scale_v1@48, wl_surface@40)
[ 960977.783]  -> wp_viewporter@20.get_viewport(new id wp_viewport@49, wl_surface@40)
[ 960977.786]  -> wp_content_type_manager_v1@22.get_surface_content_type(new id wp_content_type_v1@50, wl_surface@40)
[ 960977.798]  -> wl_compositor@9.create_region(new id wl_region@51)
[ 960977.801]  -> wl_region@51.add(0, 0, 1, 1)
[ 960977.804]  -> wl_surface@40.set_opaque_region(wl_region@51)
[ 960977.806]  -> wl_region@51.destroy()
[ 960977.966]  -> zwp_text_input_manager_v3@19.get_text_input(new id zwp_text_input_v3@52, wl_seat@29)

After this most of the actions seem to have went to zwp_text_input_v3@52 instead...

[q234rty]

@leihaojun sway 1.9 supports text-input-v3 and input-method-v2, it just does not support rendering input-method popups.

[q234rty]

it seem that chromium only support text-input-v1, so sway can't make it work....

It has just added basic support for text-input-v3, that's why the bug description mentions a snapshot build. See also the latest comments in https://issues.chromium.org/issues/40113488