Share your custom Firefox/Minefield 4 stylish scripts

By Steven P.
in Web Browser Discussion & Support

 Share

Recommended Posts

Collaborator

Deo Domuique

Posted
Posted

Quazzi Thank you! It worked!

Something last left... Please help if you can...

I got this code from "Soap-Something" ( his nickname ):

#navigator-toolbox > toolbar:not(#TabsToolbar) {
  background-color: rgb(227,237,246) !important;
}

#navigator-toolbox[tabsontop="true"] .tabbrowser-tab[selected="true"] {
  background-image: -moz-radial-gradient(center top, white, rgba(255,255,255,0) 60%),
                    -moz-linear-gradient(left, transparent, transparent 1px,
                                               rgba(255,255,255,.5) 1px, rgba(255,255,255,.5)),
                    -moz-linear-gradient(left, transparent, transparent 1px,
                                               rgb(227,237,246) 1px, rgb(227,237,246)) !important;
}

It gave me the color of 4beta6 to MineField 4 b8 pre... But when I press alt, the Menu Bar isn't transparent... Gets the same color and looks weird...

Community Regular

foxxyn8

Posted
Posted

Quazzi Thank you! It worked!

Something last left... Please help if you can...

I got this code from "Soap-Something" ( his nickname ):

#navigator-toolbox > toolbar:not(#TabsToolbar) {
  background-color: rgb(227,237,246) !important;
}

#navigator-toolbox[tabsontop="true"] .tabbrowser-tab[selected="true"] {
  background-image: -moz-radial-gradient(center top, white, rgba(255,255,255,0) 60%),
                    -moz-linear-gradient(left, transparent, transparent 1px,
                                               rgba(255,255,255,.5) 1px, rgba(255,255,255,.5)),
                    -moz-linear-gradient(left, transparent, transparent 1px,
                                               rgb(227,237,246) 1px, rgb(227,237,246)) !important;
}

It gave me the color of 4beta6 to MineField 4 b8 pre... But when I press alt, the Menu Bar isn't transparent... Gets the same color and looks weird...

Try this:

#navigator-toolbox > toolbar:not(#TabsToolbar):not(#toolbar-menubar) {
  background-color: rgb(227,237,246) !important;
}

#navigator-toolbox[tabsontop="true"] .tabbrowser-tab[selected="true"] {
  background-image: -moz-radial-gradient(center top, white, rgba(255,255,255,0) 60%),
                    -moz-linear-gradient(left, transparent, transparent 1px,
                                               rgba(255,255,255,.5) 1px, rgba(255,255,255,.5)),
                    -moz-linear-gradient(left, transparent, transparent 1px,
                                               rgb(227,237,246) 1px, rgb(227,237,246)) !important;
}

#main-menubar {
background: none !important;
}

Collaborator

Deo Domuique

Posted
Posted

Thank you foxxyn! Are you the user "Soap-Something"? He knew very well scripting but he stopped writing and you came up... Lol

Vajilent how you see if you get errors? Through error console? I don't see there something about the css script but only for sites etc...

Community Regular

foxxyn8

Posted
Posted

Thank you foxxyn! Are you the user "Soap-Something"? He knew very well scripting but he stopped writing and you came up... Lol

Vajilent how you see if you get errors? Through error console? I don't see there something about the css script but only for sites etc...

Are you talking about SoapyHamHocks? No, that's not me. I'm just foxxy!

:D

Still getting an error though...

22:0 Error in parsing value for 'right' declaration dropped.

Post the code!

Collaborator

Deo Domuique

Posted
Posted 


