- From: Gastón Rodríguez via GitHub <noreply@w3.org>
- Date: Tue, 14 Oct 2025 17:43:48 +0000
- To: public-pointer-events@w3.org
I think your interpretation regarding the order of events is correct and, if following the specs, the order of events should be: 1. `dragstart` on source node [per (9) in the DnD spec](https://html.spec.whatwg.org/multipage/dnd.html#drag-and-drop-processing-model:~:text=Fire%20a%20DND%20event%20named%20dragstart%20at%20the%20source%20node.) 2. Fire `pointercancel` on the source node and all the events required to suppress a pointer event stream per [(10) on the DnD spec](https://html.spec.whatwg.org/multipage/dnd.html#drag-and-drop-processing-model:~:text=Fire%20a%20pointer%20event%20at%20the%20source%20node%20named%20pointercancel%2C%20and%20fire%20any%20other%20follow%2Dup%20events%20as%20required%20by%20Pointer%20Events.%20%5BPOINTEREVENTS%5D). [Per the pointer events spec](https://w3c.github.io/pointerevents/#suppressing-a-pointer-event-stream), this includes: `pointerout` and `pointerleave`. The pointer events spec also specifically calls out the drag and drop scenario as a use case that calls for the events stream suppression. Could you please file a bug on chromium and assign it to me (gastonr@microsoft.com)? Thanks! I have no answer regarding the `:active` and `:hover` questions, hopefully someone will get back to you with that. -- GitHub Notification of comment by gastonrod Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/555#issuecomment-3402970393 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 October 2025 17:43:49 UTC