- From: Emilio Cobos Álvarez via GitHub <noreply@w3.org>
- Date: Sat, 11 Apr 2026 09:03:09 +0000
- To: public-css-archive@w3.org
Personally, I think the way I'd fix this would be: 1. The scroll event queue should be snapshotted before dispatching scroll events, just like the `requestAnimationFrame` behavior. This alone gets the Chromium behavior. 1. Additionally, we could add a check when dispatching the `scrollend` event like "if there's a pending scroll event for this node, return", to get the Safari behavior. I don't feel too strongly about the Safari vs. Chromium behavior, tho. We can choose which one we want by adding or removing (2). -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13772#issuecomment-4229153863 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 11 April 2026 09:03:10 UTC