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

flackr left a comment (w3c/uievents#141)

I agree, this doesn't make sense if they're changing the contents of an ancestor with a click listener. E.g. consider if the structure of a button is changed in a react render routine:

https://jsbin.com/cizifoj/edit?html,js,output

Clicking on the text doesn't dispatch a click event but conceptually the button was still clicked. We should track the ancestor of the removed node for determining the click target in these cases.

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

Message ID: <w3c/uievents/issues/141/3366391897@github.com>