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

flackr has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-scroll-snap-2] Why does scroll-start-target have separate block and inline values? ==
[css-scroll-snap-2 scroll-start-target](https://drafts.csswg.org/css-scroll-snap-2/#scroll-start-target) lets you define any element to be the starting position in either or both the block and inline axes. Does it ever make sense that you would want to scroll to one element in the block axis and a different one in the inline axis? Doing this could result in both of the targets not being visible, e.g.

```html
<style>
#a, #b {
  position: absolute;
}
#a {
  scroll-start: none auto;
  left: 300vw;
}
#b {
  scroll-start: auto none;
  top: 300vh;
}
<div id="a"></div>
<div id="b"></div>
```

The browser would scroll to (300vw, 300vh) resulting in neither element being in view.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8832 using your GitHub account


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

Received on Friday, 12 May 2023 13:29:35 UTC