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

I do think that an end developer doesn't expect that performing an appendNode to move an item in DOM order amongst siblings (which is defined to do an adoptNode, which does a remove and then an insertion) a click event won't fire. 

The fundamental principle is that Chrome, Edge, and Safari all seem to listen to DOM mutations and if the node is removed from the document the click node is cleared.  Yet FireFox seems look at whether the node is connected to the document before firing the click.

@domenic
Can anyone think of any experiments we could run? To try to figure out the interop risk of actually making such a change? I presume Chrome could add a histogram that tracks the times we encounter this scenario (where the click node is cleared yet the clicked node is still attached to the document). Although I don't know how we'd assess any interop impact.


-- 
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-298918086