Bug 203786
| Summary: | REGRESSION (iOS 13): Issues on touchstart/touchend/touchmove (pointerdown/pointerup/pointermove) events | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | juwagn <juwagn> |
| Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
| Status: | REOPENED | ||
| Severity: | Blocker | CC: | graouts, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 13 | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 13 | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=233636 | ||
juwagn
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/56849729>
juwagn
Hello,
the bug seems to be fixed in iOS 13.2.2 released on 2019-11-07
Pretty fast released, great work!
juwagn
Bug is back again with iOS 13.4.1
https://bugs.webkit.org/show_bug.cgi?id=211521