Add-on Compatibility Reporter

[RobertJ]

The add-on claims to have two options:



Problem is that only the This add-on no longer works option is there!

HOW COULD MOZILLA RELEASE SUCH A PIECE OF GARBAGE

I know that this is not Mozilla; however, there appears no direct way to tell them that their add-on doesn't work (they apparently don't read the reviews for it) and I feel better after a rant

[BigWillyStyle42]

It seems to depend on the add-on. For some I get both, but for others I get only the not working option.

[RobertJ]

Interesting, for Add-on Compatibility Reporter

I only get the not working option. I guess that makes sense since it isn't working. Maybe that's a good way to report it

[rjohnson19]

It only lets you report "This add-on still works" for add-ons not set as compatible with whatever Firefox version you are using.

[BigWillyStyle42]

It only lets you report "This add-on still works" for add-ons not set as compatible with whatever Firefox version you are using.

That makes sense, good to know what the logic is there.

[RobertJ]

It only lets you report "This add-on still works" for add-ons not set as compatible with whatever Firefox version you are using.

Unfortunately if you "forced" compatibility using something like Nightly Tester Tools before you "found" this add-on, you can't use it.

[wiiwaker]

It only lets you report "This add-on still works" for add-ons not set as compatible with whatever Firefox version you are using.

Unfortunately if you "forced" compatibility using something like Nightly Tester Tools before you "found" this add-on, you can't use it.

Then that's not fault of moziila or this add-on

[RobertJ]

Then that's not fault of moziila or this add-on

Fault is such a harsh work. Why don't we simply call it a lack of foresight in the software requirements document for the add-on (I'm not naive, I know they didn't have one.). You know the thing that is supposed to anticipate that not all users are mind readers and look at all possible actions by users using beta's since they generally are aware of things like Nightly Tester Tools being used to test developmental software to insure that the add-on covers all these advanced users.

[wiiwaker]

Problem is NTT and this add-on do the same thing, although they do it in different ways. You know installing two add-ons doing the same thing always breaks Firefox
As to the compatibility options, it confused me at first and needs a little of logic to understand.

[RobertJ]

This add-on simply sets extensions.checkCompatibility.3.6 and other versions to false. I don't know exactly what NTT does when you hit the Force button. Do you and can you "unforce" it by doing some editing of the profile?

[RobertJ]

With FF 3.6b5 released I didn't force compatibility and was able to use Add-on Compatibility Reporter to let them know that six of my add-ons work perfectly.

• Autofill Forms 0.9.5.2
• Favicon Picker 3 0.5
• MR Tech About:About 2.4
• Tamper Data 10.1.0
• User Agent Switcher 0.7.2
• Web Developer 1.1.8

Another add-on I use, CookieCuller 1.3.1, had issues with the packaging; so, I repackaged it and submitted it as a new add-on CookieCuller - Updated 1.3.1.1 in case anyone was interested (giving full credit to the original developer). Currently in the sandbox.

Hopefully someone is listening.

[ratman]

The add-on compatibility reporter appears to no longer be compatible with Firefox 4.0b7pre, which creates an odd kind of recursive add-on incompatibility issue. Is there a way to get this updated for the latest builds?

[Pillum]

yes, change the maxversion in the .xpi or add a bool pref 'extensions.checkCompatibility.4.0b' = true in about:config

[bomfog]

add a bool pref 'extensions.checkCompatibility.4.0b' = true in about:config

ITYM "false"?

[Pillum]

yep, i meant false