I still need this one! Noté 5 sur 5 étoiles

I love it, because it's the only module I've found that forces addon compatibility, allowing me to use non compatible addon! But I don't need other feature, I would prefer a light version.

Cette critique concerne une version précédente du module (3.9).  Cet utilisateur a une revue précédente sur ce module.

How to force addon compatibility (but only in Trunk aka a1 builds) without NightlyTT

On trunk builds (i.e. currently Firefox 55.0a1, Thunderbird 55.0a1, SeaMonkey 2.52a1) you can force add-on compatibility without needing any add-on for it by creating in about:config (or in the Thunderbird Config Editor) the boolean preference extensions.checkCompatibility.nightly with the value false. This pref does not exist by default.

The Mozillazine Knowledge Base article http://kb.mozillazine.org/Extensions.checkCompatibility is relevant but possibly out-of-date: IIUC the pref has been removed from all builds other than trunk (i.e. a1) ones.

Warning: Trunk builds are the "bleeding edge" of development, they contain many experimental features which have only been little tested if at all, and they are the buggiest ones. Use at your own risk. They can be downloaded from:
In all cases, scroll down until you come to the highest-numbered version for the OS you are using.

Of course, all the above won't let you benefit from other features of Nightly Tester Tools, such as easily pasting into a bug comment or copying into the clipboard the exact User-Agent, Build ID and Mercurial changeset ID of the browser or mailer you're currently using.

Screwed Things Up! Noté 1 sur 5 étoiles

"Use comma between entries when copying the list of extensions (#195)"

You just screwed this up big time. Without the commas, I could add the list of extensions into an Excel spreadsheet. I used the spreadsheet to compare my various profiles across my computers.

Now, because you made this change after all the YEARS that NTT has been around, I now have to work around this if I am going to maintain my spreadsheet.

I’m guessing you never stopped to consider how this change was going to affect those of us who have been using NTT all these years before acting on it. Thanks a lot.

Reply: Incorrect! All I needed to do prior to this change was Ctrl+V to paste the list of extensions into Excel.

I do not import which is what you are talking about. I pasted. I can't do that now because the entire list goes in one (1) cell rendering things worthless.

Again, you failed to consider the unintended consequences of this change before making it.

Cette critique concerne une version précédente du module (3.9).  Cet utilisateur a une revue précédente sur ce module.

The problem here is not that we are using comma now, but the way how you import the data into Excel. It means there is always a way to import as CSV which let you specify the separator between entries. So once you selected comma all is still working and no extra work has to be done.

Seit FireFox V. 48.x unbrauchbar - funktioniert nicht mehr Noté 1 sur 5 étoiles

Leider funktioniert dieses bisher sehr gute AddOn ab Firefox V. 48.x nicht mehr!
Ursache ist die Modifizierung von Firefox betreffend Richtlinien in Sachen AddOns.

Abhilfe gibt es keine, außer sich nach aktuellen oder ähnlichen AddOns umzusehen, welche man nicht mittels
"Nightly Tester Tools" freischalten muß.
Man kann somit getrost unter Firefox 48.x "Nightly Tester Tools" deaktivieren, oder gleich deinstallieren.

Cette critique concerne une version précédente du module (3.8). 

Danke für das Feedback. Ich hätte jedoch noch eine Frage, da die Funktion, die hier angesprochen wird, nicht Teil von NTT ist und auch nie sein wird.

Mit Firefox 48 sind signierte Add-ons vorgeschrieben. Daran kann auch NTT nichts ändern. In den Release-Versionen kann die Überprüfung so halt nicht deaktiviert werden. Firefox blockiert es einfach. In nightly Builds sollte es noch möglich sein, hierzu nehmen wir gern einen Feature-Request entgegen: https://github.com/mozilla/nightlytt/issues

Es ist jedoch unfair, eine Bewertung über eine Funktion abzugeben, die bis jetzt nicht unterstützt wird.

addon compatibility does not work in FF 48 Noté 1 sur 5 étoiles

The option to disable addon compatibility checking does not work in Firefox 48.

