- From: François REMY <francois.remy.dev@outlook.com>
- Date: Fri, 30 Nov 2012 23:36:43 +0100
- To: "Sylvain Galineau" <sylvaing@microsoft.com>, "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "www-style list" <www-style@w3.org>
| [1] http://msdn.microsoft.com/en-us/library/windows/apps/hh453816.aspx For what it's worth, the "scroll-snap" property was something I was just going to say it was mandatory to get Tab's proposal working. Indeed, if you want to use animations as a scroll behavior for slides or an image carousel, you need to have snap points in order to get it to work. Florian spotted another sample where you want either to return to 0% to go up to 100%. So, I was going to argue that we had to standardize something like that first. Seems like I don't need to argue that anymore (I was wise to wait, I just spared a bunch of minutes of my time :D) and I can be happy with just saying "+1". BTW, I didn't knew the property existed at all in IE10, so that's maybe an under-advertized property. I did make one or two Windows 8 app in HTML/CSS, I would have loved to know this property existed. Some new homework for your IEBlog redactors ?-) | but we could and imo should | start with simpler, broadly usable solutions before moving on to more elaborate | effects where developers control every millisecond of what happens. +1 However, that doesn't mean Tab's proposal isn't worth it. To be honest, I see quite a number of places (slides transitions, carousel, animated cartoons ...) where it's critical for performance reasons. But, for all those cases, we need snap points first to get something that works properly. So, let's try to get snap points working first, and let's keep Tab's proposal for later. Anyway, I guess we're probably going to wait for WebAnims to specify better the concept of Timeline before introducing it in CSS.
Received on Friday, 30 November 2012 22:37:03 UTC