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

Re: [css-scroll-snap] "single mandatory"

From: Florian Rivoal <florian@rivoal.net>
Date: Tue, 24 Nov 2015 14:51:39 +0900
Cc: www-style list <www-style@w3.org>
Message-Id: <33161AD0-D64D-49E5-A7A6-BA711324475D@rivoal.net>
To: fantasai <fantasai.lists@inkedblade.net>

> On 24 Nov 2015, at 14:48, fantasai <fantasai.lists@inkedblade.net> wrote:
> 
> On 10/22/2015 04:05 AM, Florian Rivoal wrote:
>> This is an answer to issue 1 (https://drafts.csswg.org/css-scroll-snap/#issue-12d3b5df)
>> 
>> There is a suggestion that we may need a third value besides proximity and mandatory, to say something like: stop on the next snap point in the scrolling direction even if the user flinged so hard that inertial would normally take us past it.
>> 
>> I think this is a very useful distinction to make, but not as a third value. It should be a separate orthogonal property.
>> 
>> [.... examples etc. ....]
>> 
>> scroll-snap-stop: always | inertial
> 
> Fwiw, following the TPAC discussions, Tab and I added this suggestion to our proposal as
>  scroll-snap-stop: normal | always
> https://drafts.csswg.org/css-scroll-snap/#scroll-snap-stop

Looks good, thanks.

 - Florian
Received on Tuesday, 24 November 2015 05:52:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:29 UTC