Open
Bug 1776624
Opened 2 years ago
Updated 2 years ago
Consider using mDestination as |aStartPos| argument for GetSnapPointForDestination in ScrollFrameHelper::ScrollSnap
Categories
(Core :: Layout: Scrolling and Overflow, task, P3)
Core
Layout: Scrolling and Overflow
Tracking
()
NEW
People
(Reporter: hiro, Unassigned)
References
Details
here, as of now we call GetSnapPointForDestination with GetScrollPosition() as |aStartPos|. All other call sites of GetSnapPointForDestination use mDestination, so if we can use mDestination in ScrollSnap() as well, we can refactor relevant functions as Botond suggested in a review comment.
To do this, we need to audit there's no case that ScrollSnap() gets called during async scroll is happening on the main-thread. Or we need to clarify it would be reasonable behavior change if there's such case.
You need to log in
before you can comment on or make changes to this bug.
Description
•