I am running Firefox 15 (beta) and I thought that Add-Ons where supposed to by default be compatible regardless of maximum version compatibility. I found this on a website that seems to confirm what I thought:
Default Add-on compatibility – This feature is already integrated in all versions of the browser from Firefox 10 onwards. It basically assumes that Firefox add-ons are compatible, even though their maximum version compatibility may state otherwise.
Or as Mozilla Says:
The vast majority of add-ons work from one version of Firefox to the next without the need for developer maintenance, but under the current system, compatibility information must be updated in order for Firefox to enable the add-on for use. For add-ons hosted on AMO, this is done automatically. However, 75% of add-ons in use are not hosted on AMO, and are therefore a major compatibility obstacle for our users. All of the compatibility effort put into each release is simply because Firefox still assumes add-ons will be incompatible between versions, when they usually aren't.
We should change Firefox's assumption to be that add-ons are compatible, with a few exceptions. Binary add-ons are never compatible between releases and are also the highest risk of negative side effects. Firefox should automatically enable low-risk (non-binary) add-ons in new versions of Firefox, and check AMO for additional compatibility information.
When users upgrade to a new version of Firefox, only the add-ons that are actually incompatible should be disabled, and the rest are assumed to be compatible. Because Nightly, Aurora, and Beta users will test out the add-ons for weeks before stable users, we should be able to identify and blacklist incompatible add-ons before stable users would be affected by a truly incompatible add-on.
I have several add-ons that are telling me they are incompatible with FireFox 15. Am I mis-interpreting what default add-on compatibility means? How do I tell if an Add-On is a binary add-on and/or tell if the add-on is truly incompatible?