- From: Masayuki Nakano via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 May 2025 04:36:36 +0000
- To: public-pointer-events@w3.org
@mustaqahmed Gecko/Firefox started dispatching `click` event on the preceding `pointerup` event target in nightly builds. However, [we got a compat issue for a single tap](https://bugzilla.mozilla.org/show_bug.cgi?id=1966569). The case is, there is a popup look list whose list items are `<a>` elements and the list is set to `style.display="none"` when `mousedown`. Therefore, the `click` target becomes an element under the `<a>` when user taps an item since the element at `pointerdown` implicitly captures the pointer and `pointerup` will be fired on the same target even after it's hidden. ([Here is a testcase.](https://jsfiddle.net/d_toybox/ctnvpxm3/3/)) However, this is not reproducible with Chrome because Chrome does not behave so for the `click` caused by a touch. So, Chrome does not treat the `userEvent` as the preceding `pointerup`. Could you clarify that it's a bug of Chrome or `userEvent` is the `touchend` or `mouseup` for Chrome? -- GitHub Notification of comment by masayuki-nakano Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/508#issuecomment-2885610632 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 May 2025 04:36:37 UTC