Recommended Posts

One more issue. I went ahead and installed the latest Minefield and moved over the scripts (didn't need your last fix). The active tab stylish you posted works on toolbar tabs, but not on App Tabs you create. Anyway you could make your stylish to include those as well?

post-277424-1279877174056.png

#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not(#new-tab-button),
.tabbrowser-tab[pinned="true"] {
  -moz-appearance: none !important;
  margin: 0 !important;
  padding: 0 !important;
  background-position: -6px -2px !important;
  background-repeat: no-repeat !important;
  background-size: 200% !important;
  -moz-border-image: url("chrome://browser/skin/tabbrowser/tab.png") 4 5 3 6 / 4px 5px 3px 6px !important;
  -moz-border-radius: 10px 8px 0 0 !important;
  background-image: -moz-linear-gradient(left, transparent, transparent 1px,
                                                 rgba(255,255,255,.4) 1px, rgba(255,255,255,.4)) !important;
}

Figured at least one person might like this.

post-49492-1279877486013.png

#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not(#new-tab-button) {
  -moz-appearance: none !important;
  margin: 0 !important;
  padding: 0 !important;
  background-repeat: no-repeat !important;
  background-size: 200% !important;
  -moz-border-image: url("chrome://browser/skin/tabbrowser/tab.png") 4 5 3 6 / 4px 5px 3px 6px !important;
  -moz-border-radius: 10px 8px 0 0 !important;
}

.tabbrowser-tab:not([selected="true"]),
.tabs-newtab-button,
#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not(#new-tab-button)  {
  background-position: -5px -2px !important;
  background-image: -moz-linear-gradient(top,rgba(198,201,206,.70),
                                   rgba(151,160,172,.70)),
                    -moz-linear-gradient(bottom, rgba(0,0,0,.8) 20%, rgba(0,0,0,0) 60%) !important;
  text-shadow: 0 1px 0 rgba(255,255,255,.3) !important;
}

.tabbrowser-tab:not([selected="true"]):hover,
.tabs-newtab-button:hover,
#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not(#new-tab-button):hover {
  background-image: -moz-linear-gradient(top,rgba(198,201,206,.8),
                                   rgba(151,160,172,.8)),
                    -moz-linear-gradient(bottom, rgba(0,0,0,.8) 20%, rgba(0,0,0,0) 60%) !important;
}

Is it even possible to come close to this with stylish:

post-251611-12796373481978.png

1. the thin bright line around the menu button.

2. colour/gradient on active tab & nav & bookmarks toolbar.

3. colour/gradient on inactive tab. (same as home button)

4. colour/gradient on home button. (same as inactive tab)

Cheers

Does your Firefox look the way as it look in that screenshot? If so, could you tell me how you've done that? The toolbar buttons look way nicer compared with the original ones.

I use Chrome myself but I still have to use Firefox for our school website, so I might as well mess around a little with the beta of Firefox 4 :p

Does your Firefox look the way as it look in that screenshot? If so, could you tell me how you've done that? The toolbar buttons look way nicer compared with the original ones.

I use Chrome myself but I still have to use Firefox for our school website, so I might as well mess around a little with the beta of Firefox 4 :p

It's actually just a mockup by SpewBoy

Updated my combined stop/reload script.

post-49492-12798968274443.png

Changes:

Fixed background color on a blank tab.

Added a inner glow to make the buttons "pop" a bit.

Changed the icons to newer ones from the mockups.

Changed the way the code is applied. Only works if the stop/reload buttons are directly after the Urlbar.

http://userstyles.org/styles/33745

Feedback would be great :)

Any scripts to make the navigation and bookmarks toolbar that blue-ish gradient seen in some of the pictures instead of the gray that I seem to have? The gray is pretty dull.

Its because you're using a non-default Windows theme. Here is a snip of code that should give you that blue.

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

Of course you know I'm going to clean up your code :p Great job though, looks nice.

Edit: This is how I would do it. Should make it slimmer when maximized as well.

#main-window:not([sizemode="maximized"]) #navigator-toolbox[tabsontop="true"]:not([inFullscreen="true"]) #TabsToolbar{
  padding: 7px 110px 0 4px !important;
}

#main-window[sizemode="maximized"] #navigator-toolbox[tabsontop="true"] #TabsToolbar{
  padding: 0 110px 0 0 !important;
}

.tabbrowser-tab[fadein] {
  max-width: 210px !important;
}

#appmenu-button-container {
  display: none !important;
}

You want to mess with the margin value.

#toolbar-menubar {
margin: top right bottom left !important;
}

If you still have issues, post the code you're using and I'll give you a hand.

#feed-button 
{
  display: none !important;
}




toolbar[mode="icons"][currentset*="urlbar-

container,reload-button,stop-button"] #urlbar {
  -moz-border-radius: 4px 0 0 4px !important;
  border-right: 0 !important;
}

#urlbar-container + #reload-button,
#urlbar-container + #reload-button + #stop-button{
  border-color: rgba(0,0,0,.25) rgba(0,0,0,.32) rgba

(0,0,0,.37) !important;
  -moz-border-radius: 0 4px 4px 0!important;  
  -moz-box-shadow: 0 1px 0 rgba(0,0,0,.1) inset,
                   0 1px 0 rgba(255,255,255,.4) !important;
  background: rgba(255,255,255,.725) !important;
  margin-left: -3px !important;
  list-style-image: url

("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAMCAY

AAABm

+U3GAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAA2R

pVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77

u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ld

GEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhN

UCBDb3JlIDUuMC1jMDYwIDYxLjEzNDc3NywgMjAxMC8wMi8xMi0xNzozMjo

wMCAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3Ln

czLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjc

mlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wTU09Imh0dHA6Ly9ucy5h

ZG9iZS5jb20veGFwLzEuMC9tbS8iIHhtbG5zOnN0UmVmPSJodHRwOi8vbnM

uYWRvYmUuY29tL3hhcC8xLjAvc1R5cGUvUmVzb3VyY2VSZWYjIiB4bWxucz

p4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iIHhtcE1NOk9ya

WdpbmFsRG9jdW1lbnRJRD0ieG1wLmRpZDozQkQ3OTNFRTYwOTZERjExODRF

OUQ2RDI3Qzg1RENGMCIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDo0ODA

wNTk3Rjk2NjExMURGOTRBMUI2RTAyRUYxRjAxNiIgeG1wTU06SW5zdGFuY2

VJRD0ieG1wLmlpZDo0ODAwNTk3RTk2NjExMURGOTRBMUI2RTAyRUYxRjAxN

iIgeG1wOkNyZWF0b3JUb29sPSJBZG9iZSBQaG90b3Nob3AgQ1M1IFdpbmRv

d3MiPiA8eG1wTU06RGVyaXZlZEZyb20gc3RSZWY6aW5zdGFuY2VJRD0ieG1

wLmlpZDozQ0Q3OTNFRTYwOTZERjExODRFOUQ2RDI3Qzg1RENGMCIgc3RSZW

Y6ZG9jdW1lbnRJRD0ieG1wLmRpZDozQkQ3OTNFRTYwOTZERjExODRFOUQ2R

DI3Qzg1RENGMCIvPiA8L3JkZjpEZXNjcmlwdGlvbj4gPC9yZGY6UkRGPiA8

L3g6eG1wbWV0YT4gPD94cGFja2V0IGVuZD0iciI/PoZDigQAAAN3SURBVHj

ajJJ/aBNnGMefy11ySS65kOtilyZNurX+rAYzEJ2DaVn9R

+vAsblUN2m1UK2KKM5J/bEaVnGsqfujigqWOqZVmJPqtO3arbINEcfEiVpb

tYKm1NCY1OSa5HJ573yutFDY/tgLH7jn5b3v

+7zP90s9HonrAMCE8IgV/r1yCLOybGnFQP

+DZvi/C4VtyMyvvz26xOUubDCY7ReBy

+sz2J0XnQVFQW1/1py5u4Ay9amqChVFBVWIQ/ueDu4JyKapmtJEd9bVzLva

0bXFIOQZXM4ZYY/b/TIhivnxV8k3QadTiKLSRM7CO5lIO0vTJ0FH3ZVzpPz

Sk

+ejWnNrigsFPUP3gqL6JUK2dwyFW5jzP7TlXbvcVWtzFYiHDtR3ra8MvFBU

NaMoqvR5dc1HY4nxhQaTEZJjMag/ePhJW8O+iBSP

+XI03RuY5S1HXWJhDb16AL9BsEU3HAg

+1i6j3B7vVxFRXhY60nh2XSAwnM7KYUkm2ZVl71eIYFhd6CkEjuMgGX8Jt/

o6Vz0beFj3XW317uyrsXx8zV1QgQDJ+Rmej+440Rp6q3RBC

+qKFKM3XSqe7xu98fv1y5Kcu5+ScjIatXZwaHi1p6QEBEEAhmZATMSh//bN

MvzJHB4cqDu9c

+tuRUzmg6Lgjim68ejxkHfe/AlRrWOGUIzF5XI9xaenUDSubV7ru/Gzxai/

iXMT/sPvVOfpU

+0sy26nFYK62LCezfScaT1f802zOHUIm9GL6VTajnOVsaaRJBIWM3IUQMbR

gRZHosVOsBihesFMwW7lr9g5zmN8wxGlVELGRl647/3W01E19+3ytv6hCUN

1+YL1n9FYzHuuvd2Ldd5klrULVO1ihJ1sYhzNEvRompFS/TqzOfpJQ2NobW

NTk95mjbAU+LRk4BnHhPCmzXW/SBlJvvDjTx

+fOnli9qS4E3EE9+8vXfHeu5/

+cf1XF9YW1sx9hg36wcRFNxxpDrlmz2lxFpccrwoda6J5PoIB9hk5rmoiFV

qO9+7Z4xt4NFhrsfIMIeQpZnQ4mUw60+lM8Xgill1fWXnuiy/39ngdfEHrw

fpDHwTW/TndKM3Q55iWnrPfL98YPBzE

+pYmbMOPGZ1Xr3i6u7s/TIipEimbNaMrot3GP9q2dcvfS5csjuFc7uCMR/D

sIqR/mujUMiOlyF9a8VqAAQCMEogyPkkkHQAAAABJRU5ErkJggg==") !

important;
  opacity: 1 !important;
  padding: 0 6px 0 6px !important;
  -moz-transition: -moz-box-shadow .1s !important;
}

