Running in Firefox Release #83
Comments
|
You need Firefox Developer or Nightly to run the extension because it bundles unsupported APIs ("API experiments"). Have a look at the README for the requirements. |
|
You mean firefox release won't allow it even as a temporary addon? Is there any way to get it to run in firefox release? Hack omni.ja to disable addon signing? |
I believe so. You may need to dig around in the source code to see where exactly it's getting blocked. The error you're seeing ( |
|
Yes you are right. It's disabled from here https://searchfox.org/mozilla-central/rev/014fe72eaba26dcf6082fb9bbaf208f97a38594e/toolkit/mozapps/extensions/internal/AddonSettings.jsm#93 This works! https://github.com/xiaoxiaoflood/firefox-scripts There's nothing really in that zip file. Just a configuration line to disable addon signing checks. It still warns if the addon is unsigned. Then paxmod works in Firefox release too! Could you add this to your README so that release users can also enjoy your addon? Thanks! |
|
|
|
Thanks for looking into this, and great you found a solution! I find fiddling with installation files a little awkward and potentially prone to new issues, so I'd rather want to explore some alternatives before recommending this workaround. However, I'll leave the issue open, and it's really helpful that you pointed out the general approach to bypassing the signature requirement. |
Needs to be set before installing paxmod in a fresh profile or fresh install. Otherwise it doesn't work. If you installed 8000 it before enabling the preference in about:config, you should uninstall the addon, enable the preference and then install it again. (A restart of firefox after changing the preference may be required) |
|
It's a real shame that addons like this https://addons.mozilla.org/en-US/firefox/addon/native-ext/ which can make full changes to the entire system are signed and allowed, but modifying the chrome ui is not allowed! This extension allows the restyle extension ( https://addons.mozilla.org/en-US/firefox/addon/re-style/ ) to modify the tab bar etc, by modifying userchrome.css, although a restart is required everytime. Go figure! 🙄 |
|
So - I am trying to re-enable paxmod in Firefox Release (v90) running on Ubuntu 20.04. It used to work fine until firefox updated (don't remember what the last version was). However, since I've uninstalled paxmod, I am unable to install it from file because unsigned extensions are not supported in release: https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox?as=u&utm_source=inproduct. (the recommended config options in the README are set, but it seems they are not checked by the release version). I am able to try to load it as a temporary extension, but I still get the exception mentioned in the first post: So - where would I unzip that zip file on a linux system? |
|
Please see this if it helps xiaoxiaoflood/firefox-scripts#8 (comment) |
|
@mavink - thanks - I adjusted the paths and put unzipped fx-folder.zip and moved the files in the correct folders, restarted Firefox release, unchecked and reenabled the two settings (xpinstall.signatures.required = false and extensions.experiments.enabled = true), tried to load paxmod, but it still complained that it is unsigned. If I try to load it in debug mode it complains about I'd like to ask - it's unlikely to get it to install in newer FF releases, right, since it's (and will remain) unsigned? Or will it get signed once the APIs used are mature enough not to be experimental anymore? Thanks! |
@mad-ady Yes, it's very unlikely that add-ons like this one will get signed by Mozilla. You'll always need some workaround to get unofficial add-ons installed. If you're going through all the trouble to get it installed, why not just switch to FF Developer? It's basically FF Beta with a few extra features and works just fine with the README instructions. |
|
Thank you! I think I'll have to make the switch. I can't live with a single
row of tabs, like a barbarian...
…On Wed, Jul 28, 2021, 03:41 Arminius ***@***.***> wrote:
I'd like to ask - it's unlikely to get it to install in newer FF releases,
right, since it's (and will remain) unsigned? Or will it get signed once
the APIs used are mature enough not to be experimental anymore?
@mad-ady <https://github.com/mad-ady> Yes, it's very unlikely that
add-ons like this one will get signed by Mozilla. You'll always need some
workaround to get unofficial add-ons installed.
If you're going through all the trouble to get it installed, why not just
switch to FF Developer? It's basically FF Beta with a few extra features
and works just fine with the README instructions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#83 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAO6KX7XOPRLZFJUPNFBBTTZ5G4XANCNFSM47LIFZNQ>
.
|
|
In case it does not work in FF release especially after v108.
|
|
Okay fixed the issue once more. The unsigned addon install feature was suddenly removed from https://github.com/xiaoxiaoflood/firefox-scripts maybe by mistake. See xiaoxiaoflood/firefox-scripts#324 After installing the latest firefox-scripts replace the config.js file with the one attached here (remove the .txt extension) Ensure Restart firefox after replacing config.js. Clear the startupcache in about:support. Restart again. Only after this install paxmod from file or from github. If you already installed then uninstall and reinstall. You can install tabmixplus also. Everything works perfectly. Beautiful rounded tabs with a nice black border and the newtab button from paxmod. and active/inactive tab colours from tabmixplus.
|
|
Use any webextension addon? |
|
No APIs available to modify userchrome.css and the tab bar via webextension. Need to access privileged APIs I think |
No. I hope you understand why sign check can't be disabled by default now |
|
It can be disabled by adding the following code as mentioned here xiaoxiaoflood/firefox-scripts#324 |
Why wont this run as a temporary addon in Firefox release about:debugging?
On startup there is an uncaught type error in browser.stylesheet and again when I try to change something in the options and apply it.
This is a fresh profile with no other extensions. Nothing changes in the tab bar even on applying the options.
The text was updated successfully, but these errors were encountered: