Add SyntheticPointerActionParams used in Chromedriver extension

content/common/input_messages.h

Index: content/common/input_messages.h
diff --git a/content/common/input_messages.h b/content/common/input_messages.h
index 7f05b9f9d7600da7bd300905bdc0c0388fcd7d4a..117f18f4cb7953edb554aa0785dd52ab1a8ff281 100644
--- a/content/common/input_messages.h
+++ b/content/common/input_messages.h
@@ -105,6 +105,14 @@ IPC_STRUCT_TRAITS_BEGIN(content::SyntheticTapGestureParams)
   IPC_STRUCT_TRAITS_MEMBER(duration_ms)
 IPC_STRUCT_TRAITS_END()
 
+IPC_STRUCT_TRAITS_BEGIN(content::SyntheticPointerActionParams)
+  IPC_STRUCT_TRAITS_PARENT(content::SyntheticGestureParams)
+  IPC_STRUCT_TRAITS_MEMBER(position)
+  IPC_STRUCT_TRAITS_MEMBER(duration_ms)
+  IPC_STRUCT_TRAITS_MEMBER(index)
+  IPC_STRUCT_TRAITS_MEMBER(pointer_action_type)
+IPC_STRUCT_TRAITS_END()

[samuong, 2016/02/17 22:15:48]

When we do a press, we need to pass the touch id back to the caller via the
completion callback. I guess this requires a change to one of the other packets
here?

[lanwei, 2016/02/26 18:39:26]

We do not need to pass the index back to the chromedriver_extension, we will
keep the index on the browser side. When the chromedriver send the actions to
browser, they will be always on the same order on fingers, so the browser will
keep the map function to map the index to the action orders.

+
 IPC_STRUCT_TRAITS_BEGIN(content::InputEventAck)
   IPC_STRUCT_TRAITS_MEMBER(type)
   IPC_STRUCT_TRAITS_MEMBER(state)