From e5a2355b91313a50318d4500cfb077dadb20134e Mon Sep 17 00:00:00 2001
From: Stephen Blott
Date: Sun, 15 Mar 2015 12:13:52 +0000
Subject: Fix frame-focus detection.

In b05276ed8264e5a71f20a7068690ba2a414ee6d8, I inadvertently moved the
focus handler from window to document.  As a consequence, detectFocus
(now registerFocus) wasn't being called when expected.
---
 content_scripts/vimium_frontend.coffee | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'content_scripts')

diff --git a/content_scripts/vimium_frontend.coffee b/content_scripts/vimium_frontend.coffee
index bc56e175..429657fc 100644
--- a/content_scripts/vimium_frontend.coffee
+++ b/content_scripts/vimium_frontend.coffee
@@ -209,7 +209,7 @@ window.initializeWhenEnabled = ->
     for type in [ "keydown", "keypress", "keyup", "click", "focus", "blur", "mousedown" ]
       do (type) -> installListener window, type, (event) -> handlerStack.bubbleEvent type, event
     installListener document, "DOMActivate", (event) -> handlerStack.bubbleEvent 'DOMActivate', event
-    installListener document, "focus", detectFocus
+    installListener window, "focus", registerFocus
     installedListeners = true
     FindModeHistory.init()
 
@@ -229,7 +229,7 @@ getActiveState = ->
 #
 # The backend needs to know which frame has focus.
 #
-detectFocus = ->
+registerFocus = ->
   # settings may have changed since the frame last had focus
   settings.load()
   chrome.runtime.sendMessage({ handler: "frameFocused", frameId: frameId })
-- 
cgit v1.2.3