web-ext VS fx-autoconfig

> I hope FF gets service workers going soon

As of October 2022, that’s “not planned”:

https://github.com/mozilla/web-ext/issues/2532

Yes, web-ext https://github.com/mozilla/web-ext does this.

Anyone used this and could compare/contrast with https://github.com/mozilla/web-ext ?

> On a side node, if anyone has resource about how to dev/debug userscript properly, I'm all ears. I found it super inconvenient and tedious when doing it myself, and I often have to manually copy paste stuff back and forth.

Develop it as an extension with the script as your content_script, and use web-ext [1] to run it. You can then develop in your regular editor, use your browser's extension debugging tools, and web-ext will automatically reload it when you change stuff.

Most of my extensions use a .user.js file as their content_script, which I can also publish directly to Greasy Fork.

[1] https://github.com/mozilla/web-ext#web-ext

https://github.com/mozilla/web-ext and web-ext-submit

The sole way is to use the official node.js* tool https://github.com/mozilla/web-ext

You should set up and use the tool web-ext by mozilla, so you can run it locally while developing.

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