Bug 932344 - draw tabstoolbar bottom border ourselves during customize mode, private browsing mode and fullscreen, r=MattN
authorGijs Kruitbosch <gijskruitbosch@gmail.com>
Sat, 02 Nov 2013 11:32:25 +0100
changeset 170522 42461ce3dcd0a28811aa6c0a46473a08bbfc2e14
parent 170521 70003bbafecfc3fb63ceab87c7dcaee6584684d5
child 170523 4542f91ef48b186907d228c49f6fd8ef12e3d497
push idunknown
push userunknown
push dateunknown
reviewersMattN
bugs932344
milestone28.0a1
Bug 932344 - draw tabstoolbar bottom border ourselves during customize mode, private browsing mode and fullscreen, r=MattN
browser/themes/osx/browser.css
--- a/browser/themes/osx/browser.css
+++ b/browser/themes/osx/browser.css
@@ -2554,17 +2554,17 @@ toolbarbutton.chevron > .toolbarbutton-m
   position: relative;
   -moz-appearance: none;
   background-repeat: repeat-x;
 }
 
 /*
  * Draw the bottom border of the tabstrip when core doesn't do it for us:
  */
-#main-window[sizemode="fullscreen"] #TabsToolbar::after,
+#main-window:-moz-any([privatebrowsingmode=temporary],[sizemode="fullscreen"],[customizing],[customize-exiting]) #TabsToolbar::after,
 #main-window:not([tabsintitlebar]) #TabsToolbar::after,
 #TabsToolbar:-moz-lwtheme::after {
   content: '';
   /* Because we use placeholders for window controls etc. in the tabstrip,
    * and position those with ordinal attributes, and because our layout code
    * expects :before/:after nodes to come first/last in the frame list,
    * we have to reorder this element to come last, hence the
    * ordinal group value (see bug 853415). */