Ticket #9492: 0001-replaced-JavaScript-style-comments-beginning-with-a-.patch

File 0001-replaced-JavaScript-style-comments-beginning-with-a-.patch, 1.6 KB (added by gk, 6 years ago)
  • src/chrome/skin/torbutton.css

    From 3293d9ff4ef254155f178c2559831e6e92bb3fbd Mon Sep 17 00:00:00 2001
    From: Georg Koppen <g.koppen@jondos.de>
    Date: Thu, 22 Aug 2013 14:09:03 +0200
    Subject: [PATCH] replaced JavaScript style comments (beginning with a '//')
     with a real CSS comment
    
    ---
     src/chrome/skin/torbutton.css |   12 ++++++------
     1 file changed, 6 insertions(+), 6 deletions(-)
    
    diff --git a/src/chrome/skin/torbutton.css b/src/chrome/skin/torbutton.css
    index ce59cc9..ef8abbc 100644
    a b  
    1313toolbar[iconsize="small"] #torbutton-button {
    1414  list-style-image: url("chrome://torbutton/skin/tor-16.png");
    1515}
    16 // Although the tor-enabled-16.png, tor-disabled-16.png and tor-update-16.gif
    17 // indicate that they are 16x16 icons, they have 18x18 pixels in fact. This
    18 // leads to resizing the content window's height on start-up on Windows at
    19 // least. To guarantee a content window with a multiple of 200x100 we
    20 // therefore use only a x16 part of each icon while trying to minimize bad UI
    21 // effects until #8941 gets fixed.
     16/* Although the tor-enabled-16.png, tor-disabled-16.png and tor-update-16.gif
     17indicate that they are 16x16 icons, they have 18x18 pixels in fact. This
     18leads to resizing the content window's height on start-up on Windows at
     19least. To guarantee a content window with a multiple of 200x100 we
     20therefore use only a x16 part of each icon while trying to minimize bad UI
     21effects until #8941 gets fixed.*/
    2222toolbar[iconsize="small"] #torbutton-button[tbstatus="on"] {
    2323  list-style-image: url("chrome://torbutton/skin/tor-enabled-16.png");
    2424  -moz-image-region: rect(1px, 17px, 17px, 1px);