Smooth scrolling has delay between mouse wheel movement and actual scrolling

UNCONFIRMED
Unassigned

Status

()

Firefox
General
UNCONFIRMED
3 years ago
8 months ago

People

(Reporter: aaroncohen73, Unassigned)

Tracking

43 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20150813030208

Steps to reproduce:

Turn smooth scrolling on
Scroll on a page using the mouse wheel


Actual results:

The page doesn't scroll immediately. Instead, it waits about a second before doing the scroll animation and moving the page. If the mouse wheel is moved more than one tick, the page moves slightly (Less than one scroll tick), waits about a second, then catches up to where it's supposed to be.


Expected results:

The page should scroll as the mouse wheel is being moved instead of having a delay.
(Reporter)

Comment 1

3 years ago
The scrolling delay isn't limited to pages. Dropdown boxes behave similarly with smooth scrolling on.
(Reporter)

Updated

3 years ago
Component: Untriaged → General
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64

Comment 2

a year ago
I can't reproduce this problem with Windows 7, but I can with Linux Mint 18.1 XFCE. The delay isn't as long as 1 second, but still very annoying, browsing large pages is a real pain.

Firefox 53.0 (64-bit) for Linux Mint 1.0.

Comment 3

8 months ago
opensuse 42.3 with Gnome desktop
linux 4.4.87-25-default x86_64
firefox 56.0.0

I do not have smooth scrolling enabled. Nevertheless I see the same delay between either the mouse wheel movement or moving the scroll bar, and the actual scrolling of the page. The delay is 1 - 2 seconds.

I do NOT see this behavior in v55.0,4 (or earlier), the version I am currently using since the delay in v56 is so annoying.

While the scroll is being delayed, I see the CPU usage for the thread jump to 100%. It would seem that FF.56 is doing something exceedingly inefficiently.
You need to log in before you can comment on or make changes to this bug.