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
Only wl_pointer.motion was used to update pointer position, which would
cause issues if the pointer was not moved prior to wl_pointer.button.
This also fixes touch input through wl_pointer emulation, which fires
wl_pointer.button immediately after wl_pointer.enter.
Closes: swaywm#5991
Only wl_pointer.motion was used to update pointer position, which would
cause issues if the pointer was not moved prior to wl_pointer.button.
This also fixes touch input through wl_pointer emulation, which fires
wl_pointer.button immediately after wl_pointer.enter.
Closes: #5991
neon64
pushed a commit
to neon64/sway
that referenced
this issue
Feb 11, 2021
Only wl_pointer.motion was used to update pointer position, which would
cause issues if the pointer was not moved prior to wl_pointer.button.
This also fixes touch input through wl_pointer emulation, which fires
wl_pointer.button immediately after wl_pointer.enter.
Closes: swaywm#5991
Sway Version:
1.5-40bdd0ee (Jan 6 2021, branch 'master')
Debug Log:
Description:
swaynag
andswaybar
do not react to touch input on my phone, e.g. I cannot dismiss aswaynag
prompt.Additional info
The text was updated successfully, but these errors were encountered: