- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Jul 2024 20:40:32 +0000
- To: public-pointer-events@w3.org
@masayuki-nakano I missed the discussion above! To clarify, the Chrome flag `BoundaryEventDispatchTracksNodeRemoval` is not related to `click`-like events at all! This flag controls only the dispatch of boundary (`enter`, `leave`, `over` and `out`) events after a DOM modification (tested through the WPTs [/pointerevents/pointerevent_after_target*](https://wpt.fyi/results/pointerevents?label=master&label=experimental&aligned&q=%2Fpointerevents%2Fpointerevent_after_target)). Regarding your original discussion around `userEvent`: Chrome has bugs with click-like event's targets with pointer-capture. [This bug](https://issues.chromium.org/40851596) is for mouse pointers, and we are planning to fix this as part of Interop 2024. The behavior is tested through the WPT [pointerevent_click_during_capture.html](https://wpt.fyi/results/pointerevents?label=master&label=experimental&aligned&q=pointerevents%2Fpointerevent_click_during_capture.html). I suspect we may have similar bugs with touch-pointers. Since the definition of `userEvent` is perhaps causing the confusion here, please consider sending a PR to the spec to clarify it. Do we need to add a note to the single sentence defining this (Step 1 in 4.2.12.3)? This is meant to be the "low-level" event that caused the firing of a "click"-like event, regardless of the target of either event. -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/508#issuecomment-2237535488 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 July 2024 20:40:32 UTC