[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [tor-browser/tor-browser-68.1.0esr-9.0-3] fixup! Bug 31749: Fix security level panel spawning events



commit f17113f06b92a16e01973b1f05b795ed321ffc7f
Author: Georg Koppen <gk@xxxxxxxxxxxxxx>
Date:   Thu Oct 17 10:21:51 2019 +0000

    fixup! Bug 31749: Fix security level panel spawning events
---
 browser/components/securitylevel/content/securityLevel.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/browser/components/securitylevel/content/securityLevel.js b/browser/components/securitylevel/content/securityLevel.js
index 698af8f7297f..7b3e7e4f92f9 100644
--- a/browser/components/securitylevel/content/securityLevel.js
+++ b/browser/components/securitylevel/content/securityLevel.js
@@ -160,10 +160,10 @@ const SecurityLevelButton = {
     }
   },
 
-  // for when the toolbar button needs to be activated and display the Security Level panel
+  // for when the toolbar button needs to be activated and displays the Security Level panel
   //
   // In the toolbarbutton xul you'll notice we register this callback for both onkeypress and
-  // onmousedown. We do this so match the behavior of other panel spawning buttons such as Downloads, 
+  // onmousedown. We do this to match the behavior of other panel spawning buttons such as Downloads,
   // Library, and the Hamburger menus. Using oncommand alone would result in only getting fired
   // after onclick, which is mousedown followed by mouseup.
   onCommand : function(aEvent) {

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits