aboutsummaryrefslogtreecommitdiffstats
path: root/content_scripts/vimium_frontend.coffee
diff options
context:
space:
mode:
authorStephen Blott2015-03-17 10:32:40 +0000
committerStephen Blott2015-03-17 10:32:40 +0000
commit9461d30b0d19fd65dc43e18bebec1fe0fd3ee818 (patch)
tree38336fe71a9d0d345a98b526a417024f23d12bdb /content_scripts/vimium_frontend.coffee
parentaa8d00fd9779d4061431dbdcb7a70b9c39e8049a (diff)
downloadvimium-9461d30b0d19fd65dc43e18bebec1fe0fd3ee818.tar.bz2
Activate vomnibar in window.top; hide on focus.
Diffstat (limited to 'content_scripts/vimium_frontend.coffee')
-rw-r--r--content_scripts/vimium_frontend.coffee1
1 files changed, 1 insertions, 0 deletions
diff --git a/content_scripts/vimium_frontend.coffee b/content_scripts/vimium_frontend.coffee
index eb951c33..941b2bc2 100644
--- a/content_scripts/vimium_frontend.coffee
+++ b/content_scripts/vimium_frontend.coffee
@@ -178,6 +178,7 @@ initializePreDomReady = ->
currentKeyQueue: (request) ->
keyQueue = request.keyQueue
handlerStack.bubbleEvent "registerKeyQueue", { keyQueue: keyQueue }
+ frameFocused: -> # A frame has received the focus. We don't care, here. The Vomnibar/UI-component cares.
chrome.runtime.onMessage.addListener (request, sender, sendResponse) ->
# In the options page, we will receive requests from both content and background scripts. ignore those