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 00:59:57 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-511250173-1563152396-sysbot+gh@w3.org>
@justingrant I feel as though you don’t realize that scroll containers load in on the “scrollmin” position in the first place? So what’s a scenario you can imagine where the initial scroll position should not be reachable after scrolling? You refer to “empty space” but there can be content in the “space” that just hasn’t declared a choosable/reachable snap alignment based upon the size of the snapport, content, and aligned edge? Have you scrolled the original posts test case?

> But I think the "fix" could just match the blink behavior where scrolls are not allowed to escape the first/last snap-aligned child element. 

I don’t think you’re realizing that the load in scroll position is “escaped” from what you propose, on top of being hostile towards users.

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

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