- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2023 14:07:29 +0000
- To: public-css-archive@w3.org
> Could you elaborate a little on the proposal for `scroll-align`'s syntax: why is the first option needed given that `scroll-snap-align` will override `scroll-align`? Or are there cases where it would/should not override? The `normal` option allows you to specify an alignment for scroll targeting operations (e.g. linked to an element or `scroll-start` without making the element a snap point. Technically we don't need that if we still have scroll-snap-align as a separate property but it's a bit awkward to have two properties attempting to determine the `scroll-align` alignment. By making `scroll-align` capable of handling snap alignment, `scroll-snap-align` becomes an alias for setting `scroll-align` and internally we only need to track the `scroll-align` value. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9012#issuecomment-1757774549 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 October 2023 14:07:30 UTC