W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2019

Re: [csswg-drafts] [css-scroll-snap-1] Compat between webkit and blink/gecko regarding "implicit" scroll boundary snap positions (#4037)

From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
Date: Mon, 15 Jul 2019 14:57:13 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-511437568-1563202632-sysbot+gh@w3.org>
> While we're talking test cases, have you scrolled the top list on https://codesandbox.io/s/happy-architecture-m7pn5 on Safari?

Yes, in webkit as well as blink. I find the behavior for the third scroller strange in both. Both seem broken. Neither seems to tell a user that something is going all that well. Which I imagine is simply a byproduct of pigeon-holing virtualization into scroll-snapping.

Since I am guessing the use of a simple `overflow: scroll` is immensely more common than virtualized scrolling, even with all the github stars, I think the default behavior shouldn’t cater to the needs of virtualized scrolling.

As far as scroll-snapping behavior for content that is programmatically curated like what happens with virtualized scrolling, I have found that writing scroll/touch handlers on top of pointer events or things like hammer.js and the `transform` serves those gestures far better. I’ve written variations of those handlers many times and find better perf than what I’m seeing in https://codesandbox.io/s/happy-architecture-m7pn5.

> Yep, understood. Was using "empty space" as a shorthand for something like "no reachable snap-aligned elements" because I was assuming that "no elements" would be the most common reason.

I think with responsive scroll containers and content “no elements” wouldn’t be the common reason as much as the element that defines the nearest scroll boundary alignment is attempting to align to the opposite edge of the scroll boundary, but is too large. Also, if the first piece of content has a margin on that start boundary you’re then asking to rework the other stylings to account for `scroll-margin` or putting a pseudo element in to add in an extra “scrollmin” alignment? You might be thinking of scroll-snap in the limited scope of uniform lists, but it has many more uses.

-- 
GitHub Notification of comment by jonjohnjohnson
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4037#issuecomment-511437568 using your GitHub account
Received on Monday, 15 July 2019 14:57:15 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:50 UTC