Recommended Posts

I tried this new style, but I just can't get away with that back/forward button. Personally don't like it, prefer the older theme. :\

I'm trying something new with back/forward buttons.

Before apply this you need move the back/forward buttons to Tab Bar.

This is just for Bars on Top.

Little lazy changelog:

1 - new back/forward button on Tab Bar;

2 - new square layout for url and search bar;

3 - fix double-click issue on Tab Bar;

4 - comment custom css for Status-4-Evar addon;

5 - uncomment custom css for default Add-on Bar;

The code is a bit out of order. I need to polish it later.

Actually, I do not like codes and programming. I am a graphic designer. My brain does not work well for codes. :blush:

So, if someone can check everything for me, thank you.

Got a issue that could not solve yet: if you use the auto hide menu bar (ALT key), the buttons are clipped when return to hide menu.

I tried to force zIndex negative on titlebar and mainmenu, but without success.

Please, give-me some feedback about this changes.

Thank you everyone for your help.

I didn't see any clipping (Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101007 Firefox/4.0b8pre ID:20101007042624), but you should do this so that it only applies the back/forward button styling when those buttons are placed on the tab bar:

#TabsToolbar #back-button {
	border-radius: 10000px !important;
	margin-top: -10px !important;
	margin-bottom: 5px !important;
	width: 30px !important;
	height: 30px !important;
	position: relative !important; 
	z-index: 1 !important;
	border: none !important;
	background-image: -moz-linear-gradient(rgba(251,252,253,.97), rgba(246,247,248,.5) 49%, rgba(231,232,233,.45) 51%, rgba(225,226,229,.2)) !important;
	box-shadow: 0 0 0 3px rgba(255,255,255,.3) inset, 0 0 0 2px rgba(255,255,255,.1) inset, 0 0 0 1px rgba(0,0,0,.15), 0 1px 0 rgba(0,0,0,.4), 0 1px 1px rgba(0,0,0,.3), 1px 2px 1px rgba(0,0,0,.2) !important;
}
#TabsToolbar #forward-button {
	border-radius: 0 5px 5px 0 !important;
	padding-left: 7px !important;
	padding-right: 3px !important;
	margin-top: -5px !important;
	margin-bottom: 10px !important;
 	width: auto !important;
 	height: auto !important;
	border: none !important;
 	-moz-margin-start: -5px !important;
	background-image: -moz-linear-gradient(rgba(251,252,253,.97), rgba(246,247,248,.5) 49%, rgba(231,232,233,.45) 51%, rgba(225,226,229,.2)) !important;
	box-shadow: 0 0 0 1px rgba(255,255,255,.3) inset, 0 0 0 2px rgba(255,255,255,.1) inset, 0 0 0 1px rgba(0,0,0,.15), 0 1px 0 rgba(0,0,0,.4), 0 1px 1px rgba(0,0,0,.3), 1px 2px 1px rgba(0,0,0,.2) !important;
	mask: url(chrome://browser/content/browser.xul#winstripe-keyhole-forward-mask) !important;
}

I didn't see any clipping (Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101007 Firefox/4.0b8pre ID:20101007042624), but you should do this so that it only applies the back/forward button styling when those buttons are placed on the tab bar:

#TabsToolbar #back-button {
	border-radius: 10000px !important;
	margin-top: -10px !important;
	margin-bottom: 5px !important;
	width: 30px !important;
	height: 30px !important;
	position: relative !important; 
	z-index: 1 !important;
	border: none !important;
	background-image: -moz-linear-gradient(rgba(251,252,253,.97), rgba(246,247,248,.5) 49%, rgba(231,232,233,.45) 51%, rgba(225,226,229,.2)) !important;
	box-shadow: 0 0 0 3px rgba(255,255,255,.3) inset, 0 0 0 2px rgba(255,255,255,.1) inset, 0 0 0 1px rgba(0,0,0,.15), 0 1px 0 rgba(0,0,0,.4), 0 1px 1px rgba(0,0,0,.3), 1px 2px 1px rgba(0,0,0,.2) !important;
}
#TabsToolbar #forward-button {
	border-radius: 0 5px 5px 0 !important;
	padding-left: 7px !important;
	padding-right: 3px !important;
	margin-top: -5px !important;
	margin-bottom: 10px !important;
 	width: auto !important;
 	height: auto !important;
	border: none !important;
 	-moz-margin-start: -5px !important;
	background-image: -moz-linear-gradient(rgba(251,252,253,.97), rgba(246,247,248,.5) 49%, rgba(231,232,233,.45) 51%, rgba(225,226,229,.2)) !important;
	box-shadow: 0 0 0 1px rgba(255,255,255,.3) inset, 0 0 0 2px rgba(255,255,255,.1) inset, 0 0 0 1px rgba(0,0,0,.15), 0 1px 0 rgba(0,0,0,.4), 0 1px 1px rgba(0,0,0,.3), 1px 2px 1px rgba(0,0,0,.2) !important;
	mask: url(chrome://browser/content/browser.xul#winstripe-keyhole-forward-mask) !important;
}