#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#addon-bar {
position: fixed;
bottom: -1px;
right: -130px !important;
padding: 0 2px 0 6px;
border-radius: 4px 4px 0 0;
border: 0 !important;
border-left: 1px solid rgba(0,0,0,.25) !important;
border-right: 1px solid rgba(0,0,0,.25) !important;
border-top: 1px solid rgba(0,0,0,.25) !important;
border-bottom: 2px solid rgba(0,0,0,.25) !important;
background-color: rgb(227,237,246) !important;
box-shadow: 0 0 0 1px rgba(255,255,255,.5) inset;
-moz-appearance: none !important;
-moz-transition: right .5s 1s ease-in;
}
#browser-bottombox {
border-radius: 0 4px 4px 0;
border: 0 !important;
border-right: 2px solid rgba(0,0,0,.25) !important;
border-top: 1px solid rgba(0,0,0,.25) !important;
border-bottom: 2px solid rgba(0,0,0,.25) !important;
background-color: rgb(227,237,246) !important;
box-shadow: 0 0 0 1px rgba(255,255,255,.5) inset;
}
#navigator-toolbox:not([customizing]) ~
#browser-bottombox {
position: fixed;
bottom: 0px;
left: -1px;
}
#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#addon-bar:hover {
right: 0 !important;
-moz-transition: right .5s .4s ease-out;
}
#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#main-window[sizemode="maximized"] #addon-bar {
right: 0;
}
#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#addon-bar > #status-bar {
margin: 0 !important;
padding: 2px 2px 2px 2px;
background: none !important;
}

@-moz-document url(chrome://browser/content/browser.xul) {
#status-bar,
#status-bar > statusbarpanel,
}

#addon-bar toolbarbutton,
#addon-bar dropmarker,
#addon-bar #zoom-controls,
#addon-bar .searchbar-textbox {
margin: 0 !important;
border: none 0 transparent !important;
border-radius: 0 !important;
padding: 2px !important;
box-shadow: none !important;
}

#addon-bar toolbarseparator {
height: 100% !important; /* AH OH... NOT WORKING */
min-height: 18px !important; /* TENTATIVELY */
}

#addon-bar toolbarbutton,
#addon-bar dropmarker {
background: transparent none !important;
}

#addon-bar #status4evar-status-widget,
#addon-bar #status4evar-progress-widget {
margin: 0 !important;
border: none 0 transparent !important;
padding: 0 !important;
min-height: 18px !important;
}

#addon-bar #status4evar-status-text {
height: 18px !important; /* TENTATIVELY */
}
}

Here only I get many errors... It's for my Addon-Bar to work with Status4Evah addon.... Working like Google Chrome's bar and when I hover on text "done" the entire bar appearing...

Lines:

54:0 Selector exptected. Ruleset ignored due to bad sectors

87:1 Selector exptected. Ruleset ignored due to bad sectors

87:1 Unexpected end of file while searching for closing } of invalid rule set.

It's rob64rocks code taken from http://forum.userstyles.org/comments.php?DiscussionID=22585

but when I changed colors etc... messed up.

Community Regular

foxxyn8

Posted
Posted

Here only I get many errors... It's for my Addon-Bar to work with Status4Evah addon.... Working like Google Chrome's bar and when I hover on text "done" the entire bar appearing...

Lines:

54:0 Selector exptected. Ruleset ignored due to bad sectors

87:1 Selector exptected. Ruleset ignored due to bad sectors

87:1 Unexpected end of file while searching for closing } of invalid rule set.

It's rob64rocks code taken from http://forum.userstyles.org/comments.php?DiscussionID=22585

but when I changed colors etc... messed up.

Fixed:

@-moz-document url(chrome://browser/content/browser.xul) {

#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#addon-bar {
position: fixed;
bottom: -1px;
right: -130px !important;
padding: 0 2px 0 6px;
border-radius: 4px 4px 0 0;
border: 0 !important;
border-left: 1px solid rgba(0,0,0,.25) !important;
border-right: 1px solid rgba(0,0,0,.25) !important;
border-top: 1px solid rgba(0,0,0,.25) !important;
border-bottom: 2px solid rgba(0,0,0,.25) !important;
background-color: rgb(227,237,246) !important;
box-shadow: 0 0 0 1px rgba(255,255,255,.5) inset;
-moz-appearance: none !important;
-moz-transition: right .5s 1s ease-in;
}

#browser-bottombox {
border-radius: 0 4px 4px 0;
border: 0 !important;
border-right: 2px solid rgba(0,0,0,.25) !important;
border-top: 1px solid rgba(0,0,0,.25) !important;
border-bottom: 2px solid rgba(0,0,0,.25) !important;
background-color: rgb(227,237,246) !important;
box-shadow: 0 0 0 1px rgba(255,255,255,.5) inset;
}

#navigator-toolbox:not([customizing]) ~
#browser-bottombox {
position: fixed;
bottom: 0px;
left: -1px;
}

