Comments on: Announcing the Add-on Compatibility Reporter

By: Lee

Lee — Wed, 03 Mar 2010 02:03:30 +0000

Using Nightly Tools Tester with the build listed below, I was able to enable over 36 extensions -or at it least it seems so far. I’ve noticed though Add-on Compatibility Reporter is not allowing me to report what works or/ what doesn’t.

I’m listing this here as I cannot find a version of NTT for the newest version of Firefox -would be great if this was included in future builds a testing tool.

Just learning my way though, so I’m probably not doing this right; also just learning how to do the litmus tests.

( Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a3pre) Gecko/20100302 Minefield/3.7a3pre (.NET CLR 3.5.30729) )

By: Michael A. Pasek

Michael A. Pasek — Tue, 15 Dec 2009 22:38:15 +0000

Compatibility Reporter doesn’t allow me to use “Incompatible” extensions with Thunderbird 3.1a1pre. For extensions that are “Not compatible with Shredder 3.1a1pre”, the “Enable” button is greyed out. ‘extensions.acr.firstrun’ is already set to ‘true’ in about:config.

Never having dealt with the “Add-ons” window/preferences before, I’ll also note that the “Preferences” buttons for both working and non-working extensions are also greyed out. It’s possible that this is normal — if, for example, the extension has no preferences (but I’d think the button shouldn’t even be displayed if it doesn’t).

By: Eckoman

Eckoman — Sun, 22 Nov 2009 00:59:06 +0000

@Brian:

THANKS!!! It worked, yay!

By: Brian

Brian — Fri, 20 Nov 2009 12:15:01 +0000

It seems to work okay in Fx3.6b3 after a slight adjustment. I had the same problem with it not working, but I was able to fix it. Just follow these few steps:

0: Upgrade to Fx3.6b3
1: Open the about:config page
2: Find the preference “extensions.acr.firstrun”
3: Change the value from “false” to “true”
4: Restart Firefox

After restarting, ACR did whatever magic it does to override compatibility, and wanted a second restart. Do that, and everything should work after.

By: Holly

Holly — Wed, 18 Nov 2009 21:50:27 +0000

After upgrading to Fx3.6b3, my addons for previous versions were all disabled, including the ones I had already marked as working in Fx3.6b2. I had used the MRTech extension for some time (but disabled it now). Could it be that MRTech set some pref that keeps the Reporter from enabling addons? Can I do anything to get them working again, short of bumping them manually (which would break the Reporter functionality)?

By: Ian M

Ian M — Wed, 18 Nov 2009 13:58:39 +0000

@glen @eckoman – same here

By: Eckoman

Eckoman — Wed, 11 Nov 2009 14:44:47 +0000

Same deal here but obviously no solution. *sigh*

By: Glen

Glen — Tue, 03 Nov 2009 23:16:46 +0000

When I install this on 3.6b1, half of my Add-ons are marked as Incompatible, with Options and Enable greyed-out. There is no way of testing these Add-ons.
I have uninstalled and re-installed – No difference.

I have not used Nightly Tester tools or similar, simply a pre-existing 3.5.

By: Eckoman

Eckoman — Mon, 02 Nov 2009 10:04:41 +0000

I have a problem with this add-on. I installed it on Firefox 3.5, then upgraded to 3.6b1. After the first launch of 3.6b1 it worked, I could use all add-ons and report if they are compatible or not. After another restart, all add-ons were disabled b/c they are not supporting 3.6b1. I tried to uninstall and reinstall the compatibility reporter add-on but had no luck.

How do I regain the possibility to run all my add-ons again?

By: fcp

fcp — Sat, 31 Oct 2009 13:52:55 +0000

Justin, thanks for the reply.

> If the add-on has already been marked as compatible with the version you’re using,
No, the add-on has not been marked as compatible with 3.6b1. I had overridden the compatibility by using the Nightly Tester Tools (before installing the Add-on Compatibility Reporter), and I wanted to report that the add-on was working with 3.6b1. I think that this is a common situation for users who have used 3.6a1. However, I do not know if it is possible for the Add-on Compatibility Reporter to detect whether the add-on is really marked as compatible or the compatibility is overridden by the Nightly Tester Tools.

> we have a number of reports from SeaMonkey so there’s a good chance it works
Wow, that’s great!