W3C home > Mailing lists > Public > www-style@w3.org > October 2014

Re: [css-snappoints] 10/24 Snap points draft update

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 28 Oct 2014 00:01:28 +1300
Message-ID: <CAOp6jLa7Z6sgjz8nmng0sOVxEWJ3y7AWrhyhRd8FmGOe10PyFg@mail.gmail.com>
To: Matt Rakow <marakow@microsoft.com>
Cc: "www-style@w3.org" <www-style@w3.org>
Thanks.

I think it would be helpful for the spec to define in one place what the
behavior of scroll snapping is. Right now text says "The visual viewport of
this scroll container is guaranteed to rest on a snap point when there are
no active scrolling operations." and in another place
"scroll-snap-destination" modifies this. We should be able to describe
precisely in CSS terms what invariant holds when there are no active
scrolling operations, in terms of the CSSOM scroll position.

This would also be a good place to define edge case behavior. AFAICT right
now it's undefined what happens if there no snappoints, or more
specifically if there are no snappoints that can be snapped to by scrolling
within the normally allowed scroll range.

The only allowed syntax for scroll-snap-points-x/y is 'repeat(<length>)'.
In particular there is no 'none' or equivalent. Is that an oversight? How
would zero or negative lengths behave here?

Can we call 'scroll-snap-coordinate' 'scroll-snap-target'?

Rob
-- 
oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo
owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo
osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo
owohooo
osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o
oioso
oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo
owohooo
osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro
ooofo
otohoeo ofoioroeo ooofo ohoeololo.
Received on Monday, 27 October 2014 11:01:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:47 UTC