202287 2019-09-26 14:12:32 -0700 pointerdown events are not fired for clicks that follow a drag&drop. 2026-01-12 09:08:07 -0800 1 1 1 Unclassified WebKit UI Events Safari Technology Preview Mac macOS 10.14 NEW InRadar P2 Normal --- 1 aurelien_roy webkit-unassigned 7raivis alexreardon b.houdusse blesa bumblebee.zizka graouts hi jc.dafko jeroenwienk lvegerano422 rsnow seva webkit-bug-importer oldest_to_newest 1574623 0 aurelien_roy 2019-09-26 14:12:32 -0700 Bug confirmed on stable releases of : - Safari 13.0.0 / Mojave 10.14.6 - Safari 13.0.1 / Mojave 10.14.6 Overview : "pointerdown" events are not fired for clicks that follow a drag&drop. How to reproduce : - Add an event listener to a draggable DOM element for "pointerdown" event. - If you click on it, the event will fre. - Drag the element and release it. - The next time you will click on it, "pointerdown" event won't fire. - Following clicks will work again until the next drag&drop. Codepen : https://codepen.io/Tlokuus/pen/JjPVrLy This causes some commonly used JS libraries do not work propertly, for instance : https://github.com/SortableJS/Sortable/issues/1571 1574705 1 webkit-bug-importer 2019-09-26 19:53:04 -0700 <rdar://problem/55768441> 1575258 2 graouts 2019-09-30 08:06:45 -0700 The "mousedown" and "click" events are fired as expected, odd! 1575494 3 graouts 2019-10-01 04:40:14 -0700 We're actually dispatching a "pointermove" event instead of a "pointerdown" event because we believe the pointer is still pressed in PointerCaptureController::pointerEventForMouseEvent(): // We're already active and getting another mousedown, this means that we should dispatch // a pointermove event and let the button state show the newly depressed button. if (type == names.mousedownEvent && capturingData.pointerIsPressed) return PointerEvent::create(names.pointermoveEvent, button, mouseEvent); We must not clear the pointerIsPressed state during drag-and-drop. 1625122 4 lvegerano422 2020-03-03 10:38:54 -0800 Anyone knows the status of this bug? This is very alive in Safari 13.0.5 1679701 5 7raivis 2020-08-11 22:30:27 -0700 This bug is breaking compatibility to different libraries, for example https://github.com/SortableJS/Sortable/issues/1571 1705593 6 bumblebee.zizka 2020-11-08 10:43:58 -0800 This issue still persist even in Safari 14 Preview 1868456 7 rsnow 2022-05-12 10:04:14 -0700 Any status? this is still present in 15.4 and is causing us grief in our library react-aria 2013059 8 jc.dafko 2024-02-12 23:10:34 -0800 I am able to reproduce with v17.2.1 (19617.1.17.11.12). 2056770 9 blesa 2024-08-31 03:42:55 -0700 The bug is still there in 17.6 (19618.3.11.11.5) 2060613 10 alexreardon 2024-09-16 17:17:46 -0700 I raised a (duplicate) bug for this issue, not realising a bug report already existed: https://bugs.webkit.org/show_bug.cgi?id=279749 2062702 11 ahmad.saleem792 2024-09-24 03:32:38 -0700 *** Bug 279749 has been marked as a duplicate of this bug. *** 2145192 12 jeroenwienk 2025-09-23 03:38:08 -0700 Will this ever get fixed? It's been 6 years.