Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: a19b08297f53de5702b7aa7878843c40bfc08e9e
https://github.com/WebKit/WebKit/commit/a19b08297f53de5702b7aa7878843c40bfc08e9e
Author: Franco Vieira de Souza <[email protected]>
Date: 2025-09-29 (Mon, 29 Sep 2025)
Changed paths:
M LayoutTests/TestExpectations
M
LayoutTests/imported/w3c/web-platform-tests/event-timing/interactionid-aux-pointerdown-and-pointerdown-expected.txt
M
LayoutTests/imported/w3c/web-platform-tests/event-timing/interactionid-aux-pointerdown-expected.txt
M LayoutTests/platform/gtk/TestExpectations
M LayoutTests/platform/win/TestExpectations
M LayoutTests/platform/wpe/TestExpectations
M Source/WebCore/page/PointerCaptureController.cpp
M Source/WebCore/page/PointerCaptureController.h
M Source/WebKit/WebProcess/WebPage/WebContextMenu.cpp
M Source/WebKit/WebProcess/WebPage/WebContextMenu.h
M Source/WebKit/WebProcess/WebPage/WebFrame.cpp
Log Message:
-----------
First pointerdown event lost after context menu is triggered
https://bugs.webkit.org/show_bug.cgi?id=232123
rdar://84787733
Reviewed by Lily Spiniolas and Abrar Rahman Protyasha.
We now explicitly do some cleanup on PointerCaptureController when
showing a contextmenu due right-click. This is required because the
events are not processed while the contextmenu is open, causing the
mousedown that opens the contextmenu to not have a matching mouseup.
The lack of a matching mouseup used to result in one later mousedown
being interpreted as part of a mouse button chord, causing
PointerCaptureController::pointerEventForMouseEvent() to produce a
pointermove instead of a pointerdown.
Canonical link: https://commits.webkit.org/300696@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
