- From: sb3nder via GitHub <noreply@w3.org>
- Date: Thu, 16 Oct 2025 01:03:30 +0000
- To: public-pointer-events@w3.org
Re events order, here are the filed bugs: https://issues.chromium.org/issues/452372355 https://bugzilla.mozilla.org/show_bug.cgi?id=1994552 --- Re active/hover states: Firefox behavior is a bit puzzling, it's possible to start a drag by double-tapping. In that case, only `:hover` applies. But if `touch-action: none` is set, both `:hover` and `:active` apply, and `:active` is not maintained after the DnD. I've looked around a bit on CodePen to see how `:active` is typically used in drag-and-drop scenarios. From what I’ve seen, it’s actually quite rare to see `:active` used directly for this purpose. At first, I thought it might be related to the `cursor` property, but that doesn’t seem to be the case, as `cursor` is ignored during DnD interactions. In the JS-based implementations I’ve looked at, it seems like relying on `:active` for visual feedback during dragging would cause more issues than it solves, since many of them use a dedicated class and style to indicate that an element is being dragged, so that it avoids overlapping `:hover` or `:active` styles. -- GitHub Notification of comment by sb3nder Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/555#issuecomment-3408773785 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 October 2025 01:03:31 UTC