NoOp wrote:
Jens, any possiblity that the compatibility reporter can include a box/tick that the extension works if the install.rdf is modified?
Hardly. First of all, the ACR is a Mozilla product, i.e. its main focus is Firefox and possibly Thunderbird. Secondly, it's not the right approach. The goal should be to get the add-on authors to update their creations. At least that's what I think and what I've been doing.
For example: with SM 2.7b4 (linux) the following are fine with a modified install.rdf: - Novell Moonlight 3.99.0.2.99 - Password Exporter 1.2.1
For the latter, Philip Chee provides an updated version here: <http://xsidebar.mozdev.org/modifiedmisc.html#passwordexporter>
But, if the install.rdf is modifed (to say '<em:maxVersion>2.8.*</em:maxVersion>'" and works, the compatibility reporter denotes: "Marked as compatible by developer" when it actually wasn't. But the add-on works when modified locally.
The ACR enables you to provide feedback to the add-on author, but only if you do not fake the compatibility information yourself. Until compatible-by-default add-ons were introduced (starting with SM 2.7, which you seem to run), the ACR allowed to install any add-on that ever claimed to work with SM. Now it refuses that if the add-on is not compatible with at least SM 2.1 (which was the release matching FF 4, which is also FF's cut-off version for compatible-by-default).
Now I'm not exactly sure whether the old extensions.checkCompatibility.* preferences still work, but I think it's worth a try. With trunk it's probably easiest to install the Nightly Tester Tools add-on, but I'm not sure whether it sets the necessary prefs for branches like the ACR did. Maybe the "Disable Add-on Compatibility Checks" add-on does the trick; didn't try it myself.
HTH Jens -- Jens Hatlak <http://jens.hatlak.de/> SeaMonkey Trunk Tracker <http://smtt.blogspot.com/> _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
