Recommended Posts

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...

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;
}

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...

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!


#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.

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.

@-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.

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

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%));
}

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;

:)

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;
}

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.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think it depends on what you're looking for to do; get an innate understanding of the night sky or a "quicker" path to astrophotography end results. I put "quicker" in quotes because with my Dwarf 3, I easily spend 3-4 hour sessions, half an hour driving to an un-light polluted place, setting up the smart scope + tripod for equatorial tracking, spending a few hours shooting, merging photo sessions, etc. It's something I still need to set aside a good part of an evening to do, all in all. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • 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
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!