- From: Bruno Stasse via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Mar 2021 14:33:22 +0000
- To: public-css-archive@w3.org
I think there are two elements which define the snapping mechanism: the easing curve and the duration of the snap, a bit like with CSS transitions (although the it is probably much more complex here because it has to take into account the momentum due to the scroll gesture). While it makes sense to allow browsers and OSs to have a specific easing curve which one shouldn't be able to opt out of, I don't think it makes sense for the duration of the snap. The "snap" effect is used in a lot of situations on mobile OSs, and the snap feeling is not always the same, because depending on the context it needs to be different. I have two situations in mind: - On iOS, on the home screen, the snapping between the different panels is quite fast, which allow to interact quickly with the panel after the snap; this is the same on macOS when switching between spaces. - On iOS, in the Apple Store app (an official Apple app), there is a carousel with your apple devices, and the snapping there is slower, and feels smoother. This is the same in a lot of other apps, like the carousel in the Facebook app. So we see different snapping mechanism on the same OS in native apps, and in the meantime with CSS scroll-snap we only have one mechanism, which vary in feeling between browsers and OSs, and therefore creates inconsistent experiences, and prevents certain use cases. If we can't have control over the easing curve, I think we should have some over the duration, and at least be offered choices, consistent across browsers and OSs. -- GitHub Notification of comment by brunostasse Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5464#issuecomment-801978250 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 March 2021 14:33:24 UTC