- From: Adam Argyle via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Sep 2024 23:08:32 +0000
- To: public-css-archive@w3.org
> Do you have particular use cases for which you think that the current behavior on flings is better? i think almost all of [the examples](https://developer.chrome.com/blog/scroll-snap-events?hl=en#scrollable_ruler_input) are better with the current behavior, except *maybe* [the ruler](https://developer.chrome.com/blog/scroll-snap-events?hl=en#scrollable_ruler_input). > In my experience, I haven't seen websites or native applications where a fling predicts the destination beyond the next item. agree, me neither. but i also don't think that makes them better, but it does mean it's more familiar. `animation-timeline: view()` is maybe closer to what they're using too, instead of callbacks/triggers? [the ruler](https://developer.chrome.com/blog/scroll-snap-events?hl=en#scrollable_ruler_input) uses a combination of them, but does reserve the "current indicator" visual effect not scroll driven; i felt it made the UI selected item feedback stand out. > Maybe we could prototype whatever the most compelling use cases are and spot check / vote whether the current behavior or my proposed change is better or whether there are use cases for both? you know my feelings about prototypes! they can speak 1000 words. let's do it. > there are use cases for both i _think_ if i used `view()` and specified a small animation range that matched the axis area, i could listen for `animationend` on the snap items and simulate getting a callback like this `scrollSnapOverAxis` would add. also think IO could help us too, but be more manual work to isolate the intersection. **random thoughts** the unique aspects of this event is that it fires more eagerly than the other 2 events. it would also fire at the same rate as `scrollsnapchanging` for nearly all user interactions except a fling. it's the same as the others in that it'd be useful for scroll triggered animation, from either CSS or JS. last random thought, I wonder if folks would debounce or throttle this event because it was so eager? I feel like the current `scrollsnapchanging` event is modern in it's take, smarter and less wasteful, like an evolution that required "prediction" information which maybe wasn't available in older API implementations. -- GitHub Notification of comment by argyleink Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10838#issuecomment-2332838510 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 September 2024 23:08:33 UTC