#urlbar-container + #reload-button {
  -moz-image-region: rect(0 11px 12px 0) !important;
}

#urlbar-container + #reload-button + #stop-button {
  -moz-image-region: rect(0 22px 12px 11px) !important;
}

#urlbar-container + #reload-button:not([disabled]):hover{
  background-image: -moz-linear-gradient(#9eccf1, #6fb1e1 

49%,
                                   #5b9fd9 50%, #5198d2 

60%,
                                   #3e8ac9) !important;
  -moz-box-shadow: 0 0 1px 0 rgba(255,255,255,.40) inset !

important;
}

#urlbar-container + #reload-button + #stop-button{
  background-image: -moz-linear-gradient(#e6a18a, #d17764 

49%,
                                   #c05d4e 50%, #b95546 

60%,
                                   #c15a4a) !important;
  -moz-box-shadow: 0 0 1px 0 rgba(255,255,255,.40) inset !

important;
}

#urlbar-container + #reload-button:not

([disabled]):hover:active,
#urlbar-container + #reload-button + #stop-button:not

([disabled]):hover:active {
  -moz-box-shadow: inset 0 0 3px rgba(0,0,0,.8) !important;
}

#stop-button .toolbarbutton-icon,
#reload-button .toolbarbutton-icon{
  height: auto !important;
  width: auto !important;
}



#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not

(#new-tab-button) {
  -moz-appearance: none !important;
  margin: 0 !important;
  padding: 0 !important;
  background-repeat: no-repeat !important;
  background-size: 200% !important;
  -moz-border-image: url

("chrome://browser/skin/tabbrowser/tab.png") 4 5 3 6 / 4px 

5px 3px 6px !important;
  -moz-border-radius: 10px 8px 0 0 !important;
}

