Thanks for the info… hadn’t realised until digging around a few minutes ago that the ‘old tab-centering code’ mentioned by OP YOUBESEENUMBA1 (above) very likely originated from your own reply post here back in May 2023! :)

Try the userstyles suggested in previous r/FirefoxCSS topic: ‘Help needed, how to change border color under the bookmarks toolbar ?’… ignore “under the Bookmarks toolbar” in title… these lines actually appear between main toolbars and the webpage Content window.

BTW - Do give BiggMurr’s reply a try… the whacked-out auto-changing border colours userstyle is a fun option… although you will need black or dark toolbars and content window to really enjoy the show!

I would download a copy of the .exe installer file to desktop and take that apart… don’t mess with your current installation.

You can open a copy of Firefox’s .exe installer file and extract the actual icon .svg or .png files too. Useful if want old icons from previous versions that used different icon design sets… sometimes these sets can be found online.

Only need 7-Zip utility or similar… open the .exe… then locate the ‘omni.ja’ file and open again with 7-Zip… search ‘omni’ folder for icons. Many folders contain icons… lots in the ‘icons’ folder itself (omni > chrome > toolkit > skin > classic > global > icons) in current Firefox stable release .exe installers.

Can view .svg icons by drag & drop file onto a blank page of Firefox (or any browser)… icons will appear ‘life size’ i.e. tiny in top LH corner of page. Can also find free online manipilation sites to modify .svg icons. Modified or 3rd-party icons can be added to browser’s profile ‘chrome’ folder along with a one-line CSS userstyle to replace the standard icon.

Er… Are you quite sure the image file names you’ve been trying were identical? No errors?

All works as expected here using both .svg and .png image files. :)

E.g. in your post above your profile chrome folder image file is named ‘fb1.png’… whilst your image file name in your userContent.css code is ‘fb1.svg’. Yes, the image file names match… but No, the file type suffixes do not match!

Tested here using a .svg image file and a new profile of Fx125.0.2 on Win10… with just the rule code copied directly from your post (above)… adding a Firefox logo .svg image file downloaded from here… placed in profile ‘chrome’ folder… then renamed ‘fb1.svg’ as per your example:

Thank you for your kind reply. :) Reading between the lines from the few exchanges you had with yawn_zz when you were leaving r/FirefoxCSS last July I had gained the impression that your relationship was likely on the minimal/curt/frosty side.

I have no objection to the community moving here or wherever else it wants to exist… my aim at present is to try and rescue all those years of previous posts so they can be searched… even if this was only as an archived sub in future.

As a first step I need to find out from u/moohorns if he has received any reply from the Reddit Admins Re: the message he sent to them a couple of days ago not long after the 2nd ‘gone private’ event had occured sometime in the early afternoon of Tuesday 23rd April… see: https://www.reddit.com/r/firefox/comments/1cafqvr/comment/l0wnif6/

Although no great shakes at CSS I am very dismayed by the sudden and mysterious demise of the r/FirefoxCSS sub… for exactly the same reasons as hansman Re: the loss of the huge body of previous knowledge contained in that sub’s years of posts, replies, suggested CSS userstyles, etc… and much other related info on the inner workings of Firefox including many suberb insights in the replies posted by MOG. :D

As hansman has posted today in the r/Firefox thread "Either way, u/yawn_zz needs to get his arse in gear, and at least make a statement - he owes the contributers of the sub that much.".

I too am at a complete loss to understand what is going on and what has triggered the two ‘gone private’ incidents?

Did the sole remaining Mod ‘yawn_zz’ really have his phone stolen and hacked 2 days ago by ‘pro-Palestinian protestors’… supposedly whilst leaving his unlocked phone with a friend during an exam? This seems an unlikely story to say the least? Exactly why would any ‘pro-Palestinian protestors’ have the slightest interest in messing with a Firefox CSS sub-reddit? So what is really going on? Has the Mod ‘gone rogue’? The lack of any statement from yawn_zz makes this more probable by the hour.

If yawn_zz didn’t want to be the sub’s Mod any longer why didn’t he just make an announcement post and walk away leaving the sub ‘abandoned’ but up and running? Why all the amateur dramatics and apparent deliberate spite?

I had cautiously hoped that posting here might prompt MOG to perhaps try contacting u/yawn_zz to find out what was going on? I was hoping MOG might have other contact details for him, having been the co-Mod of the r/FirefoxCSS sub with yawn_zz for several years. MOG would also have a much better understanding of the workings of Reddit Mod & Admin systems than me starting from ground zero. Any advice or assistance on how to proceed with a ‘rescue’ would be very welcome indeed!

I spent last evening reading-up on how users can attempt to ‘recover/reopen/rescue’ a sub-reddit that had been taken private, abandoned, or the ‘top-Mod’ has ‘gone rogue’. The answer is that the Reddit Admin methodology for doing this isn’t incredibly obvious. I also discovered that this is not the first time that the r/FirefoxCSS sub has ‘gone private’ or run into Mod problems either… see searches of ‘redditrequest’ and ‘top_mod_removal’, etc.

