- From: sb3nder via GitHub <noreply@w3.org>
- Date: Mon, 23 Feb 2026 17:53:41 +0000
- To: public-pointer-events@w3.org
The latest implementation in Chrome, behind a flag, does this: ``` pointerdown <DIV> SECTION:a:h DIV:a:h pointermove <DIV> SECTION:a:h DIV:a:h dragstart <DIV> SECTION:a:h DIV:a:h pointercancel <DIV> SECTION:a:h DIV:a:h pointerout <DIV> SECTION:a:h DIV:a:h pointerleave <DIV> SECTION:a:h DIV:a:h pointerleave <SECTION> SECTION:a:h DIV:a:h pointerleave <BODY> SECTION:a:h DIV:a:h pointerleave <HTML> SECTION:a:h DIV:a:h pointerleave <undefined> SECTION:a:h DIV:a:h pointerover <DIV> SECTION:a:h DIV:a:h pointerenter <undefined> SECTION:a:h DIV:a:h pointerenter <HTML> SECTION:a:h DIV:a:h pointerenter <BODY> SECTION:a:h DIV:a:h pointerenter <SECTION> SECTION:a:h DIV:a:h pointerenter <DIV> SECTION:a:h DIV:a:h dragenter <DIV> SECTION:a:h DIV:a:h ... dragend <DIV> pointerout <DIV> pointerleave <DIV> pointerleave <SECTION> pointerover <BODY> ... ``` To me, it looks like it's implemented in a way that allows `:active` and `:hover` to make sense from a pointer-events perspective, but it does not look particularly good, and probably does not make sense for `:active`. I wonder, if alignment between pointer events and `:active` and `:hover` states is really that important, could we come up with a better spec? -- GitHub Notification of comment by sb3nder Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/555#issuecomment-3946365618 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 February 2026 17:53:42 UTC