Index: chrome/common/automation_messages_internal.h |
diff --git a/chrome/common/automation_messages_internal.h b/chrome/common/automation_messages_internal.h |
index 83e2f7ff10f397c3e531b845a9ed1bbf9e3182df..561bd5da0abdd67f545433c29056e2eab8388c01 100644 |
--- a/chrome/common/automation_messages_internal.h |
+++ b/chrome/common/automation_messages_internal.h |
@@ -1522,6 +1522,10 @@ IPC_MESSAGE_ROUTED1(AutomationMsg_HeapProfilerDump, |
std::string /* reason */) |
#endif // !defined(NO_TCMALLOC) && (defined(OS_LINUX) || defined(OS_CHROMEOS)) |
+// Requests processing of the given mouse event. |
+IPC_MESSAGE_ROUTED1(AutomationMsg_ProcessMouseEvent, |
+ AutomationMouseEvent) |
dennis_jeffrey
2012/05/08 19:18:49
This will change the line numbers of the entries b
kkania
2012/05/09 18:19:59
Yes, this is ok.
|
+ |
// Renderer -> browser messages. |
// Sent as a response to |AutomationMsg_Snapshot|. |
@@ -1541,6 +1545,19 @@ IPC_MESSAGE_ROUTED2(AutomationMsg_WillPerformClientRedirect, |
IPC_MESSAGE_ROUTED1(AutomationMsg_DidCompleteOrCancelClientRedirect, |
int64 /* frame_id */) |
+// Sent right before processing a mouse event at the given point. |
+// This is needed in addition to AutomationMsg_ProcessMouseEventACK so that |
+// the client knows where the event occurred even if the event causes a modal |
+// dialog to appear which blocks further messages. |
+IPC_MESSAGE_ROUTED1(AutomationMsg_WillProcessMouseEventAt, |
+ gfx::Point) |
+ |
+// Sent when the automation mouse event has been processed. |
+IPC_MESSAGE_ROUTED2(AutomationMsg_ProcessMouseEventACK, |
+ bool /* success */, |
+ std::string /* error message */) |
+ |
dennis_jeffrey
2012/05/08 19:18:49
nit: remove this blank line
kkania
2012/05/09 18:19:59
Done.
|
+ |
// YOUR NEW MESSAGE MIGHT NOT BELONG HERE. |
// This is the section for renderer -> browser automation messages. If it is |
// an automation <-> browser message, put it above this section. The "no line |