- From: Mustaq Ahmed via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Jun 2023 21:03:28 +0000
- To: public-pointer-events@w3.org
Thanks @flackr for the discussion today, I agree with your conclusion above. The main takeaway for me is that even in the traditional MouseEvent world (without capturing), `click` as a high-level event is not tied to any single low-level event (i.e. `mousedown`, `mousemove` and `mouseup`), and its target is not affected by the effective position of the pointer implied by the boundary events (`mouseenter`, `mouseleave`, `mouseover` and `mouseout`). It is logical that the PointerEvents spec would extend this special targeting behavior to include Pointer Capture: the `click` target would be unaffected by the effective pointer target implied by `gotpointercapture` and `lostpointercapture` events for the same `pointerid`. This would make the click behavior more developer-friendly, and doesn't seem to pose any impl challenge even for asynchronous `click` from touch. And the compat question is irrelevant for obvious reasons. -- GitHub Notification of comment by mustaqahmed Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/356#issuecomment-1591981834 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 June 2023 21:03:30 UTC