- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Aug 2018 18:17:50 +0000
- To: public-css-archive@w3.org
Yes, initial load counts. The scroll position is *always* governed by snapping rules, unless you are currently in the middle of a scrolling operation. That said, putting a mandatory snap point at the bottom is probably bad, as it means you can't scroll upwards! (Putting a *proximity* one there is a good idea tho, as it helps you when scroll close to it, and "sticks" you to the bottom as new content gets added.) The correct way to handle this is with `align-content`, as specified in [Align 3](https://drafts.csswg.org/css-align/#overflow-scroll-position); `overflow-y: scroll; align-content: end;` should start the element out scrolled to the bottom. This isn't *generally* implemented yet, but it happens to work already in Chrome in the specific case of of a `flex-flow: column-reverse` flexbox. ^_^ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3014#issuecomment-412614496 using your GitHub account
Received on Monday, 13 August 2018 18:17:51 UTC