Re: [pointerevents] Clarify what the target of the click event should be after capturing pointer events (#356)

Just realized that the Chrome behavior mentioned in https://github.com/w3c/pointerevents/issues/356#issuecomment-811814819 is only for mouse pointers!  For touch pointers, the `click` is dispatched asynchronously (to be able to distinguish `click` on tap vs `auxclick` on long-tap) after both `pointerup` and `lostpointercapture` has been dispatched, fully matching Firefox!

And this behavior has been there since we (Chrome) shipped PointerEvents!

---

We never got a chance to report the counter data we added a while ago (https://github.com/w3c/pointerevents/issues/356#issuecomment-863263903).  Expecting to report back in a week.

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


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

Received on Wednesday, 13 April 2022 16:17:00 UTC