Scrolling using mouse wheel doesn't work at all 109.2
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
People
(Reporter: ontwerper, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
scroll with mousewheel
Actual results:
Nothing
Expected results:
Page moving up or down
(I use v108 now because I reverted to it using windows recovery)
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Panning and Zooming' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•2 years ago
|
||
Marc, thanks for reporting this bug. Can you please try to use https://mozilla.github.io/mozregression/ to identify which changeset in 109 caused this issue? Thanks!
As far as I can see scrolling doesn't work in any of the 109 builds. I am not sure how to determine the data range by date though. Can't seem to test between releases that way (108 to 109). But while at it I encountered the same problem in the 108 nightlies and tracked down the regression to this:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a8858873d38b456a3d1bd82f7737edc1fa4296b9&tochange=3525211fa094b4b009f13ff44e654b95822accf0
I did find out that pressing down the mouse wheel to scroll by floating the cursor does still work (I never use that).
|
||
Comment 4•2 years ago
|
||
Sounds like you are hitting bug 1798014. Do you have some software that might affect mouse handling? xbmc? X-Mouse control?
Yes X-mouse control. I assigned the Home and End button to my mouse
Ok I updated to 109.3 and had the same problem. about:config security.sandbox.gpu.level has defaulted to 1. I set it to 0, now scrolling works again.
|
||
Comment 7•2 years ago
|
||
Marc, this one: https://joelpurra.com/projects/X-Mouse_Controls/?
|
|
||
Comment 9•2 years ago
|
||
Ok, you can install beta version and it has a fix. See bug 1805618 comment 2
|
|
||
Comment 10•2 years ago
|
||
Making this as a dup of bug 1798014 based on comment 8.
Description
•