On 01/22/2012 05:23 PM, David E. Ross wrote:
> On 1/22/12 4:52 PM, NoOp wrote:
...
>> Jens, any possiblity that the compatibility reporter can include a
>> box/tick that the extension works if the install.rdf is modified?
>>
>> 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
>>
>> 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.
>>
>> Yes, I understand that it is up to the add-on developer to keep this
>> updated (install.rdf), and that is not the issue I am pointing out. The
>> issue is how to sort out compatibility when the install.rdf has been
>> modified locally _and_ the add-on works when modified.
...
>
> Note that BetterPrivacy 1.68 as downloaded from AMO has install.rdf
> containing the following:
>
> <!--SeaMonkey-->
> <Description RDF:about="rdf:#$dLacB4"
> em:id="{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}"
> em:minVersion="2.0a1"
> em:maxVersion="2.6.*"
> />
>
> Should not this work with SeaMonkey 2.6.1?
>
IMO yes.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
