Arch Linux

Commodore-Freak

Member

Registered: 2010-06-28

Posts: 6

Gnome OSK auto-summon in Chrome/Chromium

Hi everyone,
so feel like i have thoroughly researched this topic and currently there simply is no solution, but i thought maybe i'll ask here before giving up anyway.

Basically all i want is my Gnome on-screen keyboard to auto-summon when selecting a text input field in a chromium-based browser. I'm using current version of Gnome 45.4 on wayland and chrome/chromium 122.0.
I have set ozone platform to wayland and have been experimenting with --gtk-version=4 and --enable-wayland-ime flags.
Setting the GTK version seemingly doesn't help at all with the osk. Neither does --enable-wayland-ime with current builds of chrome/chromium - but it DOES work with the "chromium-wayland-vaapi" build from AUR! However, this comes with an annoying bug that deletes text in an input field upon selection - plus it's still chromium 120 and flagged out of date, so not a usable experience either.
I believe the reason the --enable-wayland-ime flag works with this particular build is because they are including these patches, which are not included with the official packages (although older google search results imply they used to be?):
0001-ozone-wayland-implement-text_input_manager-fixes.patch
0001-ozone-wayland-implement-text_input_manager_v3.patch
It appears the more up-to-date "ungoogled chromium" build also comes with the same set of patches, however for me it crashes immediately upon launch (regardless of used flags).
I have also tried every fork of chromium i could think of (thorium, brave, vivaldi, edge) but --enable-wayland-ime works with neither of them.

I'm using a Thinkpad X1 Yoga btw. and tablet mode detection/gnome osk auto-summon work just fine on native gnome apps as well as firefox, so this is chrome/chromium specific issue. Manually bringing up the osk in chrome/chromium by swiping up from the bottom is working fine, too.

So yeah, maybe not the most pressing issue, and i'm afraid the answer is before text_input_manager_v3 is officially supported there's not much i can do.
Am i missing something? Any ideas for a workaround? Any input on this is much appreciated.
Thank you for reading