DevTools: Implement extensions-based shortcut bindings

Source/devtools/front_end/SettingsScreen.js

Index: Source/devtools/front_end/SettingsScreen.js
diff --git a/Source/devtools/front_end/SettingsScreen.js b/Source/devtools/front_end/SettingsScreen.js
index cd558beb909a9a53c0715120ecfcf67bb0c7410c..e237c9912da6782298db3eef39c4b424feafe7b9 100644
--- a/Source/devtools/front_end/SettingsScreen.js
+++ b/Source/devtools/front_end/SettingsScreen.js
@@ -722,6 +722,24 @@ WebInspector.SettingsController.prototype =
 
 /**
  * @constructor
+ * @implements {WebInspector.ActionDelegate}
+ */
+WebInspector.SettingsController.SettingsScreenActionDelegate = function() { }
+
+WebInspector.SettingsController.SettingsScreenActionDelegate.prototype = {
+    /**
+     * @param {!KeyboardEvent=} keyEvent
+     * @return {boolean}
+     */
+    handleAction: function(keyEvent)
+    {
+        WebInspector.settingsController.showSettingsScreen(!!keyEvent ? WebInspector.SettingsScreen.Tabs.General : undefined);

[pfeldman, 2014/03/24 16:54:22]

How can there be no keyEvent?

[apavlov, 2014/03/25 10:03:45]

That was a provisional version to handle both keyboard and mouse click
invocation.

+        return true;
+    }
+}
+
+/**
+ * @constructor
  * @extends {WebInspector.Object}
  * @param {function(!Element, string, ?string)} itemRenderer
  */