- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2023 15:20:09 +0000
- To: public-css-archive@w3.org
I guess it depends what you mean by loosen it up a bit. I was thinking that it would be closer to the experiment I did in [crbug.com/1189696](https://bugs.chromium.org/p/chromium/issues/detail?id=1189696) where the browser can determine more appropriate fling distances. The goal there was to make the average fling distance about a page but if the user flings fast they can still fling further. I was initially thinking this should just be the default but have since come to realize this behavior only makes sense for itemized list scrollers and not something like snap points added to spec sections. That said, my exact proposal of changing the "average" (specific fling modification to be determined by the browser) distance would mean that you'd either use this new property (which is like a less strict `scroll-snap-stop`) or `scroll-snap-stop` but it would be interesting to think if there are ways to make the two properties work together in meaningful ways. E.g. maybe if this is like a stop at the next mandatory item after x pages of scrolling then we could do the velocity modifications in chrome similar to the [crbug.com/1189696](https://bugs.chromium.org/p/chromium/issues/detail?id=1189696) when you're in such a scroller because we know that you only meaningfully need to differentiate between the next N snap points and not scroll further. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8549#issuecomment-1462237303 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 March 2023 15:20:11 UTC