Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141)

Chrome didn't change the behavior in that case. Chrome always never fired click for the example mentioned in the comment. But we recently removed [an optimization](https://chromium.googlesource.com/chromium/src/+/1c12127b721f833f37b81553e19b8eb0392da651) to match the spec and other vendors regarding DOM mutation functions to actually remove and add element in some of the function calls like node.appendChild(node.lastChild) and that caused this difference in behavior to surface in more scenarios. As with that non-standard optimization we didn't actually remove the node and still sent the click event. But now without that optimization and with the removal of the node there will be no click.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/141#issuecomment-298708950