.tabbrowser-tab:not([selected="true"]),
.tabs-newtab-button,
#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not

(#new-tab-button)  {
  background-position: -5px -2px !important;
  background-image: -moz-linear-gradient(top,rgba

(198,201,206,.70),
                                   rgba(151,160,172,.70)),
                    -moz-linear-gradient(bottom, rgba

(0,0,0,.8) 20%, rgba(0,0,0,0) 60%) !important;
  text-shadow: 0 1px 0 rgba(255,255,255,.3) !important;
}

.tabbrowser-tab:not([selected="true"]):hover,
.tabs-newtab-button:hover,
#TabsToolbar > .toolbarbutton-1:not(#alltabs-button):not

(#new-tab-button):hover {
  background-image: -moz-linear-gradient(top,rgba

(198,201,206,.8),
                                   rgba(151,160,172,.8)),
                    -moz-linear-gradient(bottom, rgba

(0,0,0,.8) 20%, rgba(0,0,0,0) 60%) !important;
}



#toolbar-menubar
{
 position: fixed !important;
 margin: -25px 0 0 100px !important;
 background: -moz-linear-gradient(top, rgba(255, 255, 255, 

0.1) 0%, rgba(255, 255, 255, 0.5) 100%)!important;
 -moz-border-radius: 0px 0px 4px 4px !important;
 text-shadow: 0 0 4px rgba(255, 255, 255, 0.8), 0 0 3px 

rgba(255, 255, 255, 0.8), 0 0 3px rgba(255, 255, 255, 0.8), 

0 0 3px rgba(255, 255, 255, 0.8) !important;
 -moz-box-shadow: 0 0 1px rgba(255, 255, 255, 0.5), 0 0 1px 

rgba(30, 30, 30, 0.5) inset, 0 0 1px rgba(60, 60, 60, 0.9) 

inset, 0 0 3px rgba(0, 0, 0, 0.7) inset !important;

}

Thanks SoapyHamHocks, not very good at this yet

Also something Ive noticed, when clicking on the search engine symbol in omnibar to change engine, the window is clear, using Beta 4.02b

Of course you know I'm going to clean up your code :p Great job though, looks nice.

Edit: This is how I would do it. Should make it slimmer when maximized as well.

The thing is that i think we need few pixels above the tab bar for dragging the window , that's why im against reducing the gap to 0~1px

Anyway , thanks for appreciating , i really did not do anything , i just designed it , rest is done by Active members @ Meet Firefox 4.0 :D

Doesnt work for me?

bring the stop reload (Correct Order : Reload then Stop) buttons to right of the location bar , most probably between search and awesome bar

The thing is that i think we need few pixels above the tab bar for dragging the window , that's why im against reducing the gap to 0~1px

Anyway , thanks for appreciating , i really did not do anything , i just designed it , rest is done by Active members @ Meet Firefox 4.0 :D

It only makes it 0 on top when maximized. I find that easier, I can just move my mouse all the way to the top and select a tab.

Try this:

margin: -22px 0 0 110px !important;

#toolbar-menubar
{
 position: fixed !important;
 margin: -22px 0 0 110px !important;
 background: -moz-linear-gradient(top, rgba(255, 255, 255, 0.1) 0%, rgba(255, 255, 255, 0.5) 100%)!important;
 -moz-border-radius: 0px 0px 4px 4px !important;
 text-shadow: 0 0 4px rgba(255, 255, 255, 0.8), 0 0 3px rgba(255, 255, 255, 0.8), 0 0 3px rgba(255, 255, 255, 

0.8), 0 0 3px rgba(255, 255, 255, 0.8) !important;
 -moz-box-shadow: 0 0 1px rgba(255, 255, 255, 0.5), 0 0 1px rgba(30, 30, 30, 0.5) inset, 0 0 1px rgba(60, 60, 60, 

0.9) inset, 0 0 3px rgba(0, 0, 0, 0.7) inset !important;

}

Like this? Didint work, when I show menu bar, I get Windows frame

