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

@mustaqahmed Thank you.

> 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.

Thanks. And if somebody is still writing the patch, I'd like you guys to split the assertion to multiple ones like [this test](https://searchfox.org/mozilla-central/rev/fe8b30e982c86d26ccf1f14d825c0de870b91f27/testing/web-platform/tests/uievents/mouse/synthetic-mouse-enter-leave-over-out-button-state-after-target-removed.tentative.html#120-173)? The assertions check too many things. Therefore, it takes long time to understand the result and the investigation result requires big tables when we comment the result in issues.

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


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

Received on Monday, 13 November 2023 01:35:11 UTC