W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

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

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 Jun 2018 19:06:11 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-395859053-1528484770-sysbot+gh@w3.org>
Related previous discussion was in https://drafts.csswg.org/css-scroll-snap/issues-by-issue#issue-45 fwiw.

Snapping in one axis and not the other was seen as important, and the main thing people would want to do--snapping in both axes is fairly awkward unless you're in a strictly gridded layout.

We didn't add per-axis strictness because we didn't have a use case that wanted mandatory in one axis and proximity in the other. But we did limit the syntax of the property so that we could add that in the future if there were use cases for it. (Usually keywords are re-orderable, but if we have per-axis strictness then there needs to be a fixed order.)

GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2728#issuecomment-395859053 using your GitHub account
Received on Friday, 8 June 2018 19:06:28 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 September 2019 01:18:58 UTC