its time for new readme

[117649]

An example that may be helpful But anyway most important part should be get user understand how to install bootstrap loader.

[onemen]

Are there any special instruction on how to create xpi file from the source ?

[117649]

Are there any special instruction on how to create xpi file from the source ?

No. I just pack them as .zip then change the file name.

[117649]

Are there any special instruction on how to create xpi file from the source ?

@onemen One thing is you should use robust and well tested tool to compress the .zip that can be properly decompressed by different tools and on different OS.

One bad example is the zip compress module of the default powsershell version of win 10. The zip file it generated can only be decompress by and on Windows with compress manager tool. Don't use it.

You've been quiet for a while hope you're all well.

[onemen]

I'v just published the first development build. https://github.com/onemen/TabMixPlus/releases can you test how it work

[onemen]

also check the new RADME

[117649]

I'v just published the first development build. https://github.com/onemen/TabMixPlus/releases can you test how it work

also check the new RADME

Of course.

[117649]

@onemen The content of this page are vital to the installation and hard to find. https://github.com/xiaoxiaoflood/firefox-scripts/blob/master/extensions/bootstrapLoader/README.md Better just include it in TMP's README.

[onemen]

I already have this link https://github.com/onemen/TabMixPlus/blame/main/README.md#L28-L29

[117649]

I already have this link https://github.com/onemen/TabMixPlus/blame/main/README.md#L28-L29

Well those two prefs are still needed if using chrome script as far as I know. Without the them Firefox won't allow install legacy .xpi at all.

[117649]

And some small UI problem(The help button):

[onemen]

Well those two prefs are still needed if using chrome script as far as I know. Without the them Firefox won't allow install legacy .xpi at all.

config.js lock xpinstall.signatures.required you don't need this pref for chrome script extensions.experiments.enabled

[117649]

Well those two prefs are still needed if using chrome script as far as I know. Without the them Firefox won't allow install legacy .xpi at all.

config.js lock xpinstall.signatures.required you don't need this pref for chrome script extensions.experiments.enabled

Ok, just tried it you are right.

[117649]

I have this one record confirms that set xpinstall.whitelist.required=false helps 'file corrupt' error. https://dm.reddit.com/r/FirefoxAddons/comments/pm53qx/github_onementabmixplus_at_v100pre1/hcjn36a/

[onemen]

I have this one record confirms that set xpinstall.whitelist.required=false helps 'file corrupt' error. https://dm.reddit.com/r/FirefoxAddons/comments/pm53qx/github_onementabmixplus_at_v100pre1/hcjn36a/

Can ask @xiaoxiaoflood if it xpinstall.whitelist.required=false setting can be part of bootstrapLoader and firefox-scripts? If not i can add it to our README.md

[117649]

Can ask @xiaoxiaoflood if it xpinstall.whitelist.required=false setting can be part of bootstrapLoader and firefox-scripts? If not i can add it to our README.md

I think you can open issue on https://github.com/xiaoxiaoflood/firefox-scripts/issues . In my opinion it not seems very realistic. bootstrapLoader need setting prefs itself firefox-scripts actually use config.js which is user editable, and Waterfox haven't update loader for quite a while.

Add a troubleshoot section to README.md is faster and easier.

[yakoder]

Suggestion: making it more clear as to which version of userChromeJS is needed. Assumed "extension-only" and TMP didn't show up in the Addons list (and, although moot point & unsure what did it, with ESR 78 nothing was showing up in that list, but got ESR 91.1 today & had to redo everything). If only "utils → I'm only interested in extensions" version of userChromeJS is installed, TMP seems to function, but no options. I tried the "utils → I'm interested in both scripts and extensions" version, and TMP seems happy happy.

I would've just cleaned that up a bit & did a PR, but it is sounding like a few others are already working on the README.

[117649]

Suggestion: making it more clear as to which version of userChromeJS is needed. Assumed "extension-only" and TMP didn't show up in the Addons list (and, although moot point & unsure what did it, with ESR 78 nothing was showing up in that list, but got ESR 91.1 today & had to redo everything). If only "utils → I'm only interested in extensions" version of userChromeJS is installed, TMP seems to function, but no options. I tried the "utils → I'm interested in both scripts and extensions" version, and TMP seems happy happy.

I would've just cleaned that up a bit & did a PR, but it is sounding like a few others are already working on the README.

Well, In fact it not like that. The different between that two .zip is only a module to load userCustomJS file. It more likely because your update wiped all cache. If TMP option not show refresh Add-ons Manager page should just do it.