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

RE: [css-snappoints] 3/5 Updated ED

From: Matt Rakow <marakow@microsoft.com>
Date: Tue, 10 Mar 2015 19:05:22 +0000
To: Simon Fraser <smfr@me.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <BY2PR03MB36123BE1EC6C22F1504EA31AD180@BY2PR03MB361.namprd03.prod.outlook.com>
Yes, snapping to elements is still possible.

The previous design required the elements keyword to be used to "activate" the element snap points, otherwise they had no effect.  This was done to ensure mutual exclusivity between element snap points, snap interval, and snap list syntax.

Feedback from the WG was that the mutual exclusivity seemed like an arbitrary restriction, so it was removed.  Without this restriction there's no more need for the elements keyword -- setting a scroll-snap-coordinate implicitly "activates" the snap point.


> From: Simon Fraser [mailto:smfr@me.com] 
> Sent: Monday, March 9, 2015 12:34 PM
> To: Matt Rakow
> Cc: www-style@w3.org
> Subject: Re: [css-snappoints] 3/5 Updated ED
> On Mar 5, 2014, at 10:00 AM, Matt Rakow <marakow@microsoft.com> wrote:
> Hi all,
> Updates since my last mail include:
> Enabling the multiple scroll-snap-coordinate per element scenario via comma-separated list of space-separated pairs (feedback from Seattle f2f)
> Eliminating the snap-list and snap-interval functions in favor of a comma-separated list and repeat() syntax (Tab’s feedback from Seattle f2f and mail)
> Updated grammar notation as specified in CSS Values and Units L3
> We just noticed something about this spec update (a year later!).
> r10112 removed the “elements” keyword for the scroll-snap-points-* properties, yet the spec still defines scroll-snap-coordinate, which suggests that snapping to element is still possible. But how is it achieved?
> Simon
Received on Tuesday, 10 March 2015 19:05:50 UTC

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