Not a user of 'autohide_sidebar.css'... however, on testing (new profile of Fx132.0.2 on Win10), it appears that the behaviour of the userstyle has changed after a recent Firefox update and/or a recent Commit? Was this change intended or accidental?

IIRC the userstyle's previous behaviour, when the sidebar opened on hover, was that the page Content window was resized smaller to accommodate the presence of the expanded sidebar? Thus no page content was obscured.

Using the current version of 'autohide_sidebar.css' the open sidebar now overlays and obscures part of the page Content window.

See recent r/FirefoxCSS topic 'Sideberry Autohide Doesn't Work'.

Please would you explain why adding ' > slot' fixed Issue: toolbarbuttons_in_tabs_periphery.css makes some tabs jump several by pixels when hovered, resizing of tabs is weird #419?

What underlying change in Firefox 131 made this necessary?

Similarly, why adding ' > slot' to the 'scrollbox[orient="horizontal"] selector' also fixes this old tab-centering code broken by Fx131.0 update?

#tabbrowser-arrowscrollbox:not([overflowing]){ --uc-flex-justify: center; } scrollbox[orient="horizontal"]{ justify-content: var(--uc-flex-justify,initial); }

CSS userstyle from OP YOUBESEENUMBA1's post 'Update 131.0 broke tab-centering code': https://www.reddit.com/r/FirefoxCSS/comments/1fxb0wb/update_1310_broke_tabcentering_code/

(Note. Fedia's codebox not playing... '#tabbrowser' is always displayed as an unwanted circular link to this site?)

EDIT 3 - The r/FirefoxCSS sub 'resurfaced' mid-afternoon today, Saturday 27Apr24... over 4 days after it had closed again due to the 2nd 'gone private' blackout incident triggered for unknown reasons by a person or persons unknown on Tuesday afternoon. Previous and only current Mod 'yawn_zz' reappeared alive and well and apparently back in sole control of "his" sub. Hmm? Mild flamewars and some Mod deleting of critics' and disbelievers' posts ensued.

The good news is that the r/FirefoxCSS sub's extensive and valuable back history appears to be recovered and fully searchable again. :D

No explanation(s) offered for the 2nd 4-day-long blackout period or how/who/why the silly and petulant 'PRIVATE SUB FOR STAR FOX FANS' notice got posted? Same credulity-straining story about Pro-Palestinian protestors hijacking Mod's unlocked phone offered for 1st half-day 'gone private' blackout incident last Monday. Novacula occami... "When you hear hoofbeats, think of horses not zebras"... Caveat emptor!

---

EDIT 2 - Regrettably the 'gone private' incident resumed pm Tue 23Apr24... this time with a silly 'PRIVATE SUB FOR STAR FOX FANS. BEST NINTENDO GAME EVER!' notice added... suggesting r/FirefoxCSS Mod has been hacked and is being trolled. An alternative suggestion is that sole Mod may be doing the trolling for unknown/unexplained reasons? :(

---

EDIT 1 - Gone 'private' incident over r/FirefoxCSS reappeared a short while ago after >8 hours blackout no longer a 'private' sub. Phew!

Explanation of sorts was posted by Mod at: https://www.reddit.com/r/FirefoxCSS/comments/1caovpr/why_was_this_subreddit_closed/ (this post and sceptical comments from users Re: Mod's bizarre blackout explanation was then deleted before the 2nd 'gone private' incident began. Unknown if this was just a coincidence or deliberate trolling?)

---

ORIGINAL POST - The r/FirefoxCSS sub suddenly went private this afternoon, Monday 22nd April 2024.

No warning, no discussion, no explanation.

A minor tragedy... all those years of questions and answers, thousands of CSS code snippets, and a myriad of other info about the inner workings of Firefox all now hidden from general view and no longer searchable. What a waste!

A 'private' CSS help sub is next to useless IMO. A sad loss. :(

See also: https://www.reddit.com/r/firefox/comments/1cafqvr/does_anyone_know_why_rfirefoxcss_is_closed/

A very thin line has reappeared under the Active Tab in Firefox 123.0 when using CSS to create 'connected tabs' (i.e. no boundary between Active Tab and the Nav Bar).

This line had previously been removed in my own CSS styling by using your suggested fix in r/FirefoxCSS topic 'Connected tabs - Proton Tabs Tweaks'..."That's probably solved by simply adding .tabbrowser-tab[selected]{ position: relative; z-index: 1 }" ... however, this fix no longer works in Fx123.0... and not obvious what has changed from my efforts with the Browser Toolbox?

A hint of the problem had reappeared in Fx122... in which, when the browser window did not have focus, the Tab Bar darkened AND a thin line appeared under the active tab... until window focus was restored.

(EDIT - The reappeared Active Tab underline problem only existed if using the 'out-of-date' 25Oct23 version of MrOtherGuy's 'non_floating_sharp_tabs.css' style... the problem had already been fixed... and is NOT present in the current 24Jan24 version.)

The attached image shows the same problem also exists in your 'non_floating_sharp_tabs.css' AFAICS? The LH image is Firefox 123.0 + RH image of LibreWolf 122.0.1-2. (Both browser windows have focus. Both images of clean test profiles on Win10 with only your latest 'non_floating_sharp_tabs.css' style and the Gradient Blue theme added. The UI size has been increased by setting pref 'layout.css.devPixelsPerPx' = 2.5 to improve the image clarity o the two toolbars.)

Anyone else having problems reading older comments on the fedia.io Firefox Customs pages (https://fedia.io/m/FirefoxCSS)?

Tried logged-out and logged-in... no comments on posts older than 1 month... although the index pages show many posts have comments?

However, access Firefox Customs pages via lemmy.world (https://lemmy.world/c/[email protected]?dataType=Post&page=1&sort=New)... and all the comments are available right back to first post by MrOtherGuy 5 months ago 'How to set up userChrome.css' (https://lemmy.world/post/1055304).

Am I missing some setting on the direct fedia.io page or link?

SOLVED - Problem caused by missing one asterisk (*) in a section title whilst updating MrOtherGuy's Compact UE panel CSS to Fx 115... finger trouble/PEBCAK. Apologies, and many thanks for all the help. :)

Updating from Firefox 114 > 115 the Unified Extensions panel has notably increased in size by approx 30% even when using MrOtherGuy's updated 'compact_extensions_panel: make it work in Fx115' CSS: https://github.com/MrOtherGuy/firefox-csshacks/blob/master/chrome/compact_extensions_panel.css

Additionally, attempting to reduce the icon size or line padding makes no difference whatsoever.

Has some underlying code changed in Firefox 115's UI?

(The eagle-eyed may notice the RH image is actually from the not yet updated LibreWolf 114.0.2-1)