W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

[csswg-drafts] [css-scroll-snap] More granular control over scroll-snap-stop (#5467)

From: Johannes Odland via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Aug 2020 06:08:29 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-685201823-1598335708-sysbot+gh@w3.org>
johannesodland has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-scroll-snap] More granular control over scroll-snap-stop ==
The ``scroll-snap-stop`` property currently supports two values, either ``normal`` or ``always``. (https://drafts.csswg.org/css-scroll-snap-1/#scroll-snap-stop)

In a scroll container with many snap positions this has the following effects:
- normal: It's easy to scrub through the container to get to any part, but it's easy to miss a snap position without noticing.
- always: It's really hard to scroll through the container, but the user does not miss a single snap position.

When using scroll snap for longer scroll containers the author has to choose between these two extremes. A more granular approach could give more control to the author. I.e. a property called ``scroll-snap-strength`` where a value of 0 equals ``normal`` and 1 equals ``always``.

As the underlying used for snapping is left for the UA to decide ``strength`` might not be the best word for this property. The intention is to give more granular control than the two extremes that are specced today.

Example scroll snapping article: 

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 August 2020 06:08:31 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC