Firefox-UI-Fix VS uc.css.js

I use Lepton and i'm perfectly happy with the improved usability and readability. Also, easy to install : https://github.com/black7375/Firefox-UI-Fix

I've never used their actual project, but I really like the article they wrote covering Firefox UI changes over time (you can find it under the wiki pages of the repo) - https://github.com/black7375/Firefox-UI-Fix/wiki/%5BArticle%...

Mozilla has made significant UI changes every 3-4 years, with the last one being in 2021. Perhaps we're about due to see another?

I use Firefox with the excellent https://github.com/black7375/Firefox-UI-Fix I discovered on HN.

I wish that Mozilla didn't bungle the UI for no reason, but here we are.

Highly suggest checking out Firefox-UI-Fix [1]. I use it everywhere I use Firefox, and it makes the browser usable.

[1] - https://github.com/black7375/Firefox-UI-Fix

I use Sidebery, with some modifications from https://github.com/black7375/Firefox-UI-Fix/wiki/Options

Well, that's one more reason not to use Edge. Firefox's current design is terrible. Who thought that making tabs buttons was a good idea? Thank goodness for Firefox-UI-Fix.

And someone made an easy-ish to install UI fix to stop it looking like ass: https://github.com/black7375/Firefox-UI-Fix

Lepton, Firefox-GX, SimpleFox, Cascade

Firefox UI Fix can revert you to the old UI theme! First thing I install on a new installation of Firefox

Woah, this is nicely packaged. Even has "Releases"! Thank you! https://github.com/aminomancer/uc.css.js

UI customization is fortunately still alive in the wake of XUL extensions.

A /r/firefoxcss mod has a wonderful collection of code snippets that they maintain, which you can browse here: https://mrotherguy.github.io/firefox-csshacks/ and they created a userChrome.js loader here: https://github.com/MrOtherGuy/fx-autoconfig

My favorite customization repository is https://github.com/aminomancer/uc.css.js - which really tests the limits of what is and isn't possible with userChrome.css and .js. My favorite feature is the implementation vertical tabs, without the use of extensions.

Some legacy extensions are maintained and can be found here: https://github.com/xiaoxiaoflood/firefox-scripts/tree/master... (although you will need to use xiaoxiaoflood's userChrome.js loader AFAIK).

Honorable mention goes to the Firefox CSS Store, which can be found here: https://trickypr.github.io/FirefoxCSS-Store.github.io/

Moving to WebExtensions was the logical choice for Firefox, technical/security reasons aside, as they are not alienating extension developers that target Chromium-based browsers.

Yes, they alienated their own extension developers. Yes, they could've handled the transition better, and worked harder towards supporting some of the many APIs/functionalities that extension developers needed (or still need) for their extensions to work in the WebExtensions ecosystem. I myself was quite mad for a very long time at how they handled the switch, but I think overall it's been a success - my own personal feelings aside.

Linux support is pretty good these days and it's just as customizable as Vivaldi. See this repo for an example: https://github.com/aminomancer/uc.css.js

Only possible with JS: https://github.com/aminomancer/uc.css.js/blob/master/experimental/bookmarksPanel.uc.js

Oh, you can't use xiaoxiaoflood's autoconfig loader for this. It's for fx-autoconfig, like I said in the first post. You should not be combining the two either, that's a really bad idea. Anyway, xiaoxiaoflood's status-bar.uc.js file does not have -moz-window-dragging in it in the first place. Maybe you have an old version of it. It was updated Nov 22, 2021, so that seems likely. This is why I keep version numbers in all my scripts.

idk how many of the child elements you're showing. it appears none. if that's not the case, then you can try copying stuff from my sheet.

Hi eric, looks good. I have an update you're probably interested in. If the inconsistent tooltips of the window control buttons (close/min/max) are bugging you, I made this script to fix it. I don't think this issue has hit release builds yet but will soon. Basically the buttons get an attribute that causes them to not display tooltips at all, rather it defers to the OS to draw the tooltips. It's from bug 1718629. But anyway, just recreating the buttons without the attribute fixes it.

Try using my agent sheet loader. Make sure you move userChrome.ag.css to your main chrome folder, mine is looking for it there, not in the resources folder.