Are you using alt to show the menubar, or do you have it always visible? The numbers I used should bring it next to the Firefox button along the top.

Ok, using alt button works, is it possible to allways keep it there, and also I think it is sitting to high, maybe a 1px gap on top. Thanks SoapyHamHocks

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

    • No registered users viewing this page.
  • Posts

    • Glary Utilities 6.43.0.47 by Razvan Serea Glary Utilities offers numerous powerful and easy-to-use system tools and utilities to fix, speed up, maintain and protect your PC. Glary Utilities allow you to clean common system junk files, as well as invalid registry entries and Internet traces. You can manage and delete browser add-ons, analyze disk space usage and find duplicate files. You can also view and manage installed shell extensions, encrypt your files from unauthorized access and use, split large files into smaller manageable files and then rejoin them. Furthermore, Glary Utilities includes the options to find, fix, or remove broken Windows shortcuts, manage the programs that start at Windows startup and uninstall software. All Glary Utilities tools can be accessed through an eye-pleasing and totally simplistic interface. Glary Utilities 6.43.0.47 changelog: Optimized Memory Defrager: Optimized the clipboard cleaning algorithm, increasing speed by 5%. Optimized Wipe Free Space: Optimized the free space wiping algorithm, increasing speed by 8%. Minor GUI improvements. Minor bug fixes. Download: Glary Utilities 6.43.0.47 | 27.0 MB (Freeware) Download: Portable Glary Utilities | 32.3 MB View: Glary Utilities Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version" In my experience uBlock Origin Lite does the job for normal everday home users. When they kill that we get to watch Firefox and Brave get a boost in user market share.
    • Block by DNS ad blocker! I dare you! I will even layer unlock Origin, on top of my internal DNS, if I need to and I don’t even block ads today (I really should but this type of behavior makes me angry). I suppose I could also just be lazy, and add the flags myself, back to each release (it wouldn’t be that difficult).
    • Wonder what MPs have ties to these privacy/verification/data harvesting companies that are going to step in this time. Last time under the Tories half the cabinet had fingers in the pies, heck even the PM and his wife at the time was working for silicon valley, probably made a fortune.
    • Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow by Sayan Sen For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions. Chromium contributor Andrey Bershanskiy shared details about recent Chromium changes and according to comments from Google engineer Devlin Cronin, Chrome has now started removing the flags that previously controlled MV2 availability. kExtensionManifestV2Disabled, the Chromium feature flag that allowed controlled disabling of MV2 add-ons, is now completely removed, which means you will likely no longer find uBlock Origin in your browser extensions list. He wrote: "The kExtensionManifestV2Disabled feature has been default-enabled for over a year. Remove the feature and the effectively-dead code. ... Any tests that relied on being in the "warning" phase (i.e., with the kExtensionManifestV2Disabled) for their sole behavior testing are removed, since this stage is no longer reachable." Cronin further explained why MV2 extensions are no longer allowed in supported Chrome versions as maintaining the associated functionality indefinitely is no longer possible. He cited growing technical difficulties and implementation complexities as well as security concerns. He wrote: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire. Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others)." What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151. Here is a rundown of the changes coming in the final such releases of Chromium releases: Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024. uBlock Origin developer Raymond Hill (gorhill) apparently stated the following: "For Opera I did submit 1.70.0 rather late, but this was weeks ago. A while ago I received an email from Opera that they plan to abandon MV2-based extension so maybe they are no longer allocating resources for reviewing such extensions." The email which developers like Gorhill mentions was received from Opera last year. Here is what it seemingly said: Hence for now the only Chromium browser that seems to be on-board fully with MV2 support is Brave, and perhaps Vivaldi as well. Meanwhile if you want to ditch Chromium browsers entirely then Mozilla Firefox is an excellent alternative as MV3 and MV2 are both supported. Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version. Source: w3C (GitHub repo) As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!
  • Recent Achievements

    • Week One Done
      skylerssviv earned a badge
      Week One Done
    • One Month Later
      mobmobiles earned a badge
      One Month Later
    • 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
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      PsYcHoKiLLa
      217
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      82
  • Tell a friend

    Love Neowin? Tell a friend!