Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 2808f5b4f299d92496145faa85f15d69a16eca49
https://github.com/WebKit/WebKit/commit/2808f5b4f299d92496145faa85f15d69a16eca49
Author: Tim Horton <[email protected]>
Date: 2026-10-08 (Thu, 08 Oct 2026)
Changed paths:
M Source/WebKit/UIProcess/mac/AppKitGestures/WKAppKitGestureController.mm
M Tools/TestWebKitAPI/Tests/WebKit/WebPage/AppKit Gesture
Tests/BasicAppKitGesturesTests.swift
Log Message:
-----------
[AppKit Gestures] Scrolling can get stucked latched to a scroller that's not
under the mouse
https://bugs.webkit.org/show_bug.cgi?id=326757
rdar://188241847
Reviewed by Abrar Rahman Protyasha.
Test: Tools/TestWebKitAPI/Tests/WebKit/WebPage/AppKit Gesture
Tests/BasicAppKitGesturesTests.swift
* Source/WebKit/UIProcess/mac/AppKitGestures/WKAppKitGestureController.mm:
(-[WKAppKitGestureController sendWheelEventForGesture:]):
Make sure to send a MayBegin event at the beginning of a gesture, in order to
reset latching state.
Otherwise, for scrolls where the tail of momentum events don't make it to the
web content process,
we can get stuck latched to the wrong scroller and continue dispatching events
somewhere very distant
from the mouse. This matches what we get in the non-gesture case.
* Tools/TestWebKitAPI/Tests/WebKit/WebPage/AppKit Gesture
Tests/BasicAppKitGesturesTests.swift:
(PointerEventFamily.scrollAfterMomentumScrollTargetsElementUnderNewGesture):
Add a test that ensures that scrolling doesn't get stuck mis-latched.
Canonical link: https://commits.webkit.org/323076@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
