[Webkit-unassigned] [Bug 203232] New: Touch events goes to document element when the original target is detached and preventDefault was called for previous event

[bugzilla-daemon at webkit.org]

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

            Bug ID: 203232
           Summary: Touch events goes to document element when the
                    original target is detached and preventDefault was
                    called for previous event
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: iPhone / iPad
                OS: iOS 13
            Status: NEW
          Severity: Major
          Priority: P2
         Component: UI Events
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: xidorn-webkit at upsuper.org

Created attachment 381505

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

testcase

Please see the attached testcase. In the testcase, there is a box keep detaching and attaching itself every two seconds. And there is an event handler on `touchmove` on document which logs a "D", and a handler on the box which logs "T".

Steps to reproduce:
1. when the box is there, press on the box and move the finger around
2. wait until the box disappears, and move the finger around

Expected result:
You should see TTTT being logged because the touch event should goes to where it starts (which is the box).

Actual result:
You would see DDD being logged because the touch event gets to the document element instead.


This behavior doesn't match the spec, and any other implementation.

Also this only happens when there is `e.preventDefault()`. If you remove that line, then it correctly logs TTTT indicating the events go to the box.

-- 
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/20191022/3bee234b/attachment.html>