Defer starting of animations until after compositing update

Source/core/page/PageAnimator.cpp

Index: Source/core/page/PageAnimator.cpp
diff --git a/Source/core/page/PageAnimator.cpp b/Source/core/page/PageAnimator.cpp
index 9e3c481193216d8ca058e4ac3af0612393284bf9..245e3a0be7f893ff45ca00106a3821644f40a49e 100644
--- a/Source/core/page/PageAnimator.cpp
+++ b/Source/core/page/PageAnimator.cpp
@@ -25,7 +25,8 @@ void PageAnimator::serviceScriptedAnimations(double monotonicAnimationStartTime)
 
     for (RefPtr<Frame> frame = m_page->mainFrame(); frame; frame = frame->tree().traverseNext()) {
         frame->view()->serviceScrollAnimations();
-        DocumentAnimations::serviceOnAnimationFrame(*frame->document(), monotonicAnimationStartTime);
+        DocumentAnimations::updateAnimationTimingForAnimationFrame(*frame->document(), monotonicAnimationStartTime);
+        DocumentAnimations::dispatchAnimationEvents(*frame->document());

[abarth-chromium, 2014/02/24 06:14:08]

Given that this function is dispatching events, don't we need to collect up the
RefPtr<Frame>s in a vector before walking them?  Scripts running below this call
stack can alter the frame tree, which can screw up the traversal.  (Feel free to
address this issue in a followup CL.)

[dstockwell, 2014/02/24 06:58:07]

Will do. Looks like we can use the same collection as below.

     }
 
     Vector<RefPtr<Document> > documents;