RESOLVED FIXED232123
First pointerdown event lost after context menu is triggered
https://bugs.webkit.org/show_bug.cgi?id=232123
Summary First pointerdown event lost after context menu is triggered
Andrew O
Reported 2021-10-21 18:02:57 PDT
Overview: Pointer down events in Safari fail after triggering a context menu Steps to Reproduce: I've created a simple test case here: https://jsfiddle.net/pyzt3wf1/1/ which consists of a single div with some standard UI event listeners (mousedown, mouseup, pointerdown, pointerup, click ). 1) Right click (or ctrl-click) anywhere in content area of the browser window on the linked example to trigger the browser's context menu. 2) Dismiss the context menu by clicking outside of it. 3) Click on the "click me" button to trigger that div's event listeners, which should trigger console logs viewable in either Safari's developer tools or within jsfiddle's built-in console, viewable by clicking ">_ Console(beta)" at the bottom of the preview frame. Actual Results: All of the events fire their respective callback, except for pointerdown. The console reads: mousedown pointerup mouseup click Subsequent clicks on the div appear to trigger events correctly. Expected Results: All of the events should fire their respective callback. The console should read: pointerdown mousedown pointerup mouseup click Date & Hardware: This bug has been reproduced on Safari 15.0 on both OS 10.15.7 and 11.6 . Similar behavior was experienced with Safari 14, although it hasn't been narrowed down to a reproducible case until now.
Attachments
Radar WebKit Bug Importer
Comment 1 2021-10-28 18:03:16 PDT
Franco Vieira de Souza
Comment 2 2025-09-18 14:52:04 PDT
Still valid. Here's another fiddle, as the original isn't available anymore: https://jsfiddle.net/97qk6cex/
Franco Vieira de Souza
Comment 3 2025-09-22 19:23:55 PDT
EWS
Comment 4 2025-09-29 08:50:49 PDT
Committed 300696@main (a19b08297f53): <https://commits.webkit.org/300696@main> Reviewed commits have been landed. Closing PR #51164 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.