[pointerevents] Click event is not fired when the node is removed and then added back (#576)

NavidZ has just created a new issue for https://github.com/w3c/pointerevents:

== Click event is not fired when the node is removed and then added back ==
Looking at [this example note](https://w3c.github.io/uievents/#example-60eb6b28) in the spec it is not very explicit what should happen when a node is removed and then added back in the mousedown handler and we don't have any wpt test for it either. [This example](http://jsbin.com/tepihex/edit?html,js,console) shows the behavior.
Particularly it seems that Edge, Safari, and the latest version of Chrome don't send the click event but they do send both mousedown and up events to that element. FireFox however does send click event in that scenario.
I can see that spec is implying that the click/dblclick events should not be sent to the node if it gets removed regardless of whether it gets added back or not. But it might not be very clear. 
@garykac @smaug---- @patrickkettner what do you think?

Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/576 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 12 January 2026 22:01:12 UTC