- From: Masayuki Nakano via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jun 2024 07:52:33 +0000
- To: public-pointer-events@w3.org
> > > The note in that section implies (at least to me) that the userEvent is the PointerEvent (i.e. pointerup) whose default action caused the dispatch (excepting keyboard / accessibility means of dispatching clicks): > > > > > > If so, the `click` event target won't depend on `mouse` or `touch`, but both Chrome and Firefox dispatch it on wrong target, they dispatch `click` on the preceding `touchend` target which is same as `touchstart`'s. > > Is this not the same as the pointerup target? Note that touch usually has [implicit capture](https://w3c.github.io/pointerevents/#implicit-pointer-capture) so these would all be the same target AFAIK. No if `pointerdown` listener makes different element from `pointerdown`/`touchstart`/`touchend` target capture the pointer. [The expected result of line 192 of my test](https://github.com/web-platform-tests/wpt/blob/f18377726f412c270c3e3ed98c0b9f1c65ec2eac/pointerevents/pointerevent_click_during_parent_capture.html#L192) passed on Chrome and Firefox. -- GitHub Notification of comment by masayuki-nakano Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/508#issuecomment-2178002793 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 June 2024 07:52:34 UTC