Add SyntheticPointerActionParams used in Chromedriver extension

content/common/input/synthetic_gesture_params.h

Index: content/common/input/synthetic_gesture_params.h
diff --git a/content/common/input/synthetic_gesture_params.h b/content/common/input/synthetic_gesture_params.h
index 1c40ca98fd2a025e0d3898110e5b4bda6e1c9bb0..46e5926c8c6931febbbc14a1bf10ae5e1ceb04c5 100644
--- a/content/common/input/synthetic_gesture_params.h
+++ b/content/common/input/synthetic_gesture_params.h
@@ -48,8 +48,21 @@ struct CONTENT_EXPORT SyntheticGestureParams {
     SMOOTH_DRAG_GESTURE,
     PINCH_GESTURE,
     TAP_GESTURE,
-    SYNTHETIC_GESTURE_TYPE_MAX = TAP_GESTURE
+    POINTER_ACTION,
+    SYNTHETIC_GESTURE_TYPE_MAX = POINTER_ACTION
   };
+
+  // When we send actions one by one, once we receive a PROCESS action, we will
+  // start to dispatch a event with all the pending actions.
+  enum class PointerActionType {

[tdresser, 2016/03/17 18:25:29]

Should this be In SyntheticPointerAction or SyntheticPointerActionParams?

[tdresser, 2016/03/22 14:38:10]

Sorry! It would make more sense if this lived in SyntheticPointerAction...

+    PRESS,
+    MOVE,
+    RELEASE,
+    DELAY,

[tdresser, 2016/03/17 18:25:29]

If we aren't going to have a test that uses DELAY, we should probably just get
rid of it for now. Feel free to remove it, or add a test.

Is the plan to send one DELAY per frame for now, and then add a framecount
later? If so, if we're leaving DELAY in, we should have a comment with a TODO
indicating that this is the plan.

If we're removing DELAY, we should have a comment with a TODO indicating that at
some point we'll be adding it in.

[lanwei, 2016/03/22 00:33:43]

Yes, the current plan is to send one delay per frame, the framecount is in the
chromedriver_extension. I will remove the delay for now, add it if we change the
design.

+    PROCESS,
+    POINTER_ACTION_TYPE_MAX = PROCESS
+  };
+
   virtual GestureType GetGestureType() const = 0;
 
   // Returns true if the specific gesture source type is supported on this