earthlng / aboutconfig Goto Github PK

Services.jsm has been removed so I think your script will throw when it tries to import it. It should be fine to remove the import since it's in the global object for privileged page scripts. Cheers!

https://bugzilla.mozilla.org/show_bug.cgi?id=1780695

I already have xiaoxiaoflood's usrChromeJS 'protocol' installed so the only required step in this case is to add the aboutconfig folder to the user's profile/chrome/utils folder. For whom may be concerned ...
Nice to get back that old about;config format. Nice work, appreciated. Thanks @earthlng

I recently found a way to register a new about: URL and figured it'd be a pretty good match for this. I just registered your config document to about:cfg, which looks a bit fancier than a long chrome:// path — here's the script. Apologies if you already knew about this and passed on it. If you want to include it, it's pretty simple. The script contents can just be appended to the end of your boot.jsm file. But you can just replace findAboutConfig() with chrome://userchromejs/content/aboutconfig/config.xhtml if you don't care about supporting other possible chrome paths/autoconfig loaders.

I typed about:cfg, but it was all white. I checked all the steps myself and they are correct.
Device: Windows 10 Chinese
Tested on Firefox tete009 106.0.5 Chinese and Mozilla Firefox 106.0.5 Chinese, both failed.

So, yeah, ummm..... I don't know what they did this time, but with version: "107.0a1 (2022-09-30) (64-bit)" all I'm getting is the warning page:

But when I click "I accept the risk!" , nothing happens....
🥺

So, when I try to open chrome://userchromejs/content/aboutconfig/config.xhtml , my Nightly version 101.0a1 (2022-04-07) (64-bit) gives me a "File not found" error.

Did Mozilla change something, that made even the workaround method dead?

Loading chrome://userchromejs/content/aboutconfig/config.xhtml
Now gives:

Clicking on "I accept the risk!" does nothing.