I have a trackpoint with no 3rd button. Many trackballs don't have scroll wheels. Many folks use arrow keys and space, shiftspace, pgup/down to navigate too and those require nice visible scroll bars that move the whole document to navigate effectively.

Long story short, stop fscking with accessibility. If your js code or libraries handles ANY input events, you'd better watch yourself because you're venturing into specialized-interface-by-and-for-assholes-land.

Things like large documents don't make that any easier though. Scrolling through a large document can take a while, but a scrollbar allows you to get to somewhere else often quite a lot faster.

Imagine you cmd + F a phrase and there are 200 responses separated into like 4 chunks of a document. It can be useful to scroll to the start of each chunk to get the context of them.

Most new mice, yes. I use an original Logitech MouseMan 3-button mouse with no scroll-wheel. I realize I'm an outlier, but no mouse has ever come close in terms of comfort for me - so I continue to use it, and life has been just fine until the advent of the Overlay Scroll Bar.

I realize the benefits of the Overlay Scroll Bar to the majority of users who have scroll-wheels. But it sure would be nice if there was an easy way to revert back to the Normal Scroll Bar ("Classic" scroll bar?). You know, the wide bar that scrolls down exactly one page-length if you click outside of the bar? I've spent plenty of time Googling and in "about:config" and exporting environment variables like GTK_OVERLAY_SCROLLING=0 to no avail.

Maybe with that change you can have it now by using a userscript that override scroll bar CSS for every site.

This assumption should be listed in the Firefox "System Requirements", then. I'm pretty sure nowhere else on my system (Mac) requires the mouse to have a wheel or tracking surface, or even a second button. Just x/y positioning, and clicking.

They do, but they don't eliminate the need for scrollbars that can actually be used.

> most

But not all.