Don't send tab switching/killing/creating keyboard accelerators to pages. Th...

chrome/browser/cocoa/browser_window_cocoa.mm

Index: chrome/browser/cocoa/browser_window_cocoa.mm
===================================================================
--- chrome/browser/cocoa/browser_window_cocoa.mm	(revision 27783)
+++ chrome/browser/cocoa/browser_window_cocoa.mm	(working copy)
@@ -320,6 +320,12 @@
   // No-op. Mac doesn't support showing the menus via alt keys.
 }
 
+int BrowserWindowCocoa::GetCommandId(const NativeWebKeyboardEvent& event) {
+  // TODO(port): return the command id if this is a keyboard accelerator.
+  // CommandForKeyboardShortcut() doesn't have the full list.

[Nico, 2009/10/02 03:11:01]

Yes, that's because in cocoa most keyboard shortcuts are bound to menu items
which in turn are bound to "actions" (basically function pointers).

suzhe: I think this is ok, we can walk the menu and for all menu items that have
target commandDispatch: get the tag (which is the command id) and the
accelerator and use that to implement this function.

+  return -1;
+}
+
 void BrowserWindowCocoa::Observe(NotificationType type,
                                  const NotificationSource& source,
                                  const NotificationDetails& details) {