Accessibility issue: Disable (animating) overscroll
I want to disable overscroll. For those who don't know: it's the bouncy animation when you use scroll using a two-finger gesture past the beginning or end of a scrollable region.
The bouncing is an animation, and with animations disabled on my system, having this animation is an accessibility issue.
I guess I could split this question in two:
1. Can Mozilla please change Firefox so that it doesn't do this animation when animations are supposed to be disabled? 2. How can I disable this overscroll behaviour manually, separately from other animations?
Сви одговори (4)
Scrolling is not considered an animation. Disable overscrolling by going to about:config in the address bar and changing apz.overscroll.enabled to false.
> Scrolling is not considered an animation.
Speak for yourself, because *smooth* scrolling definitely is an animation, which is what it does, despite animation AND smooth scrolling both being disabled. Ask anyone suffering from motion sensitivity, and they'll agree that smooth scrolling is terrible to look at.
Thanks for the workaround though. But realistically people shouldn't have to dive into those settings for accessibility options.
Hi,
The people who answer questions here, for the most part, are other users volunteering their time (like me), not Mozilla employees or developers. If you want to leave feedback for developers, you can go to the Firefox Help menu and select Share ideas and feedback…. Alternatively, you can use this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.
You can also file a bug report or feature request. See File a bug report or feature request for Mozilla products for details.
> The people who answer questions here, for the most part, are other users volunteering their time (like me)
Sure thing, got it. But Mozilla devs are undoubtedly watching this. And if not, they bloody well should be.
But apart from that, surely it's not forbidden to express my discontent with a workaround? You might be taking this a little too personally, in which case, rest assured what I said is mostly directed at Mozilla devs.