Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: e17ecef9906f930f002bc0a85e246f1b62009551
https://github.com/WebKit/WebKit/commit/e17ecef9906f930f002bc0a85e246f1b62009551
Author: Simon Fraser <[email protected]>
Date: 2023-02-21 (Tue, 21 Feb 2023)
Changed paths:
M Source/WebKit/WebProcess/WebPage/EventDispatcher.cpp
M Source/WebKit/WebProcess/WebPage/MomentumEventDispatcher.cpp
M Source/WebKit/WebProcess/WebPage/MomentumEventDispatcher.h
Log Message:
-----------
Allow MomentumEventDispatcher's acceleration curve to be set in a thread safe
way
https://bugs.webkit.org/show_bug.cgi?id=252646
rdar://105710770
Reviewed by Tim Horton.
UI-side compositing will want to set MomentumEventDispatcher's
scrollingAccelerationCurve while another
thread is potentially reading it for the current gesture, so lock around
reading and writing the m_accelerationCurves.
Also remove the DisplayUpdate argument to displayWasRefreshed() since it's
unused.
* Source/WebKit/WebProcess/WebPage/EventDispatcher.cpp:
(WebKit::EventDispatcher::displayWasRefreshed):
* Source/WebKit/WebProcess/WebPage/MomentumEventDispatcher.cpp:
(WebKit::MomentumEventDispatcher::eventShouldStartSyntheticMomentumPhase const):
(WebKit::MomentumEventDispatcher::didStartMomentumPhase):
(WebKit::MomentumEventDispatcher::setScrollingAccelerationCurve):
(WebKit::MomentumEventDispatcher::scrollingAccelerationCurveForPage const):
(WebKit::MomentumEventDispatcher::displayWasRefreshed):
* Source/WebKit/WebProcess/WebPage/MomentumEventDispatcher.h:
Canonical link: https://commits.webkit.org/260617@main
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
