Recommended Posts

Try this:

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

 #appmenu-button {
   border: 2px solid !important;
   border-top: none !important;
   -moz-border-left-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-border-bottom-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-border-right-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset,
                    0 0 2px 1px rgba(255,255,255,.25) inset !important;
 }

 #appmenu-button {
   -moz-appearance: none !important;
   background-image: -moz-linear-gradient(rgb(247,182,82), rgb(215,98,10) 95%) !important;
   background-clip: padding-box !important;
   -moz-border-radius: 0 0 4px 4px !important;
   border: 1px solid rgba(83,42,6,.9) !important;
   border-top: none !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset,
                    0 0 0 1px rgba(255,255,255,.25) inset !important;
   color: white !important;
   font-weight: bold !important;
   text-shadow: 0 0 1px rgba(0,0,0,.7),
                0 1px 2px rgba(0,0,0,.5) !important;
   padding: .1em 1.5em .15em 1.5em !important;
   margin: 0 !important;
 }

 #appmenu-button:-moz-window-inactive {
   background: transparent !important;
   background-clip: padding-box !important;
   border-color: rgba(0,0,0,.4) !important;
 }

 #appmenu-button:hover:not(:active):not([open]),
 #appmenu-button:hover:-moz-window-inactive:not(:active):not([open]) {
   background-image: -moz-radial-gradient(center bottom, farthest-side, rgba(252,240,89,.5) 10%, rgba(252,240,89,0) 70%),
                     -moz-radial-gradient(center bottom, farthest-side, rgb(236,133,0), rgba(255,229,172,0)),
                     -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
   border-color: rgba(83,42,6,.9) !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.1) inset,
                    0 0 2px 1px rgba(250,234,169,.7) inset,
                    0 -1px 0 rgba(250,234,169,.5) inset !important;
 }

 #appmenu-button:hover:active,
 #appmenu-button[open] {
   background-image: -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
   -moz-border-radius: 0 !important;
   -moz-box-shadow: 0 2px 4px rgba(0,0,0,.4) inset,
                    0 1px 1px rgba(0,0,0,.2) inset !important;
 }
#main-window {
  margin-top: -1px !important;
}

Try this:

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

 #appmenu-button {
   border: 2px solid !important;
   border-top: none !important;
   -moz-border-left-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-border-bottom-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-border-right-colors: rgba(255,255,255,.5) rgba(83,42,6,.9) !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset,
                    0 0 2px 1px rgba(255,255,255,.25) inset !important;
 }

 #appmenu-button {
   -moz-appearance: none !important;
   background-image: -moz-linear-gradient(rgb(247,182,82), rgb(215,98,10) 95%) !important;
   background-clip: padding-box !important;
   -moz-border-radius: 0 0 4px 4px !important;
   border: 1px solid rgba(83,42,6,.9) !important;
   border-top: none !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.25) inset,
                    0 0 0 1px rgba(255,255,255,.25) inset !important;
   color: white !important;
   font-weight: bold !important;
   text-shadow: 0 0 1px rgba(0,0,0,.7),
                0 1px 2px rgba(0,0,0,.5) !important;
   padding: .1em 1.5em .15em 1.5em !important;
   margin: 0 !important;
 }

 #appmenu-button:-moz-window-inactive {
   background: transparent !important;
   background-clip: padding-box !important;
   border-color: rgba(0,0,0,.4) !important;
 }

 #appmenu-button:hover:not(:active):not([open]),
 #appmenu-button:hover:-moz-window-inactive:not(:active):not([open]) {
   background-image: -moz-radial-gradient(center bottom, farthest-side, rgba(252,240,89,.5) 10%, rgba(252,240,89,0) 70%),
                     -moz-radial-gradient(center bottom, farthest-side, rgb(236,133,0), rgba(255,229,172,0)),
                     -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
   border-color: rgba(83,42,6,.9) !important;
   -moz-box-shadow: 0 1px 0 rgba(255,255,255,.1) inset,
                    0 0 2px 1px rgba(250,234,169,.7) inset,
                    0 -1px 0 rgba(250,234,169,.5) inset !important;
 }

 #appmenu-button:hover:active,
 #appmenu-button[open] {
   background-image: -moz-linear-gradient(rgb(246,170,69), rgb(209,74,0) 95%) !important;
   -moz-border-radius: 0 !important;
   -moz-box-shadow: 0 2px 4px rgba(0,0,0,.4) inset,
                    0 1px 1px rgba(0,0,0,.2) inset !important;
 }
#main-window {
  margin-top: -1px !important;
}

No, that didn't work for me. It just moved the firefox button and tabs up a little bit.

OH the home button. :laugh:

I thought you were talking about the firefox button. The home button is not implemented yet, but there are some addons available, and a "make into app tab" in the latest nighlies.

Sorry.

So it's an add-on that can make the home button like that, not a stylish script? Do you know the name of the add-on?

So it's an add-on that can make the home button like that, not a stylish script? Do you know the name of the add-on?

Just right-click on the bar, go to customize, and move the home button up to the tabs. :)

What do you think of this, I modified the Aqua Toolbar script I had (for ages, Vista theme) to your blue button colors, only thing I'm having trouble with is getting the home button to stick, after a restart.. Maybe one of the scripts is conflicting (Tabs in titlebar?)

post-2-12794420592189.png

My home button is sticking on Beta 1 portable, it could be your re-color to the home button itself. Also, could you post that Aqua Toolbar modded script?

Will installing the beta wipe my FF3 out, or can I have both on the same machine?

I'm personally using the portable version of the beta to test it out.

http://portableapps.com/apps/internet/firefox_portable/test

Can someone help me make the home button the same color as the active tab?

Here's what I have now -moz-dialog doesn't work (tried that).

post-2-12794013813275.png

How did you get your home button to look like that? I tried this stylish code, but it didn't work for me.

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

#TabsToolbar > #home-button {
-moz-appearance: none !important;
background: transparent -moz-linear-gradient(left center , transparent, transparent 1px, rgba(128, 128, 128, 0.1) 1px, rgba(128, 128, 128, 0.1)) repeat scroll -6px 0 !important;
background-clip: border-box !important;
background-origin: padding-box !important;
background-size: 200% auto !important;
margin: 0 !important;
padding: 0 1px !important;
-moz-border-image: url("chrome://browser/skin/tabbrowser/tab.png") 3 5 3 6 / 3px 5px 3px 6px !important;
-moz-border-radius: 6px 4px 0 0 !important;
margin-left: 3px !important;
}

#TabsToolbar > #home-button:hover {
background-image: -moz-linear-gradient(left, transparent, transparent 1px, rgba(255,255,255,.4) 1px, rgba(255,255,255,.4)) !important;
}

#TabsToolbar > #home-button > .toolbarbutton-icon {
margin-top: -1px !important;
margin-bottom: -1px !important;
}

The beta is nice...might switch back from chrome to firefox if it delivers better speed while taking up less resources when the final comes out

Jaeger Monkey already overtook webkit engine (of chrome and safari) in v8 benchmark , its just that it will take some weeks (months?) to land , so don't worry about its performance in Final version

couple weird quirks i noticed recently

