From 3b3ec721627391f78747d19bd3cc87792e0210a8 Mon Sep 17 00:00:00 2001 From: "jam@chromium.org" Date: Fri, 21 Oct 2011 17:35:08 +0000 Subject: Update automation messages to use the new way of declaring message structs, to cut back on unnecessary code. Review URL: http://codereview.chromium.org/8356020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106734 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/common/automation_messages_internal.h | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) (limited to 'chrome/common/automation_messages_internal.h') diff --git a/chrome/common/automation_messages_internal.h b/chrome/common/automation_messages_internal.h index 63da146..ee904a1 100644 --- a/chrome/common/automation_messages_internal.h +++ b/chrome/common/automation_messages_internal.h @@ -4,18 +4,6 @@ // Defines the IPC messages used by the automation interface. -#include -#include - -#include "base/string16.h" -#include "chrome/common/content_settings.h" -#include "googleurl/src/gurl.h" -#include "ipc/ipc_message_macros.h" -#include "net/base/cert_status_flags.h" -#include "net/url_request/url_request_status.h" -#include "ui/gfx/rect.h" -#include "webkit/glue/window_open_disposition.h" - // 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 @@ -26,8 +14,20 @@ // 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 any of the messages below. This will be fixed once Xcode supports -// __COUNTER__, in which case we can get rid of the __LINE__. +// of any of the messages below. + + + + + + + + + + + + + -- cgit v1.1