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

Re: [css-scroll-snap] Splitting scroll-snap-type, shorthanding on scroll container

From: Sebastian Zartner <sebastianzartner@gmail.com>
Date: Tue, 15 Dec 2015 08:44:48 +0100
Message-ID: <CAERejNbkDuWrqrgGsYd0hVABUxW6ymGBYhk97w1AGg9Uvis7rQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On 15 December 2015 at 00:26, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Sun, Dec 13, 2015 at 1:31 PM, Sebastian Zartner
> <sebastianzartner@gmail.com> wrote:
>> On 9 December 2015 at 19:36, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>>> On Tue, Dec 8, 2015 at 5:05 AM, Sebastian Zartner
>>> <sebastianzartner@gmail.com> wrote:
>>> > To me the difference between the 'both' and 'point' values is not
>>> > clear yet, or more precisely the difference between two 1D snap
>>> > positions vs. one 2D snap position.
>>> > So assuming those values could be removed, the property could also be
>>> > split up in two, one for each axis. So we'd have
>>> > 'scroll-snap-type-block' and 'scroll-snap-type-inline'.
>>> I'd love to know what we could improve in
>>> <https://drafts.csswg.org/css-scroll-snap/#snap-dimensions> to make
>>> this clearer.  They can't be merged, as they do two rather different
>>> things.
>> Examples explaining the differences would help.
>> For the description and the examples given for 2D snap positions I'd
>> imagine having two 1D snap positions for each axis to work the same.
>> After rereading the spec. I guess what is actually meant is 'axis
>> snapping' vs. 'point snapping'. The difference would be that for axis
>> snapping the scroll snapping can happen along the whole *axis*, while
>> for point snapping it can only happen at that specific *point*. If
>> that's the case, I suggest to rename 1D snap positions and 2D snap
>> positions accordingly to clarify that difference.
> As far as I can tell, that's what we wrote in the linked section?  The
> note in the 1D section is pretty explicit about the difference between
> 2D and double-1D: double-1D can horizontally snap to one element, but
> vertically snap to a different element entirely, while 2d snapping
> always snap both axises to a single element.

At least for me it is not clear enough. At least mentioning the word
'point' within the 2D snap position section could clarify things a bit
more. Also, as mentioned before, code samples and/or drawings showing
the differences would make it more obvious.

Received on Tuesday, 15 December 2015 07:45:38 UTC

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