- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2016 23:05:32 +0000
- To: public-css-archive@w3.org
You do indeed model them all separately. Each element, based on its
laid-out position and its scroll-snap-align, contributes a [scroll
snap
position](https://drafts.csswg.org/css-scroll-snap/#scroll-snap-position)
- a particular scroll offset that it would like the scroller to
settle on.
Once you filter the elements you want to pay attention to (you don't
want to snap to things positioned way off-screen, as it would be
confusing), then you have a set of possible snap positions to pay
attention to. Then, based on the scroll offset the scroller would
*naturally* land on, you might choose one of the snap positions to
instead land on ("might" if it's proximity; "must" if it's mandatory).
The spec should define all of this. What parts did you find
incomplete or confusing?
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/780#issuecomment-264025329
using your GitHub account
Received on Wednesday, 30 November 2016 23:05:38 UTC