Open Bug 1423534 Opened 7 years ago Updated 6 months ago

The positioning of elements is choppy & staggered when positioned with the scroll event


(Core :: Layout, defect, P3)

57 Branch





(Reporter: sathish_gx, Unassigned)



(3 files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171129231020

Steps to reproduce: This website uses scroll based positioning of images to create a parallax effect. Basically the images are moved up/down at a different rate(as opposed to the normal rate) when scrolled creating a parallax effect.

Actual results:

I've noticed the positioning of elements when tied to scroll event  is very choppy in the new Quantum Firefox. After the upgrade to Quantum the elements which gets positioned on scroll is very choppy. This was not the case in the old Firefox as well as current chrome and every other browser.

Also when you scroll using the scroll bar there is no choppiness. Only when using the scroll wheel on the mouse this issue occurs.

Now here is the weird thing which further hints this is a firefox issue. When you open the "Developer Tools" and scroll, the choppiness disappears. When you close the developer tools and scroll, the choppiness returns.

I may be wrong but maybe when the developers were coding quantum I think the code responsible for smooth CSS positioning of elements on scroll event(with smooth scrolling enabled) was taken out or messed up? Could Firefox look into this issue soon. Thanks

Expected results:

The should be no choppy & staggered scroll on elements positioned with the scroll event. It should be smooth like the old Firefox and Chrome.
Summary: The scrolling is choppy & staggered on elements positioned on scroll event → The positioning of elements is choppy & staggered when positioned with the scroll event
Component: Untriaged → Layout
Product: Firefox → Core
Priority: -- → P1
Priority: P1 → P3
Severity: normal → S3
Attached file Firefox 57.0
Attached file choppy & staggered
Attached file further hints

Thanks a lot! I was now able to solve the same problem on the website.

You need to log in before you can comment on or make changes to this bug.