- From: Simon Pieters via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Feb 2025 13:25:33 +0000
- To: public-css-archive@w3.org
> It's unclear to me what `scroll alignment` means here. `scroll-snap-align` is applicable only for `scroll snap container`s. So if the target scroll container's scroll-snap-type is `none`, it doesn't affect at all. Scroll alignment refers to the `block` and `inline` members in this PR. I think `scrollIntoView` should keep these, so that alignment can be controlled in cases where there is no scroll snap container, and so that it can be set to something else even if there is a scroll snap container (similar to how you can set `smooth` to override CSS). Also "nearest" is not covered by scroll snap AFAICT. When `block` or `inline` are undefined, it would make sense to use `scroll-snap-align` (if applicable) before using default values. Also see https://github.com/w3c/csswg-drafts/issues/4778 > > Whereas `scroll-margin` and `scroll-padding` are applicable as the names stand for. OK, they should probably be honored by `scrollIntoView()`. -- GitHub Notification of comment by zcorpan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/5677#issuecomment-2687959065 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 February 2025 13:25:34 UTC