[csswg-drafts] [css-scroll-snap] By design, why does scroll-snap-type disallow per axis strictness?

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

== [css-scroll-snap] By design, why does scroll-snap-type disallow per axis strictness? ==
https://drafts.csswg.org/css-scroll-snap-1/#scroll-snap-type

Before bringing up this issue, I ran my quandary by blink implementors ([comment](https://bugs.chromium.org/p/chromium/issues/detail?id=826416#c6)).

I can see how the syntax was designed to infer `none` in the opposing axis of setting snapping/strictness as well as the ability to set both axes to the same strictness, but a snapping scroller, per spec, doesn't allow per axis strictness.

Even if this may not have a lot of use cases, while playing with the feature on a large scrolling table, I found this limitation undesirable, wishing I could set the strictness of the `block` axis to `mandatory` and `inline` to `proximity`.

I'm guessing this was a by-product of not creating per axis longhand properties for both logical and physical `scroll-snap-type`, like we are now dealing with for properties like `overflow`?

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

Received on Thursday, 31 May 2018 23:56:39 UTC