- From: Florian Rivoal <florian@rivoal.net>
- Date: Thu, 29 Nov 2012 10:12:14 +0100
- To: www-style@w3.org
On Thu, 29 Nov 2012 02:36:33 +0100, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > Thoughts? Does anyone I haven't spoken to about this think it's > crazy? Would you like to see working examples (done with a JS shim, > of course) of the functionality? We haven't done any impl work yet, > but implementing this or something that solves the same problem is a > priority for the Chrome team in the next few months, so feedback > sooner rather than later would be great. There's one thing that I think would be useful, that seems to be missing. Say you're pulling a tray to open it. You might want to have a threshold point, say around 50%. When you releasse before the threshold, the tray falls back to 0, but if you release after it, it goes to the end. Notches aren't quite the same, as you need to get close by before they snap. You might be able to do it with accelerating momentum curves, but it sounds like a very roundabout way to go after it. Maybe a way to go after it would a property that let's you say something like: "if you release between 0% and 50%, switch to the (time based) animation called xxxx". That said, I don't know how this would interract with momentum, and how to handle the fact that someone may try to scrub again while the time-based animation started by the release has kicked in. Maybe another way would be to address the usecase more directly than with ranges mapping to other named animations, and instead define gravity centers, with affected ranges. when you're scrubbing, ignore them, when you release, if you're in an affected range, fall towards the center. - Florian
Received on Thursday, 29 November 2012 09:09:15 UTC