Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Scrolling "Area" is too small.

  • 3 respostas
  • 1 tem este problema
  • 1 visualização
  • Última resposta por imgraftedin

more options

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.

Solução escolhida

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

Ler esta resposta no contexto 👍 0

Todas as respostas (3)

more options

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.

more options

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".

more options

Solução escolhida

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