[Webkit-unassigned] [Bug 82646] [chromium] Idle painting is not sufficient to pre-paint animated layers and delay animation start time

Fri Mar 30 18:36:33 PDT 2012

https://bugs.webkit.org/show_bug.cgi?id=82646

--- Comment #6 from Eric Penner <epenner at chromium.org>  2012-03-30 18:36:33 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > > 
> > > Either way, I expect that this will become a non-issue once he fixes the synchronization issues we're seeing when main thread commits. And if it's the way I think we'll fix it, then we will be far better off starting the animation as fast as possible and prepainting non-visible stuff to try catch up after the first commit.
> > 
> > Sounds like a great find! 
> > 
> > I'm pretty convinced this is still an issue based on the early experiment I did, but we can see how things pan out. As an example to illustrate why I'm still convinced we need to do some work upfront: I've seen some transitions where the work required (painting and uploads), takes 1.5x the length of the subsequent animation. I'll dig up a trace to illustrate further.
> 
> Hm, yes please!
> 
> I wonder what would happen if we didn't accelerate these animations. On the software path would they just not happen and the element jump to its destination?

Yes. But that's not to say it has to. Even the not threaded path could run faster if we did more work upfront.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.