Prepare for Unified Gesture Recognizer landing in Aura

content/common/input/synthetic_web_input_event_builders.cc

Index: content/common/input/synthetic_web_input_event_builders.cc
diff --git a/content/common/input/synthetic_web_input_event_builders.cc b/content/common/input/synthetic_web_input_event_builders.cc
index 2fcca34afb73bc9878c14511225ca545da3b58ef..4582e28c3fa0ef6d9c07ff20300cb47582377bba 100644
--- a/content/common/input/synthetic_web_input_event_builders.cc
+++ b/content/common/input/synthetic_web_input_event_builders.cc
@@ -147,7 +147,9 @@ WebGestureEvent SyntheticWebGestureEventBuilder::BuildFling(
   return result;
 }
 
-SyntheticWebTouchEvent::SyntheticWebTouchEvent() : WebTouchEvent() {}

[jdduke (slow), 2014/05/30 15:04:54]

I am curious what test failures this was causing... is it because the gesture
detector runs on ack'ed events with Aura, rather than the source events? 

[tdresser, 2014/05/30 16:04:06]

    TouchInputBrowserTest.MultiPointTouchPress
    TouchInputBrowserTest.TouchHandlerConsume
    TouchInputBrowserTest.TouchHandlerNoConsume

You're right - this should stop being an issue when we switch to being eager.

+SyntheticWebTouchEvent::SyntheticWebTouchEvent() : WebTouchEvent() {
+  SetTimestamp(base::TimeTicks::Now() - base::TimeTicks());
+}
 
 void SyntheticWebTouchEvent::ResetPoints() {
   int point = 0;