From c698061e8ae7e9ec61a780c1ff0658f4f349a4a3 Mon Sep 17 00:00:00 2001
From: Stephen Blott
Date: Sun, 14 Dec 2014 15:58:22 +0000
Subject: FRAMESET frames should not be registered.

Somewhere along the road, this got goofed up.  This reverts to the
intended behaviour.
---
 content_scripts/vimium_frontend.coffee | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content_scripts/vimium_frontend.coffee b/content_scripts/vimium_frontend.coffee
index 469afe71..31f0eab5 100644
--- a/content_scripts/vimium_frontend.coffee
+++ b/content_scripts/vimium_frontend.coffee
@@ -186,7 +186,7 @@ initializeOnDomReady = ->
 
 registerFrame = ->
   # Don't register frameset containers; focusing them is no use.
-  if document.body.tagName != "FRAMESET"
+  if document.body.tagName.toLowerCase() != "frameset"
     chrome.runtime.sendMessage
       handler: "registerFrame"
       frameId: frameId
-- 
cgit v1.2.3