uc.css.js VS aboutconfig

I'm using this script which enchances the all tabs menu functionality of FF.

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

Yes. It is possible, but you will have to set up a JavaScript loader. See this GitHub page for more info. 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

I'm glad they're making changes, but I'd advise everyone to watch closely what they end up implementing and what potential security and privacy risks will be introduced. It seems like I'm having to disable something or other with every major update of firefox lately, and as long as they continue to let me disable risky features I'll keep using it. Nothing strikes a better balance between useful and secure like hardened firefox, but it takes a lot of vigilance and a willingness to add or modify hundreds of about:config options (after installing https://github.com/earthlng/aboutconfig)

Therefore I now use this, which gives me the traditional layout and functionality: https://github.com/earthlng/aboutconfig

from an autoconfig script you can call registrar.registerFactory(CID, className, contractID, factory) and set up the same kinds of objects that firefox does. I haven't explored this that much, so far only used it to create a new about: page. if you wanna see that example here's the link. it's just a regular autoconfig script, but of course it needs some html for that new URL to lead to.

In this example we're just assigning the URL about:cfg to earthlng's pre-87 aboutconfig module. Its path would normally be something like chrome://userchromejs/content/aboutconfig/config.xhtml, which isn't perceived as a system page and is a bit of a nuisance to type in the urlbar. Shortening that particular url and making it fit in like a genuine system page would was my main reason for looking into this, but it could conceivably be done with any URL. local files, extensions, etc. The new URL even shows up in about:about which is pretty cool.

the page is no longer present, so need an integration (https://github.com/earthlng/aboutconfig)