Refactor Timer classes in preparation for landing FrameTimers.

third_party/WebKit/Source/core/layout/ImageQualityController.h

Index: third_party/WebKit/Source/core/layout/ImageQualityController.h
diff --git a/third_party/WebKit/Source/core/layout/ImageQualityController.h b/third_party/WebKit/Source/core/layout/ImageQualityController.h
index d6636b7d3f9ae9a5600c2aa8e5d317de5e6865a8..3feab63e1a7bda03b65649a165268cf96c8eefdc 100644
--- a/third_party/WebKit/Source/core/layout/ImageQualityController.h
+++ b/third_party/WebKit/Source/core/layout/ImageQualityController.h
@@ -77,14 +77,14 @@ private:
     void objectDestroyed(const LayoutObject&);
     bool isEmpty() { return m_objectLayerSizeMap.isEmpty(); }
 
-    void highQualityRepaintTimerFired(Timer<ImageQualityController>*);
+    void highQualityRepaintTimerFired(TimerBase*);
     void restartTimer(double lastFrameTimeMonotonic);
 
     // Only for use in testing.
-    void setTimer(Timer<ImageQualityController>*);
+    void setTimer(TaskRunnerTimer<ImageQualityController>*);

[dcheng, 2016/07/28 13:09:51]

Do we have a better way to mock out timers for tests with the new scheduling
stuff? This is pretty ugly.

[haraken, 2016/07/28 14:44:46]

Yeah, this looks ugly. Can we make MockTimer inherit from TimerBase and make
setTimer take a |TimerBase*| parameter?

[dcheng, 2016/07/29 02:23:18]

Hmm, the more I think about, I think that Timer should just not be templated
(and use WTF::bind() internally to capture the timer task).

I suppose making it a TimerBase won't hurt for now though, so done.

 
     ObjectLayerSizeMap m_objectLayerSizeMap;
-    std::unique_ptr<Timer<ImageQualityController>> m_timer;
+    std::unique_ptr<TaskRunnerTimer<ImageQualityController>> m_timer;
     double m_frameTimeWhenTimerStarted;
 
     // For calling set().