Cette critique concerne une version précédente du module (3.7.1-signed.1-signed). 

We are currently preparing a new release of NTT. It will be available in the next couple of days. It will fix this and other issues.

Update: Would you mind testing NTT again? It was fixed in version 3.8 and over the weekend we already released 3.9. Thanks.

Noté 5 sur 5 étoiles

Good way to force the installation of incompatible extensions.

Cette critique concerne une version précédente du module (3.7.1-signed.1-signed).  Cet utilisateur a une revue précédente sur ce module.

Not working Noté 1 sur 5 étoiles

All the features seems awesome but I can't manage to find them anywhere. No menu under the main menu, neither under Tools menu and no options button in face of the add-on in the manager so I don't know how to configure it.
I'm using Pale Moon 25.2.1 (x86) under windows 7.
Thanks again.

Cette critique concerne une version précédente du module (3.7.1-signed.1-signed). 

Forced Ghostery to start working again in Firefox 35 Noté 5 sur 5 étoiles

Had no icon or features for ghostery until I used this addon

Cette critique concerne une version précédente du module (3.7.1-signed.1-signed). 

Noté 5 sur 5 étoiles

I just use this extension to disable extension capability checking. I'm sure it's more powerful than that, but it does what I need and it light and simple. 5 star.

Cette critique concerne une version précédente du module (3.7.1-signed.1-signed). 

tested few weeks Noté 5 sur 5 étoiles

OK, thank you for answering.

Like I said, I have tested your add-on for a few weeks with different add-ons and browser crashes. After first install, I had some problems but I think it was my fault because I didn't know how to use your add-on properly. I had only two times Firefox crashes (Aurora). I HAD before installed your add-on very often crashes (especially when Firefox reached 700 MB to 1,5 GB memory usage). I think that your add-on helped to make Firefox more stable?

I will use Nightly Tester Tools. I'll report if I've issues. For now, it works great. 5 stars for your add-on.

Cette critique concerne une version précédente du module (3.7.1-signed.1-signed).  Cet utilisateur a une revue précédente sur ce module.

Crash reports

Hello. As you are mentioning a lot of crashes I'm highly interested in those reports. Would you mind to let me know about those urls? You can find them when opening about:crashes in Firefox. Please send me a couple of those to hskupin(at)mozilla(dot)com. Thanks.

Muito Bom ! Noté 5 sur 5 étoiles


Cette critique concerne une version précédente du module (3.7.1-signed.1-signed). 

I guess it would have to work differently to do what I want Noté 3 sur 5 étoiles

I was hoping that NTT's title-bar editor would do what I want, but it doesn't, so probably the only feature I'll really use (not actually being a nightly tester, just beta) is the "force compatibility" tool, in order not to keep losing add-ons every time I update to a new Beta release number. The other tools do look useful for people who really are living on the Firefox edge.

What I was *hoping* the title-bar editor might do was allow me to customize the title *individually* for each of my open windows. I've lately been trying to use separate windows to group related tabs (e.g. a "social" window for Facebook and LinkedIn tabs, a "work" window for things I'm currently researching for work, etc.). I often have several hundred tabs open (lots of "I'll get back to that"s that never happen...) but it's hard to keep track of what's where when each window just shows the title of the current web page. And no, Firefox's own "tab groups" feature won't do what I want, and I hate, hate, hate that interface. (Clustering *actual* tabs or expand/collapse *actual* tabs would be the way to go -- not a gazillion thumbnails.)

UPDATE -- 25 Feb 2013: Loss of 1 star, from 4 to 3.

