Re: [csswg-drafts] [css-scroll-snap-2] How should competing scroll-start-targets be resolved? (#10774)

I thought of a possible option that would support a lot of the 2d cases fairly simply. We could scroll to every specified item in order, then if you combine this with `nearest` behavior it will try to scroll to a position that includes all of the specified elements. Elements that are wider than the viewport (e.g. scrolling to a row in a table) won't move the horizontal position as its already fully in view and thus implicitly supports the scrolling to a specific row and column use case.

I also wonder if we should consider re-using `scroll-snap-align` for this. We already use `scroll-margin` and `scroll-padding` to affect scrolling behaviors beyond snapping, it seems reasonable that we may want a `scroll-align` which affects the alignment used for anchor scrolls or other scrolls even when not using scroll snapping.

-- 
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10774#issuecomment-2313551599 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 27 August 2024 21:08:49 UTC