Re: [pointerevents] Clarify `mousedown` event target if the preceding `pointerdown` event listener removes the target (#492)

Thanks @masayuki-nakano for filing this issue.  Wondering what UI Event spec says (or implies) about dispatching vs skipping click event in this case.  Let's continue the discussion here.

(To me, Chrome not firing click seems like a bug, btw.)

---

I wanted to clarify one thing about the WPT that brought up this discussion: [pointerevent_after_target_removed.html](https://wpt.fyi/results/pointerevents/pointerevent_after_target_removed.html%3Fmouse?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-events).

When the WPT was picked as an Interop 2023 goal last year, we didn't intent to cover interleaved pointer+mouse event dispatch.  Unfortunately, while addressing #377 and #380, we unintentionally added two sub-tests for the interleaved case instead of adding mouse-only sub-tests ([CL](https://chromium-review.googlesource.com/c/chromium/src/+/4854903/2/third_party/blink/web_tests/external/wpt/pointerevents/pointerevent_after_target_removed.html)).  We will correct the mistake now, and preserve the interleaved case as a tentative test for this issue.


-- 
GitHub Notification of comment by mustaqahmed
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/492#issuecomment-1799537944 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 7 November 2023 18:50:38 UTC