- From: Masayuki Nakano via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Jun 2024 00:16:04 +0000
- To: public-pointer-events@w3.org
masayuki-nakano has just created a new issue for https://github.com/w3c/pointerevents: == Clarify (or override) `dblclick` event target == Pointer Events [defines](https://w3c.github.io/pointerevents/#event-dispatch) the event target of `click`, `auxclick` and `contextmenu` as same as `userEvent` which is fired by user's operation. So, this means that the event target may be different from the definition in UI Events because UI Events [defines](https://w3c.github.io/uievents/#event-type-dblclick) the event target of `dblclick` as: > the event target MUST be the same between [mousedown](https://w3c.github.io/uievents/#mousedown), [mouseup](https://w3c.github.io/uievents/#mouseup), and [dblclick](https://w3c.github.io/uievents/#dblclick). However, Pointer Events does not override `dblclick` event interface and does not mention it. Therefore, in the edge cases, `click` event target and `dblclick` event target may be different. I think that it is not developer-friendly. It must cause web-compat issues if browsers do not work exactly same as current odd and implicit definitions. I think that Pointer Events should mention about `dblclick` event target at least since `mousedown` and `mouseup` may be prevented by a `pointerdown` event handler. I hope, the `dblclick` event target should be same as the preceding `click` and there should be WPTs. Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/507 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 June 2024 00:16:06 UTC