[Webkit-unassigned] [Bug 211521] New: AX: REGRESSION (iOS 13.4.1): Issues on touchstart/touchend/touchmove (pointerdown/pointerup/pointermove) events

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 6 11:26:09 PDT 2020


            Bug ID: 211521
           Summary: AX: REGRESSION (iOS 13.4.1): Issues on
                    (pointerdown/pointerup/pointermove) events
           Product: WebKit
           Version: Safari 13
          Hardware: All
                OS: All
            Status: NEW
          Severity: Critical
          Priority: P2
         Component: UI Events
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: juwagn at gmail.com


on latest iOS update 13.4.1 with Safari the bug with fast touch sequences came back once it was fixed on 2019-11-14, but now exactly same bug is back again!
In the similar ticket number 203786 the bug link contains already full description.
That breaks behavior of our software totally compared as example to Android browsers since touchstart/touchend gets detected in sequence, and by fast sequence when it gets detected as dblclick then touchstart and touchend stay unfired!
That can't be replaced by dblclick since in this sequence i need to move finger after non-fired touchstart event but since on new Safari it gets not reported the functionality gets broken.
There is in fact no need to create extra reproducer case since issue is reproducible always, touch the screen fast two times in sequence and only one event gets fired instead expected two.
Is there any chance to return back this functionality? Or at least register specific new event name that would be fired regardless of dblclick detection where i could recognize that finger was touched/untouched or moved while being fast touched two times in sequence?
I just did not expect that same issue would come back after being reported and fixed already!

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.

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/20200506/de373ef7/attachment.htm>

More information about the webkit-unassigned mailing list