- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Sep 2024 17:30:53 +0000
- To: public-css-archive@w3.org
> > 4. They scroll by one "page" of scroll distance (e.g. similar to page up / down keys on the keyboard), which in most UA's is 85% of the scrollport size in the relevant axis but are adjusted by `scroll-padding`. > > Could it be configurable whether it scrolls one "page" or one snap point/area? I think there are use-cases for both. > > Also, when scrolling a fixed amount like 85% with scroll-snapping, an element that was partly obscured before scrolling can end up being partly scrolled out on the other side without ever being fully visible. This is especially frustrating when scrolling in the inline direction, as text can be cropped across lines, making it unreadable. In these cases, we've added code to ensure that only fully visible elements is scrolled out. Would it be possible to address this issue somehow? Do you have an example? The way that we avoid this issue for carousel experiences is by ensuring that we have appropriate snap areas. I.e. we will target scrolling 85% but given `scroll-snap-type: x mandatory` it will force it to align to the nearest snap area. I think that defining snap areas would be the recommended way to avoid the scroll resting between lines. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10722#issuecomment-2353509780 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 September 2024 17:30:54 UTC