1. every now and again the title bar wigs out and you have to restart the browser to fix it, i think it might be related to the modded greasemonkey extension though (i'll try remember to get a screenshot next time it happens)

2. I noticed that sometimes the tab preview down in the superbar turns itself off but creating a new tab turns it back on

So are those going to be the default icons from now on? What happened to the home button?

no, that person is using small icons, what he's directing you to is the close tab icon.

home button hasn't been worked in yet, one step at a time my friend, one step at a time

2jbjmzm.png

Does anyone else have the issue with the popup windows not working properly (i.e., the title bar gets covered making it hard to close the popup window, and the firefox button overlays)?

Can some people post screenshots of what their popup windows look like? Here's an example popup window for testing:

http://rip747.github.com/popupwindow/

no, that person is using small icons, what he's directing you to is the close tab icon.

home button hasn't been worked in yet, one step at a time my friend, one step at a time

Oh I see, thanks for clearing that up. It looks like to me the only thing that's changed is a red square replacing the blue square, in the close tab icon. Is that the change?

1. every now and again the title bar wigs out and you have to restart the browser to fix it, i think it might be related to the modded greasemonkey extension though (i'll try remember to get a screenshot next time it happens)

I've had this happen to me with Firefox 3.6.4 - > 3.6.7 and Beta 1 portable. I'm not sure what's causing it, but maybe it is a bug in an extension.

Jaeger Monkey already overtook webkit engine (of chrome and safari) in v8 benchmark , its just that it will take some weeks (months?) to land , so don't worry about its performance in Final version

Chrome and Safari use 2 different JavaScript engines, JaegerMonkey isn't currently anywhere close to beating them.

It's faster than the current JS engine, but not JSC or V8 at the moment.

Chrome and Safari use 2 different JavaScript engines, JaegerMonkey isn't currently anywhere close to beating them.

It's faster than the current JS engine, but not JSC or V8 at the moment.

On some individual tests it is.

Also, Moz is holding back the merged branch.

... what he's directing you to is the close tab icon.

I'm not really interested in beta testing Fx myself this time (though I did for the previous versions.) Can anyone tell me if they have re-added the close button on a tab if there is only ONE tab open? The removal of that in Fx 3.x really irritated me. I enjoyed being able to close all tabs and just get back to a blank page.

My home button is sticking on Beta 1 portable, it could be your re-color to the home button itself. Also, could you post that Aqua Toolbar modded script?

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

#main-window #navigator-toolbox #PersonalToolbar

{

border-top: 0 none !important;

-moz-appearance: none !important;

/* Thanks to Carl Booth for the aqua image - public domain license I assume */

background-image: -moz-linear-gradient(top, rgba(58,127,197,1), rgba(47,119,189,1), rgba(0,58,229,1)) !important;

padding: 1px 3px 0px 3px !important;

color: white !important;

}

#main-window #navigator-toolbox #PersonalToolbar toolbarbutton

{

padding: 0 5px !important;

}

#main-window #navigator-toolbox #PersonalToolbar toolbarbutton > label

{

color: white !important;

}

#main-window #navigator-toolbox #PersonalToolbar > toolbaritem > menubar > menu

{

padding-top: 2px;

margin-bottom: 1px !important;

}

#main-window #navigator-toolbox #PersonalToolbar > toolbaritem > menubar > menu > label

{

color: white !important;

}

#main-window #navigator-toolbox #PersonalToolbar .toolbarbutton-menu-dropmarker

{

margin-left: 5px;

list-style-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAoAAAAICAYAAADA+m62AAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAABh0RVh0U29mdHdhcmUAUGFpbnQuTkVUIHYzLjMwQIRHEAAAAHpJREFUKFNjYCABMAPVcgKxEBBLArEMEgbxQeIgeQa2/3gAUF4fiMVACkGqlbCpBYpXAbEfSB5sItQqD2TFQLENQNwIxB5QeQaQG/mhViSCFAPZq4B4MhAnQsVB8mCArDgQyE8BYhANch9IEUgeDmCK5YEiGkAMouGKAOOdSG/rm13TAAAAAElFTkSuQmCC) !important;

}

aznkid25 my home button stylish script

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

#TabsToolbar > #home-button {

-moz-appearance: none !important;

background: transparent -moz-linear-gradient(left center , transparent, transparent 1px, rgba(128, 128, 128, 0.1) 1px, rgba(128, 128, 128, 0.1)) repeat scroll -6px 0 !important;

background-clip: border-box !important;

background-origin: padding-box !important;

background-size: 200% auto !important;

margin: 0 !important;

padding: 0 1px !important;

-moz-border-image: url("chrome://browser/skin/tabbrowser/tab.png") 3 5 3 6 / 3px 5px 3px 6px !important;

-moz-border-radius: 6px 4px 0 0 !important;

margin-left: 10px !important;

}

#TabsToolbar > #home-button:hover {

background-image: -moz-linear-gradient(left, transparent, transparent 1px, rgba(255,255,255,.4) 1px, rgba(255,255,255,.4)) !important;

}

#TabsToolbar > #home-button > .toolbarbutton-icon {

margin-top: -1px !important;

margin-bottom: -1px !important;

}

To get it there you have to disable tabs in titlebar stylish script (if you have that) then drag it to the left of the tabs (otherwise it will stick to the right) apply the script (above) and then re-enable tabs in titlebar.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I can name 10x that on why not to switch.... It's funny outlook/office are going towards web app wrappers, and then MS is now preaching native apps again.... ugh can we just pick a lane and stay in it
    • Absolutely NOBODY has suggested such a conclusion. I am affirming the sober reality check that AV2's overall market adoption will take longer than AV1's adoption rate -- which, by the way, is the whole point of the article! While PCI-SIG is productive (on paper), other WGs have created all sorts of confusing progress plans that consumers have tuned-out of their improvements... HTML/W3C, USB, HDMI, BT, WIFI (ieee802.11) as a few other groups where spec naming conventions, split progress paths, overlapping ambitions... I'm not critiquing the AV specs group; I'm simply affirming that adoption for AV2 faces headwinds beyond the macroeconomics of it all.
    • Segra 1.5.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.5.2 changelog: Settings: Added an Airplane Mode that hides account, login, and upload features. Storage: Added a button to migrate videos into the recording path after changing it. Import: Added auto-scroll and a highlight pulse to videos right after importing. Recording: Added graceful handling of low disk space and output failures, finalizing files safely with clear errors. Recording: Added a guard blocking recording when any drive exceeds 99% full. OBS: Removed the download timeout to support users with slow internet. Clips: Fixed an error modal incorrectly appearing when clip creation was cancelled. Settings: Fixed the content folder path not refreshing in the UI after changes. Updates: Improved error handling for multiple simultaneous update checks. Stability: Fixed a WebSocket reconnect loop that ran while the window was backgrounded. Dependencies: Updated project dependencies. Maintenance: Removed dead code, reduced duplication, and fixed several latent bugs. Download: Segra 1.5.2 | 73.1 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      471
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      69
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!