Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo
Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.
Oplost Argivearre

Scrolling "Area" is too small.

imgraftedin

I used to be able to grab the scroll bar with my mouse, click and drag up in any direction....even across the browser and it would keep scrolling. Now if I get more than about 75 or 100 pixels to the left it stops scrolling and snaps back to the previous position. One I click I should be able to drag in any direction and it should scroll at a speed relative to the angle I'm dragging away. A more vertical angle should be faster and a more horizontal should be slower.

I used to be able to grab the scroll bar with my mouse, click and drag up in any direction....even across the browser and it would keep scrolling. Now if I get more than about 75 or 100 pixels to the left it stops scrolling and snaps back to the previous position. One I click I should be able to drag in any direction and it should scroll at a speed relative to the angle I'm dragging away. A more vertical angle should be faster and a more horizontal should be slower.
Dit antwurd yn kontekst lêze

Keazen oplossing

After playing some more I realized that this is not a firefox problem but a microsoft problem.

Alle antwurden (3)

Do you have the setting called 'widget.non-native-theme.scrollbar.size' when you navigate to about:config? Increase this to maybe 100 and hit enter. Then, refresh the page. It works for me.

Sounds that you are talking about auto-scrolling that you initiate by clicking the mouse wheel in free space (i.e. not an active area or link) on the webpage. You can find this setting in "Settings -> General -> Browsing -> Use autoscrolling".

Keazen oplossing

After playing some more I realized that this is not a firefox problem but a microsoft problem.