Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't scroll in FF after switching tabs on libinput platform #2247

Closed
wmww opened this issue Dec 8, 2021 · 3 comments · Fixed by #2275
Closed

Can't scroll in FF after switching tabs on libinput platform #2247

wmww opened this issue Dec 8, 2021 · 3 comments · Fixed by #2275
Labels

Comments

@wmww
Copy link
Contributor

wmww commented Dec 8, 2021

After opening Firefox scrolling works fine on the first tab, but stops working after the first tab switch until it's restarted. Wayland messages Mir is sending seem normal, but this doesn't effect Sway so there must be something different we're doing.

@wmww wmww mentioned this issue Dec 8, 2021
@wmww
Copy link
Contributor Author

wmww commented Dec 8, 2021

Updates:

  • This is present at least as far back as v2.5
  • It happens on libinput/KMS, but not the X11 platform

@wmww wmww changed the title Can't scroll in FF after switching tabs Can't scroll in FF after switching tabs on libinput platform Dec 8, 2021
@AlanGriffiths
Copy link
Contributor

I see this, but only with touchpad scrolling. (Scrolling with mouse wheel works as expected).

@wmww
Copy link
Contributor Author

wmww commented Jan 13, 2022

The problem is that we do not send wl_pointer.axis_stop events for axis sources wl_pointer::axis_source::finger, as required by the protocol.

wayland.xml:

If the source is wl_pointer.axis_source.finger, a wl_pointer.axis_stop event will be sent when the user lifts the finger off the device

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants