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

RE: [css-snappoints] Befine behaviour when content is larger than scroll container

From: Matt Rakow <marakow@microsoft.com>
Date: Wed, 8 Apr 2015 18:16:25 +0000
To: Guido Bouman <m@guido.vc>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <BY2PR03MB3611DD4E53D19B6C6DB88B4ADFC0@BY2PR03MB361.namprd03.prod.outlook.com>
Hi Guido,

Cool plugin! :)  Is this functionality your plugin provides that we could use to try it out?  I'm curious how this behavior would work when panning the opposite direction.

Thanks,
-Matt 

> From: Guido Bouman [mailto:m@guido.vc] 
> Sent: Wednesday, April 8, 2015 5:24 AM
> To: www-style@w3.org
> Subject: [css-snappoints] Befine behaviour when content is larger than scroll container
> 
> Hi all,
> 
> 
> Let me introduce myself first, as I think this is relevant for the issue I’m raising. I am the author of jQuery panelSnap (https://github.com/guidobouman/jquery-panelsnap). This CSS module would render my plugin obsolete, something I’m looking forward to, a lot.
> 
> There’s one issue that should be taken into account though: content that is larger than the scroll container.
> 
> With the current implementation this is not addressed. There should be a way to specify to only snap when there’s a snappoint in the visible area of the scroll container. I’m trying to describe something which feels in-between the current [mandatory] & [proximity] values for [scroll-snap-type]. It could be named [visible]. In this case [proximity] would be too loose, but [mandatory] too strict. You don’t want to change the behaviour of the current values, as they make a lot of sense in other situations. So adding a new one is my suggestion.
> 
> 
> Kind regards,
> Guido Bouman
> 
> +31 6 42945687
>
Received on Wednesday, 8 April 2015 18:16:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:30 UTC