Why dblclick silently fails when a click handler replaces the DOM element

A web developer discovered that double-click events never fire when a click handler replaces the target DOM element, with no console errors to signal the problem. Testing across Chromium 148, Firefox 150, and WebKit 26.4 confirmed that all three browsers drop the dblclick event if the second click lands on a newly created node rather than the original one. Crucially, the issue is about node identity — removing and reinserting the same object works fine, but swapping in a new node with identical markup does not. The dblclick also does not bubble up to parent elements, so attaching a listener higher in the DOM tree offers no escape. A reliable cross-browser fix is to check the click event's detail property inside the click handler, since detail correctly reaches 2 on the second click regardless of whether the target node was replaced.