- From: David A via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Mar 2025 14:34:10 +0000
- To: public-css-archive@w3.org
Hm, I guess in theory since the update in the momentum event is entirely external to the UA (I think?), if the UA believes momentum events are still incoming, it's reasonable that it behaves as if there are still pending updates. But my hunch is that in practice these momentum updates cannot suddenly change direction so if you reach the edge, you know there will be no more updates so you can send scrollend - that actually seems more correct to me. Seems to me that if an author wants, for example, to load more content if the user hits the edge and is relying on scrollend, waiting for the noop momentum events before sending scrollend would be a worse experience. -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11973#issuecomment-2743551675 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 March 2025 14:34:11 UTC