#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#addon-bar:hover {
right: 0 !important;
-moz-transition: right .5s .4s ease-out;
}

#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#main-window[sizemode="maximized"] #addon-bar {
right: 0;
}

#navigator-toolbox:not([customizing]) ~ #browser-bottombox
#addon-bar > #status-bar {
margin: 0 !important;
padding: 2px 2px 2px 2px;
background: none !important;
}

#addon-bar toolbarbutton,
#addon-bar dropmarker,
#addon-bar #zoom-controls,
#addon-bar .searchbar-textbox {
margin: 0 !important;
border: none 0 transparent !important;
border-radius: 0 !important;
padding: 2px !important;
box-shadow: none !important;
}

#addon-bar toolbarseparator {
height: 100% !important; /* AH OH... NOT WORKING */
min-height: 18px !important; /* TENTATIVELY */
}

#addon-bar toolbarbutton,
#addon-bar dropmarker {
background: transparent none !important;
}

#addon-bar #status4evar-status-widget,
#addon-bar #status4evar-progress-widget {
margin: 0 !important;
border: none 0 transparent !important;
padding: 0 !important;
min-height: 18px !important;
}

#addon-bar #status4evar-status-text {
height: 18px !important; /* TENTATIVELY */
}
}

I removed 

#status-bar,
#status-bar > statusbarpanel,
}

because that's what was causing all your errors.

Community Regular

foxxyn8

Posted
Posted

@-moz-document url(chrome://browser/content/browser.xul) {

What's that? I removed it too and worked again... Do I need it?

In this case, technically, no. That's a rule that applies the styling ONLY to browser.xul elements. It's just good habit. If you removed it, make sure you removed the "}" at the very end of your code.

Community Regular

foxxyn8

Posted
Posted

Yes I removed the last bracket. Ok then, thank you!

Do you know why I can't load your script "flat and dark" through userChrome.css file? I can only through Stylish...

The "Hide NavBar" Section goes in userChrome

The rest goes in userContent

Collaborator

vajlent

Posted
Posted

Post the code!

#addon-bar {
 position: fixed;
 bottom: -19px;
 right: 18px;
 border: 0 !important;
 -moz-appearance: none !important;
 -moz-transition: bottom .5s 1s ease-in;
 padding-top: 22px !important;
}

#browser-bottombox {
 position: fixed;
}

#addon-bar:hover {
 bottom: 0;
 -moz-transition: bottom .5s .4s ease-out;
}

#main-window[sizemode="maximized"] #addon-bar {
 right: 17;
}

#addon-bar > #status-bar {
 margin: 0 !important;
 padding: 0 2px 0 2px;
 border-radius: 4px 4px 0 0;
 border: 0 !important;
 border-left: 1px solid rgba(0,0,0,.25) !important;
 border-right: 1px solid rgba(0,0,0,.25) !important;
 border-top: 1px solid rgba(0,0,0,.25) !important;
 background-color: rgb(207, 219, 236) !important;
 background-image: -moz-linear-gradient(rgba(255,255,255,.5), rgb(207,220,236)) !important;
 box-shadow: 0 0 0 1px rgba(255,255,255,.5) inset;
}

 #browser-bottombox, #status-bar {
 background-image: -moz-linear-gradient(white, rgba(255,255,255,.5) 30%), -moz-linear-gradient(hsl(214,44%,87%), hsl(214,44%,87%));
}

Community Regular

foxxyn8

Posted
Posted

I'm pretty satisfied with my setup of the addon bar icon_wink.gif

addonbar.png

Still getting an error though...

  • 22:0 Error in parsing value for 'right' declaration dropped.

Bring back the tab progress lines and give us the home tab button now! :p

You didn't specify the unit of measurement.

Fixed:

#addon-bar {
 position: fixed;
 bottom: -19px;
 right: 18px;
 border: 0 !important;
 -moz-appearance: none !important;
 -moz-transition: bottom .5s 1s ease-in;
 padding-top: 22px !important;
}

#browser-bottombox {
 position: fixed;
}

#addon-bar:hover {
 bottom: 0;
 -moz-transition: bottom .5s .4s ease-out;
}

#main-window[sizemode="maximized"] #addon-bar {
 right: 17px;
}

#addon-bar > #status-bar {
 margin: 0 !important;
 padding: 0 2px 0 2px;
 border-radius: 4px 4px 0 0;
 border: 0 !important;
 border-left: 1px solid rgba(0,0,0,.25) !important;
 border-right: 1px solid rgba(0,0,0,.25) !important;
 border-top: 1px solid rgba(0,0,0,.25) !important;
 background-color: rgb(207, 219, 236) !important;
 background-image: -moz-linear-gradient(rgba(255,255,255,.5), rgb(207,220,236)) !important;
 box-shadow: 0 0 0 1px rgba(255,255,255,.5) inset;
}

 #browser-bottombox, #status-bar {
 background-image: -moz-linear-gradient(white, rgba(255,255,255,.5) 30%), -moz-linear-gradient(hsl(214,44%,87%), hsl(214,44%,87%));
}

Changed :

right: 17;

to  

right: 17px;

:)

Collaborator

Deo Domuique

Posted
Posted

foxxyn save me bro!... With this code I make the "New Tab Button" -> Cross to be transparent without border...

But I'd like also when I hover to show me the transparent border... How can I?

.tabs-newtab-button {
        background: none !important;
        border: transparent !important;
}

Community Regular

foxxyn8

Posted
Posted

foxxyn save me bro!... With this code I make the "New Tab Button" -> Cross to be transparent without border...

But I'd like also when I hover to show me the transparent border... How can I?

.tabs-newtab-button {
        background: none !important;
        border: transparent !important;
}

I use a custom-modified(by me) Elan in Win 7.

is this what you want?

.tabs-newtab-button:hover {
        background: none !important;
        border: transparent !important;
}

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • WhatsApp slams Isreali firm, NSO Group, for trying to spy on its users

      By Brian Miller · Posted

      HUH? Don't the same people own it?
    • macOS ‘Golden Gate' unveiled with standalone Siri app, performance improvements and more

      By +virtorio · Posted

      They fixed the weird looking sidebars. I'm happy.
    • JetBrains launches Rider 2026.2 EAP 5, bringing several AI improvements

      By David Uzondu · Posted

      JetBrains launches Rider 2026.2 EAP 5, bringing several AI improvements by David Uzondu JetBrains has released the fifth EAP version of Rider 2026.2, bringing a faster startup flow with the new non-modal startup screen and quality-check hooks for Claude Code and Codex. In the latest EAP release, Rider now has newly bundled "quality-check" hooks that run background tests on code edits before the external agent proceeds. For example, after Claude Code rewrites a class, Rider immediately triggers a PostToolUse hook that analyzes the code for syntax errors and formatting warnings. It then passes those findings back to the model as feedback, allowing the agent to fix its own output before finalizing the task. If Rider detects compilation errors, the IDE prevents the agent from treating the task as complete, while minor formatting warnings simply help guide the model toward better output. The "Explain with AI" feature can now tackle tricky build errors directly from the console, helping .NET developers who frequently wrestle with multi-targeting failures and MSBuild errors. JetBrains introduced Explain with AI back in the 2024.1 release cycle. With this feature, instead of forcing developers to copy long diagnostics into a separate chat window, Rider now lets you trigger these explanations directly from the error source. In similar EAP news, JetBrains recently opened the first EAP for IntelliJ IDEA 2026.2, with features that appeal to both those who are into AI-assisted coding and those who prefer "classic" manual development. For manual developers, the release adds revamped dependency completion for Maven and Gradle build scripts, which pulls data directly from the local cache to suggest relevant versions. It also brings the Spring Debugger update, displaying security indicators next to endpoints to visualize secured routes during runtime. In addition to database migration tools for Flyway and Liquibase, this build introduces a Hibernate debugger that shows the exact SQL or HQL queries that the framework plans to execute, letting developers jump directly to the Java code that triggered them.
    • Politically funny images of the World

      By +primortal · Posted

    • Is your Apple Watch supported? Check the watchOS 27 compatibility list

      By loaderbull · Posted

      I have updated my Series 9 Watch so I assume there is either a mistake in what was said, or as suggested - the new AI feature set isn’t supported on anything other than those listed above.

  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient

  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      PsYcHoKiLLa
      222
    3. 3
      ATLien_0
      87
    4. 4
      Steven P.
      80
    5. 5
      +Edouard
      80
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!