Delete Automation[Tab/Renderer]Helper and users.

chrome/common/automation_messages_internal.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Defines the IPC messages used by the automation interface.
 
 // NOTE: All IPC messages have either a routing_id of 0 (for asynchronous
 //       messages), or one that's been assigned by the proxy (for calls
 //       which expect a response).  The routing_id shouldn't be used for
 //       any other purpose in these message types.
 
 // NOTE: All the new IPC messages should go at the end.
 //       The test <--> browser IPC message IDs need to match the reference
 //       builds.  Since we now define the IDs based on __LINE__, to allow these
 //       IPC messages to be used to control an old version of Chrome we need
 //       the message IDs to remain the same.  This means that you should not
-//       change the line number of these types of messages. You can, however,
-//       change the browser <--> renderer messages.
+//       change the line number of these types of messages.
+
 
 #define IPC_MESSAGE_START AutomationMsgStart
 
 // This message is fired when the AutomationProvider is up and running
 // in the app (the app is not fully up at this point). The parameter to this
 // message is the version string of the automation provider. This parameter
 // is defined to be the version string as returned by
 // chrome::VersionInfo::Version().
 // The client can choose to use this version string to decide whether or not
 // it can talk to the provider.
@@ skipping 929 matching lines @@
                             std::string /* JSON response */,
                             bool /* success */)
 
 // This message requests that a key press be performed.
 // Request:
 //   int - tab handle
 //   int - the ui::KeyboardCode of the key that was pressed.
 IPC_MESSAGE_CONTROL2(AutomationMsg_KeyPress,
                      int /* tab_handle */,
                      int /* key */)
-
-// Browser -> renderer messages.
-
-// Requests a snapshot.
-IPC_MESSAGE_ROUTED0(AutomationMsg_SnapshotEntirePage)
-
-#if !defined(NO_TCMALLOC) && (defined(OS_LINUX) || defined(OS_CHROMEOS))
-// Requests to dump a heap profile.
-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)
-
-// Renderer -> browser messages.
-
-// Sent as a response to |AutomationMsg_Snapshot|.
-IPC_MESSAGE_ROUTED3(AutomationMsg_SnapshotEntirePageACK,
-                    bool /* success */,
-                    std::vector<unsigned char> /* png bytes */,
-                    std::string /* error message */)
-
-// Sent when the renderer has scheduled a client redirect to occur.
-IPC_MESSAGE_ROUTED2(AutomationMsg_WillPerformClientRedirect,
-                    int64 /* frame_id */,
-                    double /* # of seconds till redirect will be performed */)
-
-// Sent when the renderer has completed or canceled a client redirect for a
-// particular frame. This message may be sent multiple times for the same
-// redirect.
-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 */)
-
-// 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
-// number change" applies only to the automation <-> browser messages.