Category group support/Renamings.

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.
@@ skipping 910 matching lines @@
 // Request:
 //   gfx::Rect - the bounds of the window
 // Response:
 //   None expected
 IPC_MESSAGE_ROUTED1(AutomationMsg_MoveWindow,
                     gfx::Rect /* window position and dimentions */)
 
 // Call BeginTracing on the browser TraceController. This will tell all
 // processes to start collecting trace events via base/debug/trace_event.h.
 IPC_SYNC_MESSAGE_CONTROL1_1(AutomationMsg_BeginTracing,
-                            std::string /* categories */,
+                            std::string /* category_patterns */,
                             bool /* success */)
 
 // End tracing (called after BeginTracing). This blocks until tracing has
 // stopped on all processes and all the events are ready to be retrieved.
 IPC_SYNC_MESSAGE_CONTROL0_2(AutomationMsg_EndTracing,
                             size_t /* num_trace_chunks */,
                             bool /* success */)
 
 // Retrieve trace event data (called after EndTracing). Must call exactly
 // |num_trace_chunks| times.
@@ skipping 67 matching lines @@
 
 // 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.