From d4e6ea04fd5e741662c6ff3e08b44481a40a651d Mon Sep 17 00:00:00 2001 From: janekptacijarabaci Date: Wed, 6 Jun 2018 18:58:12 +0200 Subject: Fix a comment in browser.js (the FindBar - a tab vs the chrome window's context) Issue #430 --- application/palemoon/base/content/browser.js | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'application') diff --git a/application/palemoon/base/content/browser.js b/application/palemoon/base/content/browser.js index af5d8b62a..def8828ec 100644 --- a/application/palemoon/base/content/browser.js +++ b/application/palemoon/base/content/browser.js @@ -365,8 +365,9 @@ var gFindBarSettings = { receiveMessage(aMessage) { switch (aMessage.name) { case this.messageName: - // If the find bar for this tab is not yet alive, only initialize - // it if there's a possibility FindAsYouType will be used. + // If the find bar for chrome window's context is not yet alive, + // only initialize it if there's a possibility FindAsYouType + // will be used. // There's no point in doing it for most random keypresses. if (!gFindBarInitialized && aMessage.data.shouldFastFind) { let shouldFastFind = this.findAsYouType; -- cgit v1.2.3