Perfect!

Thanks again!

About the clipping:

Direct10 enable, d2d etc. Same version as yours. In a clean profile, same issue.

When I come back from ALT Key, the clippling occurs. I need hover mouse on title or tabbar to force redraw.

Perfect!

Thanks again!

About the clipping:

Direct10 enable, d2d etc. Same version as yours. In a clean profile, same issue.

When I come back from ALT Key, the clippling occurs. I need hover mouse on title or tabbar to force redraw.

I tested it again. You're right about the clipping. I'm not sure how to go about fixing it though.

Does anyone know the IDs for the two Panorama buttons? The close and search buttons on the right to be exact.

I can't find anything from Panorama in DOM Inspector for some reason:

29ofsc9.jpg

#exit-button is the close button

#actions is the outside of the search button

#actions #searchbutton is the inside of the search button (the part with the image)

Panorama is here: chrome://browser/content/tabview.html

In order to avoid spamming here with long long threads I posted/updated the code on the userstyles.org.

Thus, any change will do directly there and post here the screenshot and link.

For now:

@foxxyn8 Hey, thank you so much for the IDs and the tabview.html!

- - -

I played a bit with the buttons and searchbox and here's what I came up with so far:

2lk775x.jpg

I removed the exit-button for now since it's just an image at the moment and therefore can't be changed using CSS, at least I don't know how it could be done. You can always use the Escape key to get out of Panorama.

The style is quite simple so feel free to edit it to your liking:

@-moz-document url("chrome://browser/content/tabview.html") {
 #bg {
  display: none;
 }

 #exit-button {
  display: none;
 }

 #actions {
  opacity: 1 !important;
  background: -moz-linear-gradient(top,rgb(245,183,93) 0%,rgb(220,115,35) 100%) !important;
  border-radius: 4px;
  box-shadow: 0 0 0 1px rgba(255,255,255,.5), 0 0 0 1px rgba(0,0,0,.5) inset !important;
  margin-top: -97px;
  margin-right: 4px;
 }

 #actions:hover {
  background: -moz-linear-gradient(top,rgb(245,183,93) 0%,rgb(234,140,55) 100%) !important;
 }

 #actions #searchbutton {
  opacity: 1 !important;
 }

 #searchbox {
  background: rgba(255,255,255,.8) !important;
  color: #000 !important;
 }
}

If you want to edit the dark overlay while searching you could use something like this:

#search {
 background-color: [color] !important;
}

I think the default looks pretty good so I didn't put it in the main style.

Have fun!

@foxxyn8 Hey, thank you so much for the IDs and the tabview.html!

- - -

I removed the exit-button for now since it's just an image at the moment and therefore can't be changed using CSS, at least I don't know how it could be done. You can always use the Escape key to get out of Panorama.

You can style the exit button:

#exit-button {
  background-color: orange !important;
  box-shadow: 0 0 0 1px rgba(255,255,255,.5), 0 0 0 1px rgba(0,0,0,.5) inset !important;
  border-radius: 4px !important;
  margin-right: 4px !important;
}

You can style the exit button:

#exit-button {
  background-color: orange !important;
  box-shadow: 0 0 0 1px rgba(255,255,255,.5), 0 0 0 1px rgba(0,0,0,.5) inset !important;
  border-radius: 4px !important;
  margin-right: 4px !important;
}

Wow, thank you again!^^ I only tried it with background instead of background-color. I used background-image though to get the gradient but had to create a Panorama icon in white myself.

- - -

So, I think it looks pretty good now. I uploaded it to userstyles.org since the style is a bit long because of the base64 images: http://userstyles.org/styles/37944?r=1286567046

post-309006-12865674827954.jpg

Looks good. Nice job! :yes:

