- From: Dan Robertson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Aug 2023 20:20:46 +0000
- To: public-css-archive@w3.org
> But, at what point does the UA determine that scrolling is completed? If it's not done in "run the scroll steps", the spec may fire scrollend first and scroll afterwards. Or, if "scrolling is completed" happens in parallel (off-main-thread), then the spec says to fire an event in a situation where would instead have to queue an event to fire the event (which the spec doesn't say to do). Similar to what is stated here, what is the expected behavior given a user scrolling with a mousewheel in a scenario where smooth scroll is disabled. Currently Firefox fires a scrollend event as soon as the mousewheel scroll completes, which results in many `scrollend` events for a series of mousewheel scrolls. Simple tests with chrome seem to indicate that scrollend events are a bit more aggressively coalesced. -- GitHub Notification of comment by dlrobertson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8396#issuecomment-1690583824 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 August 2023 20:20:48 UTC