fx-autoconfig VS firefox-scripts

I'm using your https://github.com/MrOtherGuy/fx-autoconfig

Basically what the title says. I have some JS code I'd like to automatically run in a specific moz-extension:// page. In particular, I'm interested in Sidebery's moz-extension://*/sidebar/index.html, but I suspect the answer would be the same for any page. I tried writing a userscript with MrOtherGuy's fx-autoconfig, but to no avail: I can successfully run userscripts in chrome://browser/content/browser.xhtml, but if I add

If not possible with CSS, will JS work making them draggable? I found several JS draggable buttons at https://github.com/MrOtherGuy/fx-autoconfig

copy config.js from https://github.com/MrOtherGuy/fx-autoconfig/tree/master/program > C:\Program Files\Mozilla\Firefox

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.

Run it as userChrome.js

I'm currently using a customized version of Aris-t2's CustomCSSforFx theme, along with /u/It_Was_The_Other_Guy's fx-autoconfig loader for JavaScript. My setup uses the option to put the application menu button in the title bar. In the versions that had this as standard, the menu button disappeared when the menu bar was shown. Is there a way to recreate this with either CSS or JavaScript?

Why Use CSS Alone Though

For a long time, I've been making use of a MacOS-esque scrollbar I found online. I'm using XiaoXiaoFlood's loader script, and I've made the necessary changes to the files mentioned here to make it able to load .js and .uc.js files again. I've also modified the script a fair bit, though reverted most as it didn't work. Currently, I'm using this one, which has simply commented out the things that rely on Services. Though, even if I add it with something like const Services = globalThis.Services || ChromeUtils.import("resource://gre/modules/Services.jsm").Services; it doesn't make much of a difference. I've also tried using a userChrome.xml file, but that doesn't do much anymore. Was around 72/75 where that stopped working right?

Though for the full value I personally really also need some sort of interface that can show individual page visits in order to answer the question "What other pages did I visit at that point in time?" (sometimes I don't remember the right keywords to find a certain page again, but only some other page I visited during the same browsing session). The built-in history view is only of limited value here, because it always only shows the most-recent visit, so as soon as you visit a page again, it moves to the front of the list again and loses its original place and history context.

As usual, there used to be an add-on for that, which was subsequently broken by the move to webextensions (and even if somebody wanted to rewrite it, the webextension API doesn't cater for its full functionality). Thankfully some kind soul has maintained a version hacked to still work even on a current Firefox (https://github.com/xiaoxiaoflood/firefox-scripts/tree/master...).

This is what you're looking for.

Heads up though, it doesn't work for most tooltips. For that, I found the only way to change them is to use the above code in an agentsheet (https://github.com/xiaoxiaoflood/firefox-scripts, see the "StyloaiX" section)

Bootstrapped extensions are supported (really, xiaoxiaoflood is the only one who maintains any popular ones).

depending on your needs existing extensions may work for you, though the ContentScript based implementations have issues, if that's not enough you can use https://github.com/xiaoxiaoflood/firefox-scripts as it allows you to run the code in the browser UI, unfortunately there's no easy to use extension (and sadly FireGestures require update to work, even with loader injected into Quantum) so you may need to work with the code a bit (or more)

do what exactly? inject code? there are many slightly different approaches, the most reliable seems to be https://github.com/xiaoxiaoflood/firefox-scripts and using an approach like that forks can add extra configs to the UI making users' lives easier

Not in the foreseeable future, but maybe achievable with userChromeJS.