[Webkit-unassigned] [Bug 251925] New: [WPE] Compatibility mapping with mouse events use too naive target node detection

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=251925

            Bug ID: 251925
           Summary: [WPE] Compatibility mapping with mouse events use too
                    naive target node detection
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WPE WebKit
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: bst at pengutronix.de
                CC: bugs-noreply at webkitgtk.org, cgarcia at igalia.com,
                    zdobersek at igalia.com

Created attachment 464907

  --> https://bugs.webkit.org/attachment.cgi?id=464907&action=review

Demo: Touch compatibility mapping with mouse events trigger on wrong element

WPE sends mouse motion/down/up in PageClientImpl::doneWithTouchEvent() for touches as compatibility mapping with mouse events [1]. Instead of reusing the target node (result of the hit test) from the touch events, completely new synthetic input events are created that rely solely on the X/Y coordinates of the touch event (see TouchGestureController::EventVariant()). Since all of this happens after the touch gesture is done, the new hit test triggered by the synthetic input events can be a different target node (i.e. if the DOM changes under the touch point as a result of the touchstart event). This again can lead to events on wrong elements.

See attachment for a demo.

This also affects the contextmenu handling in https://bugs.webkit.org/show_bug.cgi?id=248076 because it imitates the click handling.


[1] https://www.w3.org/TR/pointerevents/#compatibility-mapping-with-mouse-events

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230208/e44e6213/attachment-0001.htm>