Bug 203786 - REGRESSION (iOS 13): Issues on touchstart/touchend/touchmove (pointerdown/pointerup/pointermove) events
Summary: REGRESSION (iOS 13): Issues on touchstart/touchend/touchmove (pointerdown/poi...
Status: REOPENED
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: Safari 13
Hardware: iPhone / iPad iOS 13
: P2 Blocker
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-11-02 11:58 PDT by juwagn
Modified: 2021-12-01 17:17 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description juwagn 2019-11-02 11:58:12 PDT
The touch sequence: finger touch > finger release > finger touch > finger move > finger release, where last 3 event types get not reported to event handling. 
On earlier iOS versions like iOS12 the sequence above fired following events:
1. touchstart
2. touchend 
3. touchstart (in fast sequence to previous touchend)
4. touchmove
5. touchend (when moving ended)

On new iOS 13 versions on tested iPad only first two
1. touchstart
2. touchend 
3. ---- not fired> touchstart  (in fast sequence to previous touchend) 
4. ---- not fired> touchmove
5. ---- not fired> touchend 
In such case not event dblclick gets fired.

Unfortunatelly unreported "dbl-touch and move" breaks functionality of our software. Pointer events have same issue like touch events, they are not propagated to DOM if detected by iOS as potential dblclick even if moved between.
Comment 1 Radar WebKit Bug Importer 2019-11-03 10:24:10 PST
<rdar://problem/56849729>
Comment 2 juwagn 2019-11-14 17:23:49 PST
Hello, 

the bug seems to be fixed in iOS 13.2.2 released on 2019-11-07
Pretty fast released, great work!
Comment 3 juwagn 2020-05-06 12:05:54 PDT
Bug is back again with iOS 13.4.1
https://bugs.webkit.org/show_bug.cgi?id=211521