- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jun 2024 14:12:16 +0000
- To: public-pointer-events@w3.org
> Yeah, however, both Chrome and Firefox dispatch `click` event on the `#target` instead of `#parent` which is captured and is the target of `pointerup`. So, both browsers treat `userEvent` as the preceding `touchend` or `mouseup`. I believe if you try chrome with the `--enable-blink-features=BoundaryEventDispatchTracksNodeRemoval` flag that it will dispatch to the captured target of the pointerevent instead (code [here](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/input/pointer_event_manager.cc;l=1091;bpv=1;bpt=1?q=pointereventmanager)). @mustaqahmed I'm not sure why we have this change behind that flag, I thought this was a separate issue. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/508#issuecomment-2180813312 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 June 2024 14:12:16 UTC