From 3581b585acf996fb8515c11d30682269557301c2 Mon Sep 17 00:00:00 2001
From: Stephen Blott
Date: Sat, 23 Aug 2014 15:01:03 +0100
Subject: Allow passing of keys to the underlying page (minor code review).

---
 background_scripts/main.coffee | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'background_scripts')

diff --git a/background_scripts/main.coffee b/background_scripts/main.coffee
index e32027b6..6d986187 100644
--- a/background_scripts/main.coffee
+++ b/background_scripts/main.coffee
@@ -512,10 +512,10 @@ handleKeyDown = (request, port) ->
     console.log("checking keyQueue: [", keyQueue + key, "]")
     keyQueue = checkKeyQueue(keyQueue + key, port.sender.tab.id, request.frameId)
     console.log("new KeyQueue: " + keyQueue)
-  # Tell the front end whether there are keys in the queue.  If there are, then subsequent keys in passKeys will be
+  # Tell the content script whether there are keys in the queue.  If there are, then subsequent keys in passKeys will be
   # handled by vimium.
   # FIXME: There is a race condition here.  The behaviour depends upon whether this message gets back
-  # to the front end before the next keystroke or not.
+  # to the content script before the next keystroke or not.
   chrome.tabs.sendMessage(port.sender.tab.id,
     name: "currentKeyQueue",
     keyQueue: keyQueue)
-- 
cgit v1.2.3