W3C home > Mailing lists > Public > www-style@w3.org > June 2015

Re: : [css-snappoints] elements and nested scrollers

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 17 Jun 2015 09:34:47 +1200
Message-ID: <CAOp6jLZzKBtXWZF1qgXWznZyx-vbFAYyAN=HsO-mZhCNZhQwcA@mail.gmail.com>
To: Simon Fraser <smfr@me.com>
Cc: Majid Valipour <majidvp@chromium.org>, "www-style@w3.org list" <www-style@w3.org>
On Wed, Jun 17, 2015 at 6:12 AM, Simon Fraser <smfr@me.com> wrote:

> However, I think there’s one issue we need to decide soon. If we treat X
> and Y snap point lists as independent, even when using ‘elements’, then you
> can only ever have a complete grid of snap points (snap point at every
> intersection of an X value and a Y value). The spec isn’t totally clear,
> but it seems that the current behavior with scroll-snap-coordinates is that
> it allows a partial grid (set of specific X,Y coordinates based on element
> positions).
>
> The “partial grid” behavior is interesting, but problematic when
> scrolling: a vertical scroll could yank you sideways to go to nearby snap
> point. So I’m not sure we want to do this.
>

Yeah, I don't think that makes sense.

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 Tuesday, 16 June 2015 21:35:15 UTC

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