DevTools: Decouple shortcuts from actions, introduce shortcut contexts

Source/devtools/front_end/Main.js

Index: Source/devtools/front_end/Main.js
diff --git a/Source/devtools/front_end/Main.js b/Source/devtools/front_end/Main.js
index e82b996c20ca3afbbc468f8f0b6b93d244db3e77..1b33e72ad8c226df8a147a6ad2c4d3aa1883aced 100644
--- a/Source/devtools/front_end/Main.js
+++ b/Source/devtools/front_end/Main.js
@@ -334,7 +334,8 @@ WebInspector.Main.prototype = {
         WebInspector.settings.initializeBackendSettings();
 
         this._registerModules();
-        WebInspector.KeyboardShortcut.registerActions();
+        WebInspector.moduleManager.instance(WebInspector.ActionRegistryAPI).registerActions();

[pfeldman, 2014/04/14 13:10:44]

You should depend on the action system directly - it can be a part of UI
component

[apavlov, 2014/04/15 13:33:14]

Done.

+        WebInspector.KeyboardShortcut.registerBindings();
 
         WebInspector.panels = {};
         WebInspector.inspectorView = new WebInspector.InspectorView();
@@ -540,7 +541,7 @@ WebInspector.Main.prototype = {
             event.consume(true);
             return;
         }
-        WebInspector.KeyboardShortcut.handleShortcut(event);
+        WebInspector.KeyboardShortcut.handleShortcut(event, WebInspector.inspectorView.currentPanelId() || "");
     },
 
     _documentCanCopy: function(event)