CC::Animations should use TimeTicks & TimeDelta to represent time

cc/layers/layer.cc

 // Copyright 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "cc/layers/layer.h"
 
 #include <algorithm>
 
 #include "base/debug/trace_event.h"
 #include "base/location.h"
@@ skipping 1100 matching lines @@
     return false;
 
   UMA_HISTOGRAM_BOOLEAN("Renderer.AnimationAddedToOrphanLayer",
                         !layer_tree_host_);
   layer_animation_controller_->AddAnimation(animation.Pass());
   SetNeedsCommit();
   return true;
 }
 
 void Layer::PauseAnimation(int animation_id, double time_offset) {
-  layer_animation_controller_->PauseAnimation(animation_id, time_offset);
+  layer_animation_controller_->PauseAnimation(
+      animation_id,
+      base::TimeTicks::FromInternalValue(time_offset *

[danakj, 2014/04/09 16:34:15]

Is converting back and forth from double to time ticks going to cause
jitter/error in the time value? Can we change the PauseAnimation method to
TimeTicks here or is that later?

[Sikugu_, 2014/04/10 14:04:57]

Keeping this as it is to avoid jitter.
Will take care of this in the Animaitons patch.

+                                         base::Time::kMicrosecondsPerSecond));
   SetNeedsCommit();
 }
 
 void Layer::RemoveAnimation(int animation_id) {
   layer_animation_controller_->RemoveAnimation(animation_id);
   SetNeedsCommit();
 }
 
 void Layer::SetLayerAnimationControllerForTest(
     scoped_refptr<LayerAnimationController> controller) {
@@ skipping 58 matching lines @@
   if (clip_parent_)
     clip_parent_->RemoveClipChild(this);
 
   clip_parent_ = NULL;
 }
 
 void Layer::RunMicroBenchmark(MicroBenchmark* benchmark) {
   benchmark->RunOnLayer(this);
 }
 }  // namespace cc