[Webkit-unassigned] [Bug 205446] New: Cross-frame pointer events lost when preventing default

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Dec 19 05:36:06 PST 2019


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

            Bug ID: 205446
           Summary: Cross-frame pointer events lost when preventing
                    default
           Product: WebKit
           Version: Safari 13
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ashley at scirra.com

Steps to reproduce:
1. Visit https://www.scirra.com/labs/bugs/pointer-frames/frame.html
2. Place a pointer down (using mouse on desktop or touch on mobile) inside the frame on the left, drag to the right outside the frame, and release
3. Observe the events printed in the frame

The frame should see either a pointerup event when releasing, or a pointercancel event when it loses the pointer. Both Firefox and EdgeHTML fire a pointerup event (but Chrome has the same bug).

Instead, the frame receives neither a pointerup or pointercancel event. In more complex web apps, this causes code that tracks pointers to get permanently stuck, since it will never see an event indicating the pointer ended.

This only happens when preventDefault() is called on the pointerdown event. However sometimes this has to be done for unrelated reasons. It should not cause a framed page to lose pointer events.

-- 
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/20191219/7f79f7b3/attachment.htm>


More information about the webkit-unassigned mailing list