Re: Request for Comments: Proposal for Touch-Based Animation Scrubbing

|  Hold it; what do you define as 'normal'? The normal case for most web 
pages
|  does not tie animations to scrolling.

Yes, this is what I meant for 'normal'. I did read complaints that 
implementing something like this may slow down normal pages scrolling. This 
is not true: this is an opt-in so this is certainly not going to slow down 
normal pages.



|  I, for one, don't buy it would be sufficiently better to scale to what
|  devs will do once creating such animations is easy.

May or may not be true. This is difficult to assess so I'm not going to 
enter this discussion.



|  My bigger concern is that there are far more important scenarios to 
address
|  right now. Making Facebook's momentum scrolling better, for instance, 
impacts
|  far more users than enabling Beercamp-style scrolling stunts (however 
cool I
|  may find them).

Yes, I agree. Actually, my priority would be on adding Staged Layout to CSS 
as soon as possible so I'm not against working on that before (this is 
actually one of the three things I'm particulary going to give my support to 
this coming year, alongside CSS Custom Properties and Layout Events). I was 
just reacting to the comments saying that Tab's proposal would make the 
scrolling experience worse, which is not true. In the worst case, the 
scrolling experience stays the same.

Anyway, the Web Anims group will define the 'animation-timeline' property 
sooner rather than later for other purposes (like syncing an animation to a 
media element) and once it will be done, creating a scroll-based timeline is 
something Google will be able to do on their own pretty quickly (and I'm 
sure they will). So, my advice would be to solve the 'root use cases' now, 
this will come in a natural way once it's done.

Received on Sunday, 2 December 2012 13:30:30 UTC