From e0f2c18286e5485963e40d3711a0cf41d987541e Mon Sep 17 00:00:00 2001
From: mrmr1993
Date: Wed, 3 Jun 2015 05:21:56 +0100
Subject: Inline HUD.findModeKeydown at its sole callsite

---
 content_scripts/hud.coffee | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/content_scripts/hud.coffee b/content_scripts/hud.coffee
index 33656210..30dece24 100644
--- a/content_scripts/hud.coffee
+++ b/content_scripts/hud.coffee
@@ -60,6 +60,8 @@ HUD =
       @tween.fade 0, 150, => @hide true, updateIndicator
 
   hideFindMode: (data) ->
+    window.scrollTo @findMode.scrollX, @findMode.scrollY if @findMode.options.returnToViewport
+
     # An element element won't receive a focus event if the search landed on it while we were in the HUD
     # iframe. To end up with the correct modes active, we create a focus/blur event manually after refocusing
     # this window.
@@ -70,11 +72,7 @@ HUD =
     focusNode?.focus()
 
     findModeQuery.rawQuery = data.query
-    @findModeKeydown data.event
-
-  findModeKeydown: (event) ->
-    window.scrollTo @findMode.scrollX, @findMode.scrollY if @findMode.options.returnToViewport
-    postExit = null
+    {event} = data
 
     if event.keyCode == keyCodes.enter
       handleEnterForFindMode()
-- 
cgit v1.2.3