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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Oct 24 15:59:21 PDT 2019


--- Comment #4 from Xidorn Quan <xidorn-webkit at upsuper.org> ---
> As far as I know, our implementation of touch events isn't meant to match any particular specification. You say there's a behavior change between iOS 12 and 13 and that's worth investigating.

I think the touch events behavior is covered by Touch Events spec https://www.w3.org/TR/touch-events/#the-touchmove-event which stats:
>  The target of this event must be the same Element on which the touch point started when it was first placed on the surface, ...

which matches all other browsers as well as iOS 12.

> We now implement Pointer Events. Do you see similar behavior with Pointer Events?

I haven't tried yet, and I'm not quite familiar with Pointer Events, but will have a look.

Actually I was a bit surprised that you decided to implement Pointer Events, as I thought WebKit was publicly against this.

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/20191024/064e5dc6/attachment.htm>

More information about the webkit-unassigned mailing list