Implement actions for Automation API.

chrome/common/extensions/api/automation_internal.idl

Index: chrome/common/extensions/api/automation_internal.idl
diff --git a/chrome/common/extensions/api/automation_internal.idl b/chrome/common/extensions/api/automation_internal.idl
index 3b018be6a88f53dbefca3cd72337da5bb21ff632..fe8a905ff3cd6ca7108d47bfd38fa9e46648bfec 100644
--- a/chrome/common/extensions/api/automation_internal.idl
+++ b/chrome/common/extensions/api/automation_internal.idl
@@ -28,6 +28,9 @@ namespace automationInternal {
   // tree. See ui/accessibility/ax_tree_update.h for an extended explanation of
   // the tree update format.
   dictionary AXEventParams {
+    // The process id of the renderer host.
+    long process_id;
+
     // The routing id of the web contents that this update is for.
     long routing_id;
 
@@ -39,14 +42,31 @@ namespace automationInternal {
     AXNodeData[] nodes;
   };
 
-  // Returns the routing_id of the tab whose accessibility was enabled using
-  // enable().
-  callback EnableCallback = void(long routing_id);
+  // All possible actions that can be performed on automation nodes.
+  // TODO(dtseng): Refer to
+  // content/browser/accessibility/browser_accessibility_manager.h:BrowserAccessibilityDelegate

[dmazzoni, 2014/04/01 17:05:25]

nit: wrap to 80 chars

[aboxhall, 2014/04/01 17:49:51]

Difficult to do. I think this could stay as-is, or alternatively replace
content/browser/accessibility with c/b/a or even just leave out?

[David Tseng, 2014/04/01 21:27:15]

I removed this TODO. I initially thought I could reuse the
BrowserAccessibilityDelegate interface for actions, but it was easier to stick
with defining everything on RWH.

+  // (which should live in ui/accessibility).
+  enum ActionType {
+    focus,
+    do_default,
+    make_visible,
+    set_selection
+  };
+
+  // Returns the process_id and routing_id of the tab whose accessibility was
+  // enabled using enable().
+  callback EnableCallback = void(long process_id, long routing_id);
 
   interface Functions {
     // Enable automation of the active tab and retrieves its routing id for use
     // in future updates.
     static void enableCurrentTab(EnableCallback callback);
+
+    static void performAction(long processId,
+			      long routingId,
+                              long automationId,
+                              ActionType actionType,
+			      long[] opt_args);

[dmazzoni, 2014/04/01 17:05:25]

What about args that aren't a long, is there a chance we'll have some in the
future?

[aboxhall, 2014/04/01 17:49:51]

Suggestion: use an object for opt_args and pass by name (e.g. {"start_index": 0,
"end_index": 10}). I think this pattern is used elsewhere in extension APIs.

[David Tseng, 2014/04/01 21:27:15]

Updated with the object approach.

   };
 
   interface Events {