-
Notifications
You must be signed in to change notification settings - Fork 88
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
Sideways scrolling works very badly with mouse #3862
Comments
Tracking here igordanchenko/yet-another-react-lightbox#305 |
The upstream issue seems to be resolved, according to that link. How often does Flathub update this part of the website, so that I can check if it actually resolves the issue? Thanks! :) |
I already updated to the relevant version |
Thanks! Then upstream doesn't seem to actually have fixed it after all, because nothing has changed for me. |
It changed for my mouse |
Still doesn't work for me. I asked on Reddit for more people to test, unfortunately only one did, but it didn't work for them either https://www.reddit.com/r/flatpak/comments/1fx33p5/help_me_test_a_bug_on_flathub/ I'm on Firefox 131.02 |
It would be interesting to see the values your mouse produces and report them upstream |
Sure. How would I find those? |
Hi. Quite a few mice have a scroll wheel that also can be pushed to the side to scroll sideways. When I use such a mouse and see a sideways scrolling UI, I expect to be able to scroll trough it that way.
This works so poorly on Flathub that I would say that it doesn't work at all. Both with the featured apps slider thingy on the front page and on screenshots you have to hold the scroll wheel in position, and then it slowly moves, jaggedly. If you let go it snaps back. On the front page you seem to be able to do this as much as you like, but with the screenshots it only works once, and then even that stops working.
Screencast.from.2024-09-14.22-03-54.mp4
Expected behavior is that you just have to click sideways on the scroll wheel once to move to the next/previous item/screenshot.
Thanks for your great work! :)
The text was updated successfully, but these errors were encountered: