- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2023 01:06:10 +0000
- To: public-css-archive@w3.org
I'm pretty strongly against more arbitrary control over fling curves; every single site that does customized scrolling that doesn't match the my OS's default fling physics is deeply unsettling to interact with, personally. This probably applies to things like letting people choose a friction amount, especially since there's no intuition for how it works so it'll just be a random number that feels right to the dev at the time, and totally inconsistent across sites. (In particular, I consider the [Google Search request](https://bugs.chromium.org/p/chromium/issues/detail?id=1420772) to be an **active anti-goal**. "Consistent experience across OSes and devices" is another way of saying "wrong physics on every device and OS (*maybe* matching the one OS/device the dev happens to use and like)". Users want physics to be consistent across different pages/apps on their device, because it's something you build muscle memory for; a single page being different from other pages, but consistent across different devices, has literally zero benefit for users and significant downsides, imo.) But having a little more control over how far a fling is meant to go over stops sounds reasonable! Especially with nice semantic names that appear to be meaningful, like the item/page/document you have here. Is this meant to interact with scroll-snap-stop? Like, `item` would be the default and give the current stop `scroll-snap-stop:always` behavior, while the other values loosen it a bit? Or were you thinking about something else? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8549#issuecomment-1461108153 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 01:06:12 UTC