As reported in an update post on the r/Firefox sub topic yesterday afternoon I have applied to ‘join’ the now private r/FirefoxCSS in an attempt to discover what is happening. No reply from the Mod yawn_zz as yet. Not a huge surprise given the silly/childish/petulant/spiteful ‘PRIVATE SUB FOR STAR FOX FANS. BEST NINTENDO GAME EVER!’ notice added by ‘someone’ when the sub was taken ‘private’ for the 2nd time yesterday afternoon. What on earth is that all about?

Although I do not have deep CSS knowledge I have been interested in modifying Firefox’s UI for over a decade. I would be happy to learn how to become a Reddit Mod and take on looking after a rescued r/FirefoxCSS… however, it would be better if there were a few other Mods too (preferably stable, well-adjusted adults!) with some in-depth CSS skills! :)

Apologies… thought I’d linked and used latest version of your non_floating_sharp_tabs.css … seems not… my bad… not sure how that happened… sigh! :(

Notes on underlying cause/code changes. The only change made to the non_floating_sharp_tabs.css style between the ‘wrong/out-of-date’ 25Oct23 version incorrectly used and linked (above) and the current version is this Commit on 24Jan24: https://github.com/MrOtherGuy/firefox-csshacks/commit/a2b52b6da07f009e872aee124adf932a88c8f483.

This resulted from ‘Issue #335 - non_floating_sharp_tabs line when unfocused’ posted by corobin on 24Jan24… which links to ‘Remove opacity changes from titlebar - fixes #331’ which explains the underlying cause is the code change in Bug 1870803.

@hansman: Yes… just tested your code posted above ( #nav-bar:-moz-lwtheme { box-shadow: none !important; } ). It works! Hurrahs and BZ! (Bravo Zulu). :D

So the reappeared underline is caused by some Tab Bar coding change in Fx123.0 Re: Active Tab shadow.

Code successfully removes the new ‘Active Tab underline effect’ in both my own custom CSS profile… AND with the example used in this thread… i.e. a clean profile with just MrOtherGuy’s ‘non_floating_sharp_tabs.css’ style and NH0jNG’s Gradient Blue toolbar theme added… see new image of that combination in a Fx123.0 test profile attached below… properly ‘connected tabs’ re-established. :)

PS. Would be interested to find and read comments where this problem mentioned elsewhere Re: your comment “The issue has been discussed in a couple of other forums, seems like the code for that shadow has changed recently.”

Image. Fx123.0 test profile (non_floating_sharp_tabs.css + Gradient Blue toolbar theme) with hansman’s fix:

@hansman: Thanks for replies and CSS suggestions… will try those later today. :)

As in my reply to MrOtherGuy… none of my own CSS in use or even present in the two clean profiles used to create the 2 images… both new ‘out-of-the-box profiles’ of Firefox 123.0 and LibreWolf 122.0.1-2… with just MrOtherGuy’s ‘non_floating_sharp_tabs.css’ style and NH0jNG’s Gradient Blue theme (which I’ve used for years) added… nothing else.

Which to my logic, if not a code change in Fx123.0… that leaves the only possibility being some conflict, since Fx123.0 was released, with some aspect of the settings within the Gradient Blue theme?

@MrOtherGuy: Thanks for your reply and testing. :)

Don’t understand why the underline ‘artifact’ won’t reproduce for you? The 2 images attached are without any of my own CSS and are just “clean test profiles on Win10 with only your latest ‘non_floating_sharp_tabs.css’ style and the Gradient Blue theme added.”

Thus, unless the ‘underline’ in Fx123.0 is somehow being created by some conflict with the setting(s) within the Gradient Blue theme itself… I can’t see what could be causing the problem?

Will test again with new clean profiles just to be sure I can reproduce too! And then try your ‘non_floating_sharp_tabs.css’ style with Firefox’s default themes and a random selection of other AMO toolbar themes.

(FWIW - The Gradient Blue toolbar theme is one of the older ones and IIRC from looking at its coding a couple of years ago it is written in a slightly different format to the way a toolbar theme would be created using the latest version of Firefox Color.)

Thanks for your info “I was still using the old version, now it appears like it was before to me.”

I’d already tried hashing-out the only other piece of UE panel code I was using (to shorten the Fireshot extension’s stupidly long name in UE panel). I’ll now try MrOtherGuy’s Fx 115 UE panel code on a clean profile and work back through all my CSS userstyles… must be some curious conflict somewhere else in my CSS if UE panel compacts to same size as Fx 114 for you.

Thanks… had a feeling I’d missed some underlying change to the UE panel code/sizing. Thankfully, AFAICS, only the UE panel seems to have been “plumped” so far… other ‘compacted’ drop-down menus remain unchanged, as in Fx 114.