diff options
| author | Stephen Blott | 2014-12-14 15:58:22 +0000 |
|---|---|---|
| committer | Stephen Blott | 2014-12-14 16:00:21 +0000 |
| commit | c698061e8ae7e9ec61a780c1ff0658f4f349a4a3 (patch) | |
| tree | d5aa1dbb025fbb1ebe95a2e95f2f14c951b8e7bb | |
| parent | 3f3444d1fe72c74439bd9bec3c27ab441ae560a0 (diff) | |
| download | vimium-c698061e8ae7e9ec61a780c1ff0658f4f349a4a3.tar.bz2 | |
FRAMESET frames should not be registered.
Somewhere along the road, this got goofed up. This reverts to the
intended behaviour.
| -rw-r--r-- | content_scripts/vimium_frontend.coffee | 2 |
1 files changed, 1 insertions, 1 deletions
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 |