I just had my first occasion to try using the "Force Addon Compatibility" feature, when FF updated itself from Version 19 to Version 20 Beta 1. (Does anyone else find it absurd that we're up to "FF 20" with essentially the same product as FF 7? Or is it FF 5?) As a result of the update, my "Tab Utillities" add-on was disabled as being "incompatible".

I saw a warning about the Tab Utilities add-on before I actually applied the update, so I turned on "Force Compatibility" before updating FF. No joy -- the add-on was still disabled after the update. So I turned off the Force Compatibility, then turned it back on and accepted a re-start. Still no joy, the add-on continues to show as disabled. So, as far as I can tell, the Force Addon Compatibility feature doesn't work. Since that's the only feature I was expecting to use, I've deducted one star.

What does work (sort of), in place of NTT, is the trick COKEDUDE posted below, updated. I added

extensions.checkCompatibility.20.0 FALSE

to about:config. Now I can fiddle with Tab Utilities options, but it doesn't seem like Tab Utilities actually WORKS even with that new Config line.

(As a feature request for more serious testers than me, I wonder if forced compatibility could be managed on a per-add-on basis. Someone doing serious testing might want to activate just one "incompatible" add-on at a time to see if they actually work.)

Cette critique concerne une version précédente du module (3.3.1-signed.1-signed). 

Indeed, the title customization is, at the moment, common to all windows. Your request looks interesting, though. Maybe you could open a new "enhancement" issue at https://github.com/mozilla/nightlytt/issues/new

P.S. See also https://github.com/mozilla/nightlytt/issues/63

P.P.S. "Cokedude's trick" is documented at http://kb.mozillazine.org/Extensions.checkCompatibility

Setup Info Noté 5 sur 5 étoiles

I found out why. About:config is missing this line. Set it to false

Then install whatever you want.

Cette critique concerne une version précédente du module (3.3.1-signed.1-signed).  Cet utilisateur a une revue précédente sur ce module.

Noté 3 sur 5 étoiles

I love this addon! BUT.....I don't seem to be able to get it to work in Firefox 16.0.2 running on Ubuntu 11.10 :-(

Cette critique concerne une version précédente du module (3.3.1-signed.1-signed). 

Need feedback

Reporter, thank you for your review, but it's not clear to us what's not working for you. We should appreciate any kind of feedback which will help us to identify the problem and get it fixed.

Noté 5 sur 5 étoiles

Great for Titlebar text, 5 stars

Cette critique concerne une version précédente du module (3.3.1-signed.1-signed). 

Noté 5 sur 5 étoiles

Fantastic little addon!! .... Is there somewhere I can download it and save it to my PC in case Firefox outdates it lol

Cette critique concerne une version précédente du module (3.3.1-signed.1-signed). 

LOL. The "stable" version of this addon is, and will remain, here at addons.mozilla.org. Now that Firefox, Thunderbird and SeaMonkey are equipped with a "default to compatible" feature, it is expected that NTT won't become "outdated" by any foreseeable future version of theirs, though new NTT versions will of course be uploaded to fix bugs and/or add features.

The development source is on github (see the link on the "addon home page"), you will normally not need it unless you want to add features and/or help fixing bugs.

Until the next version... Noté 5 sur 5 étoiles

To force addon compatibility in Firefox 8 you must have to:

Type about:config in Firefox addressbar and press Enter. It'll confirm, click on "I'll be careful, I promise!" button. Now right-click and select "New", then "Boolean". Give it name:


And set it's value to false. That's all.

This is the same thing that NTT does with your browser, but it always changes the version number automatically to match the browser's version. That's why I gave it five stars.

Cette critique concerne une version précédente du module (3.2). 

Noté 4 sur 5 étoiles

What they said, not compatible with Firefox 8. Tried to find your e-mail, but to no avail.

Cette critique concerne une version précédente du module (3.2). 

Noté 3 sur 5 étoiles

Same here, not working anymore. Plsssss!

Cette critique concerne une version précédente du module (3.2). 

Noté 5 sur 5 étoiles

Force addon compatibility is not work with FF8.

Cette critique concerne une version précédente du module (3.2). 

Broken Noté 2 sur 5 étoiles

Firefox 3.6.23 on Solaris 10 SPARC system

I agree with QueenOfStars writing on August 24, 2011

"the version numbering is off; you went from 3.1.7 back to and it doesn't auto-update anymore."

The "make compatible" button no longer displays on the Add-ons menu and Force Addon Compatibility option from the Tools->Nightly Tester Tools menu does nothing.

Is there a plan to fix this and when will this be updated for Firefox 7?

Cette critique concerne une version précédente du module (