FYI : "background:" is CSS shorthand. It allows you to specify all background properties with one property. It's usage is:

background: background-color | background-image | background-repeat | background-attachment | background-position;

Drifus... Bro! LoL! I don't deserve at all man to place my name in your Script's page... I don't have a clue about scripts... I just suggested one thing... LoL!

Guys, the Progress line will be history in a while... Mozilla will place only a Throbber inside the tab. There where the favicon is... Progress line spending 30% more resources and many other are the reasons!...

So, get ready! :p By the way, I like the progress line... But certainly I prefer a more resources-free FireFox!

Drifus... Bro! LoL! I don't deserve at all man to place my name in your Script's page... I don't have a clue about scripts... I just suggested one thing... LoL!

Guys, the Progress line will be history in a while... Mozilla will place only a Throbber inside the tab. There where the favicon is... Progress line spending 30% more resources and many other are the reasons!...

So, get ready! :p By the way, I like the progress line... But certainly I prefer a more resources-free FireFox!

Deo, you gave me a good suggestion... square urs bars and search. I'm using them. :yes:

About progress bar: maybe a matter of habit, but I prefer the throbber style.

Nice style dert07. Just edited a custom version of my own inspired by yours. I have a question: how can I disable the "minimize/maximize/close" buttons in panorama, I mean the titlebar bar altogether ?

You can hide the Titlebar:

#titlebar {
 visibility: hidden;
}

Although the min/max/close buttons don't hide then. They have IDs, too but I can't get them to hide. You also would have to somehow check if Panorama is active and then hide it, maybe someone else knows how to do that.

can anyone help me with this problem? why my status bar is at the left side?

What Stylish styles do you use?

- - -

I did another version of the Exit and Search buttons from Panorama and also slightly edited the Exit icon with a small X to indicate the resulting close. What do you guys think, which one looks better?

2mep9gg.jpg

You can hide the Titlebar:

#titlebar {
 visibility: hidden;
}

Although the min/max/close buttons don't hide then. They have IDs, too but I can't get them to hide. You also would have to somehow check if Panorama is active and then hide it, maybe someone else knows how to do that.

What Stylish styles do you use?

- - -

This one:

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

#FindToolbar .findbar-container {
 margin-bottom: -1px !important;
 margin-left: 5px !important;
 border-radius: 4px 4px 0 0;
 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 {background: none !important;}

#FindToolbar {border:none !important;}

#FindToolbar .find-status-icon:not([status="notfound"]):not([status="wrapped"]) {
display:none !important;
}

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

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

#browser-bottombox {
 position: fixed;
 bottom: 0px;
}

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

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

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

and if I use this style http://userstyles.org/styles/37366 the bar totally dissapear

and if I use this style http://userstyles.org/styles/37366 the bar totally dissapear

You can't hide the caption buttons in Aero because they're supplied by Windows DWM. The caption button IDs dert07 spoke of are the Fx supplied caption buttons. They are disabled if Aero is in use.

Concerning the statusbar: Are you using the Status-4-Eva addon?

You can't hide the caption buttons in Aero because they're supplied by Windows DWM. The caption button IDs dert07 spoke of are the Fx supplied caption buttons. They are disabled if Aero is in use.

Concerning the statusbar: Are you using the Status-4-Eva addon?

nop, using FF 4.6

You can't hide the caption buttons in Aero because they're supplied by Windows DWM. The caption button IDs dert07 spoke of are the Fx supplied caption buttons. They are disabled if Aero is in use.

Concerning the statusbar: Are you using the Status-4-Eva addon?

I do and I have it shown on hover and it does work. I only have Yahoo mail notifier in it though.

I do and I have it shown on hover and it does work. I only have Yahoo mail notifier in it though.

I know it works. I had only asked because one of the earlier versions of that add-on had moved the status bar over to the left on my system. The OP's problem was caused by trying to use Minefield scripts in Firefox b6. You can't style the add-on bar if there is no add-on bar.

I found this code

#urlbar hbox[anonid="textbox-input-box"]
{
   -moz-box-ordinal-group: 2;
}

#urlbar hbox[anonid="textbox-input-box"] + hbox
{
   margin-left: 3px;
}

#urlbar-icons
{
   padding: 0px !important;
}

To put the Bookmark Star on the left of the address bar but there's one problem, when I hover over a link, the star dissapears, anyway to fix this?

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, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. 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 in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • 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!