From d48914545ee1536ae39b02c7c885cfbdd3c8b804 Mon Sep 17 00:00:00 2001
From: janekptacijarabaci <janekptacijarabaci@seznam.cz>
Date: Thu, 7 Jun 2018 05:32:41 +0200
Subject: Using "function()" in browser.js - consistency with the surrounding
 code

Issue #430
---
 application/palemoon/base/content/browser.js | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'application')

diff --git a/application/palemoon/base/content/browser.js b/application/palemoon/base/content/browser.js
index def8828ec..ba791f709 100644
--- a/application/palemoon/base/content/browser.js
+++ b/application/palemoon/base/content/browser.js
@@ -333,14 +333,14 @@ var gFindBarSettings = {
   prefName: "accessibility.typeaheadfind",
   findAsYouType: null,
 
-  init() {
+  init: function() {
     window.messageManager.addMessageListener(this.messageName, this);
 
     gPrefService.addObserver(this.prefName, this, false);
     this.writeFindAsYouType();
   },
 
-  uninit() {
+  uninit: function() {
     window.messageManager.removeMessageListener(this.messageName, this);
 
     try {
@@ -362,7 +362,7 @@ var gFindBarSettings = {
     this.findAsYouType = gPrefService.getBoolPref(this.prefName);
   },
 
-  receiveMessage(aMessage) {
+  receiveMessage: function(aMessage) {
     switch (aMessage.name) {
       case this.messageName:
         // If the find bar for chrome window's context is not yet alive,
-- 
cgit v1.2.3