You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[UI-side compositing] Ensure that wheel events got to the web process for JS event handlers
https://bugs.webkit.org/show_bug.cgi?id=248846
Reviewed by Tim Horton.
Override `eventListenerRegionTypesForPoint()` in RemoteScrollingTreeMac just as we do in ScrollingTreeMac
to get the event handler details for a given point. We use this to know if we have to continue with the
web process/main thread event handling path.
* Source/WebKit/UIProcess/RemoteLayerTree/mac/RemoteScrollingTreeMac.h:
* Source/WebKit/UIProcess/RemoteLayerTree/mac/RemoteScrollingTreeMac.mm:
(WebKit::eventRegionForLayer):
(WebKit::layerEventRegionContainsPoint):
(WebKit::RemoteScrollingTreeMac::eventListenerRegionTypesForPoint const):
Canonical link: https://commits.webkit.org/257531@main
// Scrolling changes boundsOrigin on the scroll container layer, but we computed its event region ignoring scroll position, so factor out bounds origin.
0 commit comments