Bug 1551801 Comment 12 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I did confirm that this issue is not a regression by the new scroll snap implementation. It also happened on Firefox 65. 

Now I think using un-negated velocity for pan-momentum is AsyncPanZoomController::ScrollSnapToDestination() is a reasonable way to fix this issue, and probably it will be able to be uplifted.   For long term, we might want a dedicated VelocityTracker for flick-ish operations, but I am not totally sure at this moment.
Revision 1 by
on 
I did confirm that this issue is not a regression by the new scroll snap implementation. It also happened on Firefox 65. 

Now I think using un-negated velocity for pan-momentum in AsyncPanZoomController::ScrollSnapToDestination() is a reasonable way to fix this issue, and probably it will be able to be uplifted.   For long term, we might want a dedicated VelocityTracker for flick-ish operations, but I am not totally sure at this moment.

Back to Bug 1551801 Comment 12