You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
regreet 0.1.1, sway 1.10+wlroots 0.18.1, also sway 1.9+wlroots 0.17.4
Trying ReGreet on a touchscreen-only device, I've noticed that keyboard input using squeekboard does not work as intended. zwp_text_input_v3 enter is not called until an input field is selected AFTER a window focus change has taken place. This is not the case with gtkgreet.
Press the user name field using touch input. The keyboard is toggled, but no zwp_text_input_v3#.*.enter event is received. Keyboard input via squeekboard is not received.
Via ssh, run SWAYSOCK=/run/user/*/sway*.sock swaymsg focus parent
Select the user name field using touch input. Not until now the zwp_text_input_v3#.*.enter event is received.
The text was updated successfully, but these errors were encountered:
I don't have a touch-enabled device to test this out 😅. I tried this same setup on my Arch desktop, but squeekboard wouldn't pop up. I had to type with my physical keyboard. Is it actually supported on desktops, or only on touchscreen-only devices?
regreet 0.1.1, sway 1.10+wlroots 0.18.1, also sway 1.9+wlroots 0.17.4
Trying
ReGreet
on a touchscreen-only device, I've noticed that keyboard input usingsqueekboard
does not work as intended.zwp_text_input_v3 enter
is not called until an input field is selected AFTER a window focus change has taken place. This is not the case withgtkgreet
.swaymsg -t get_tree |jq
yields the same result after touching the text input the second time, so the surface focus logic in https://github.com/swaywm/sway/blob/master/sway/input/text_input.c might be relevant here.To reproduce:
Start via greetd/sway:
Then
zwp_text_input_v3#.*.enter
event is received. Keyboard input via squeekboard is not received.SWAYSOCK=/run/user/*/sway*.sock swaymsg focus parent
zwp_text_input_v3#.*.enter
event is received.The text was updated successfully, but these errors were encountered: