Open Bug 1825470 Opened 2 years ago Updated 2 years ago

Consider stop firing scroll events if the scroll position is unchanged during the scroll frame is reconstructed

Categories

(Core :: Layout: Scrolling and Overflow, defect, P3)

Product:
Core
Component:
Layout: Scrolling and Overflow
Type:
defect

Tracking

()

People

(Reporter: hiro, Unassigned)

References

Details

During reconstructing each scroll frame, we save the scroll position and restore the scroll position so that we can keep the scroll position unchanged. But unfortunately in the newly reconstructed scroll frame, this GetScrollPosition() in nsHTMLScrollFrame::ScrollToImpl returns (0, 0) so that we fire a scroll event for the restoring the scroll position. Theoretically it should be treated as unchanged scroll position, thus there should be no scroll event.

This is the root cause of bug 1777052 high frequent intermittent failure on test_mousecapture.xhtml.

That said, as far as I know of, there's no bug reports from users, so maybe some redundant scroll events don't matter in practice?

Summary: Consider stop firing scroll events → Consider stop firing scroll events if the scroll position is unchanged during the scroll frame is reconstructed
You need to log in before you can comment on or make changes to this bug.