Reasonably on which Firefox version can I upgrade to where most things are working, and how?

[mzso]

Hi!

Since this project is dormant, I wonder how can I get it to work with later Firefox version. I see people sharing code sometimes, but it's all around.
Are @AlexVallat's changes good for 142, for XUL addons and uc scripts? Are they good for later than version 145?

Do all of the half-dozen or so addons works? I'm interested in Keyconfig, Downthemall, Backtrack Tab History and Advanced Locationbar.

Any other fixes around for this loader?

[AlexVallat]

My changes (which, to be accurate, are changes shared by others that I have just integrated) should be good to Firefox 147. I run Developer Edition, and that's my target to keep working.

Currently Backtrack Tab History is not working with 147, but I'm working on it. Unless it turns out to be impossible, I will update with a fix when I can.

Uc scripts should be working in general. If there's a specific uc script which does not work you can post an issue about it.

[AlexVallat]

I think BackTrack Tab History v0.41 should be compatible with Firefox 147 now.

[mzso]

@AlexVallat Thanks! I will try it.
Did you try any of the other XUL addons?

[AlexVallat]

@mzso No, but proves it is at least in principle possible to load legacy addons. Each addon may require individual fixes to make it work, so if there isn't an active maintainer for the addon you are interested in then it will probably stop working eventually. As with the scripts, if a specific addon doesn't work for you, post an issue for it and hope for the best!

[mzso]

@AlexVallat
So I've been testing it in portable devedition 147, but the addon won't load with the "This add-on could not be installed because it appears to be corrupt." error.

I think I did anything right. got the util/fx-folder zip files from your repo (At first I followed the link, which linked to this repo...)
Then grabbed rebuildrebuild_userChrome.uc.js, and placed it into the chrome folder.
I get a blank icon which is the script menu. I get a windows icon (for some reason), which is the extensionOptionsMenu.uc.js icon apparently (used to be a blue puzzle piece). Also chrome://userchromejs/content/aboutconfig/aboutconfig.xhtml works, after I added it files. (edit: well, mostly. The search field doesn't)
But not Backtrack. Am I missing something?

[mzso]

@AlexVallat
Hm. I could Install @117649 / AdvancedLocationbar2 and it works.

So I guess the problem is with the addon.

No the problem was with me... I botched downloading the file.

However I do notice something strange. I get both a new tab and a new windows opened after Backtrack was installed on every startup, with the url https://example.com/?tab and https://example.com/?window:

[AlexVallat]

Hmm, weird. MD5 of the addon xpi should be a4b54e9d96387cfe352ccd49c0defaad, if it's not that, then it's really corrupt...
Ninja'ed

To answer your other question, those windows should appear once and then never again, after the parentClickTimeoutTab and parentClickTimeoutWindow prefs have been set (they are used to calibrate the speed at which tabs and windows open on your system).

You could try setting them using the BackTrack options page (the "New child window time (ms)" and "New child tab time (ms)" settings, or if all else fails, set them in about:config as extensions.backtrack.parentClickTimeoutWindow and extensions.backtrack.parentClickTimeoutTab.

Reasonable values are about 1000. Increase them if new tabs/windows are not properly being parented to their opener. Decrease them if a new tab/window is improperly being parented to the last tab you had open before manually opening a new window or tab.

[mzso]

@AlexVallat It seems like the options page is missing:

Setting via about:config works. And now the inheritance started working as well.

[AlexVallat]

Should be accessible through the menu:

Or by clicking on the extension in the extensionOptionsMenu.

[mzso]

@AlexVallat Ah yes... I guess I used CustomCSSforFx for so long I forgot, unless it's a new thing. Also adv. locationbar had it exposed, which gave me a false impression.
Well, that's two out of five working. My hopes are not as good for DTA, custom buttons and keyconfig. (Also styloaix, and old about:config)

[robbely]

@AlexVallat Any chance you could get DownThemAll working? That one has been broken for some while and didn’t get an annual update for the latest ESR release

[AlexVallat]

No, I don't want to be the maintainer for DownThemAll, I don't use this addon. Dimdamin would seem to be your best bet: #329 (comment)

[robbely]

No, I don't want to be the maintainer for DownThemAll, I don't use this addon. Dimdamin would seem to be your best bet: #329 (comment)

That's fair enough - thanks

Edit: dimdamin has solution here #336 (comment)

[mzso]

Well, eventually I only upgraded to 135. Seems like v136 broke all/most addons. Only Backtrack, DTA, Advanced Locationbar (maybe custom buttons for a few more versions) was upgraded. Losing Keyconfig, and Custom Buttons would be quite a heavy loss. Also losing StyloaiX would require screwing around with CSS files manually and restarting every single time to see the change.

On ever sadder news, CustomCSSforFX is now abandoned, and knowing Mozilla, most of the CSS will be broken soon.

[TFWol]

Uc scripts should be working in general. If there's a specific uc script which does not work you can post an issue about it.

@AlexVallat would you be willing to fix up the MouseGestures script?