Closed LewisR closed 10 years ago
Thanks! I've pushed it now, I'll get round to updating the mozilla site plugin at some point, but the last version has been sat in their review queue for 7 months :(
Unfortunately this failed the automatic version check on the add-ons site. Having max 2.* doesn't do it for them. I don't know much about Seamonkey, but from the link on the warning it seems like setting max version to 2.26 should do the trick. What do you think? I've submitted it like that anyway, so I'll close this issue if/when it's approved.
Error: The maximum version that was specified is not an acceptable version number for the Mozilla product that it corresponds with.
Version "2.*" isn't compatible with "seamonkey".
Ugh...
2.26 seems like we'll/you'll be updating the install.rdf too often. I would go with 2.9, Rich. I don't anticipate anything changing WRT this extension's compatibility until at least 3.0, and that is a long, long way off, AFAIK.
Thanks for letting me know. This is good information, as I've never submitted an extension to AMO.
Cheers
Lewis
Scratch that. I see from the appversions page that the best we can do is 2.26, so let's go for it.
;-)
This was fixed in commit 821235760a2b9c469e29f2286798ed3b6be38448 a while ago.
Nice work, Richard!
It would be great if you would just tweak the install.rdf to include SeaMonkey (the chrome urls for this are identical to TB). I've tested this under SeaMonkey on OS/2 and SeaMonkey on Linux, as well as making sure that I didn't break the install.rdf for TB.
From my diff:
Thanks!
Lewis