[Webkit-unassigned] [Bug 214141] New: touchend doesn't trigger on element when touch is released after touch motion
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jul 9 08:56:18 PDT 2020
https://bugs.webkit.org/show_bug.cgi?id=214141
Bug ID: 214141
Summary: touchend doesn't trigger on element when touch is
released after touch motion
Product: WebKit
Version: WebKit Local Build
Hardware: Unspecified
OS: Linux
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
touchend (and some corresponding events, see below) do not trigger on touch release right after a touch motion (scroll gesture). This seems to be the case because the wpe_input_touch_event_type_up does only end the gesture, but is not handled as a general touch event in this case.
backend: wpebackend-fdo-1.6.1
wpewebkit: 2.28.2 (tarball from https://wpewebkit.org/releases/)
browser: cog 0.7.1, qt-wpe-simple-browser 0.2
How to reproduce:
Visit https://patrickhlauke.github.io/touch/tests/event-listener.html, touch the button, move finger (while still touching) on button (or off button) and release touch.
Expected behavior:
touchstart
mouseover (15ms)
mouseenter (1ms)
mousedown (0ms)
mousemove (35ms)
touchmove (128ms)
touchmove (1ms)
touchend (8ms)
mouseup (10ms)
click (0ms)
mouseout
mouseleave (3ms)
Observed behavior:
touchstart
mouseover (15ms)
mouseenter (1ms)
mousedown (1ms)
mousemove (35ms)
touchmove (128ms)
touchmove (1ms)
Similar bugs:
- https://bugs.webkit.org/show_bug.cgi?id=202527
Proposed fix:
ScrollGestureController::handleEvent (Source/WebKit/UIProcess/API/wpe/ScrollGestureController.cpp) could always return false for wpe_input_touch_event_type_up cases. This way the wpe_input_touch_event_type_up would not only end the scroll gesture (Source/WebKit/UIProcess/API/wpe/WPEView.cpp) but also be processed as any other touch up event leading to correct touchend events in javascript. I am not sure whether this is really the desired fix though but it produces the desired output (as seen in "Expected behavior" above).
--
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/20200709/5cf31e0f/attachment.htm>
More information about the webkit-unassigned
mailing list