- From: Adam Argyle via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Dec 2022 17:48:03 +0000
- To: public-css-archive@w3.org
I feel like keeping `scrollend` "simple" in that it fires after `scroll` when there's no more translations or user input happening. if the scroll is requested to a new location, but it happens its the current location, there was no `scroll` so no `scrollend` event. It feels much more appropriate for the `scrollTo` functions to provide a callback or promise that the request was fulfilled, regardless of whether scroll actually occurred. the problem space of this issue seems to be "it's hard to know that no scrolling occurred after programmatic assignment" and I think that problem lives at a higher level than `scrollend`, aka it's not `scrollend`'s responsibility to remedy it. i do agree this is a real issue though and scroll api's should offer ways to reduce this mystery. -- GitHub Notification of comment by argyleink Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8218#issuecomment-1349267299 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 December 2022 17:48:05 UTC