https://bugzilla.novell.com/show_bug.cgi?id=679580
https://bugzilla.novell.com/show_bug.cgi?id=679580#c8
--- Comment #8 from Jan Engelhardt 2011-03-24 18:28:31 UTC ---
I think I found the issue.
1. Install an addon with a given maxVersion, for example: firebug 1.6.2, which
has maxVersion="3.6.*" in its install.rdf.
2. In any "default case", the extension is deactivated — seems logical given it
just said maxV=3.6.
3. However, if extensions are checked against the Internet database, they can
magically become enabled, because firebug's entry in the db is now listed as
compatible with 4.0.
This extension recheck can be triggered when prefs.js's
"extensions.lastAppVersion" is unequal to the version of firefox. Removal of
extensions.sqlite etc. does not trigger this.
The check however is also buggy, because it is not known *which* version of
firebug is the one compatible with firefox 4. For all that is known, it may
only be firebug 1.7 that can handle firefox 4, but not 1.6.2.
Subsequently, removal of extensions.* will disable the extension again, see
(2).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.