Polish the keybinding implementation a bit.

chrome/browser/ui/views/browser_actions_container.cc

Index: chrome/browser/ui/views/browser_actions_container.cc
===================================================================
--- chrome/browser/ui/views/browser_actions_container.cc	(revision 127690)
+++ chrome/browser/ui/views/browser_actions_container.cc	(working copy)
@@ -116,18 +116,14 @@
       UpdateState();
     }
 
-    // Iterate through all the keybindings and see if one is assigned to the
-    // browserAction.
-    const std::vector<Extension::ExtensionKeybinding>& commands =
-        extension_->keybindings();
-    for (size_t i = 0; i < commands.size(); ++i) {
-      if (commands[i].command_name() ==
-          extension_manifest_values::kBrowserActionKeybindingEvent) {
-        keybinding_.reset(new ui::Accelerator(commands[i].accelerator()));
-        panel_->GetFocusManager()->RegisterAccelerator(
-            *keybinding_.get(), ui::AcceleratorManager::kHighPriority, this);
-        break;
-      }
+    std::vector<Extension::ExtensionKeybinding> browser_action_command;
+    extension_->GetCommandByType(Extension::ExtensionKeybinding::BROWSER_ACTION,

[Aaron Boodman, 2012/03/21 21:05:04]

Can you change Extension to store these commands in a more easily accessible
form during parse?

So that you can just do: extension->browser_action_command(),
extension->page_action_command(), and extension->named_commands() or something.

The named_commands field probably makes sense to be a map.

+                                 &browser_action_command);
+    if (!browser_action_command.empty()) {
+      Extension::ExtensionKeybinding* command = &browser_action_command[0];
+      keybinding_.reset(new ui::Accelerator(command->accelerator()));
+      panel_->GetFocusManager()->RegisterAccelerator(
+          *keybinding_.get(), ui::AcceleratorManager::kHighPriority, this);
     }
   }