DevTools: Decouple shortcuts from actions, introduce shortcut contexts

Source/devtools/front_end/SourceFrame.js

Index: Source/devtools/front_end/SourceFrame.js
diff --git a/Source/devtools/front_end/SourceFrame.js b/Source/devtools/front_end/SourceFrame.js
index 937d52e22e8df9fac3a19e6336c78716f4789b16..c4ba20c82f765d825cbe1dc78ebfd3f435be621e 100644
--- a/Source/devtools/front_end/SourceFrame.js
+++ b/Source/devtools/front_end/SourceFrame.js
@@ -425,6 +425,12 @@ WebInspector.SourceFrame.prototype = {
     _editorFocused: function()
     {
         this._resetCurrentSearchResultIndex();
+        WebInspector.context.setFlavor(WebInspector.SourceFrame, this);

[pfeldman, 2014/04/17 10:40:25]

I think this should be done on the level of SourceViewer. Selected tab is our
source frame, no matter whether it has focus or not.

[apavlov, 2014/04/17 12:42:22]

If Ctrl+H were our "Search&Replace in source code" shortcut, it should not get
activated with the actual focus being in the drawer console view, for example,
right?

+    },
+
+    _editorBlurred: function()
+    {
+        WebInspector.context.setFlavor(WebInspector.SourceFrame, null);
     },
 
     _resetCurrentSearchResultIndex: function()
@@ -839,6 +845,11 @@ WebInspector.TextEditorDelegateForSourceFrame.prototype = {
         this._sourceFrame._editorFocused();
     },
 
+    editorBlurred: function()
+    {
+        this._sourceFrame._editorBlurred();
+    },
+
     populateLineGutterContextMenu: function(contextMenu, lineNumber)
     {
         this._sourceFrame.populateLineGutterContextMenu(contextMenu, lineNumber);