Re: [csswg-drafts] [css-scroll-snap-2] Why does scroll-start-target have separate block and inline values? (#8832)

If the table had explicit `<col>` elements maybe we could scroll to the intersection of all `scroll-start-target`s - also giving an answer for how we handle multiple targets?

Also, I noticed that the spec says:
> If the second value is omitted, it defaults to [none](https://drafts.csswg.org/css-scroll-snap-2/#valdef-scroll-start-target-none).

This means that if a developer naively sets `scroll-start-target: auto` on some element it won't scroll into view in the inline axis, right? This seems surprising.

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


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

Received on Monday, 15 May 2023 17:06:03 UTC