Re: [w3c/uievents] Click event is not fired when the node is removed and then added back (#141) from Mustaq Ahmed on 2022-09-30 (public-webapps-github@w3.org from September 2022)

From: Mustaq Ahmed <notifications@github.com>
Date: Fri, 30 Sep 2022 13:39:36 -0700
To: w3c/uievents <uievents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/uievents/issues/141/1264003271@github.com>

Here is Chrome's argument for not firing a click: by definition, the "moved child" is not connected to DOM for a while (see ["Point 2" here](https://bugs.chromium.org/p/chromium/issues/detail?id=716694#c75)), therefore the ancestry info of the `mousedown` target is logically reset after the move, making the common ancestor undefined.

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

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

Received on Friday, 30 September 2022 20:39:49 UTC