- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Sun, 12 Apr 2026 20:36:36 +0000
- To: public-css-archive@w3.org
The way this works in chrome is all of the events (i.e. scroll and scrollend) are already enqueued before we start dispatching. This is why even if you start scrolling in response it doesn't prevent the scrollend from being dispatched - since it technically ended before you received the scroll event. IMO this is expected since per spec scroll events are added to a queue and dispatched later. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13772#issuecomment-4232698982 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 12 April 2026 20:36:37 UTC