Broken executables in extensions in Firefox 3.6
Reposted from my blog in order to spread the word: If you are an extension developer and include executable files in your XPI package (binary or shell scripts) then you … Read more
Reposted from my blog in order to spread the word: If you are an extension developer and include executable files in your XPI package (binary or shell scripts) then you … Read more
A few weeks ago, we launched the Add-on Compatibility Reporter, a way for Firefox users to let us know if their incompatible add-ons were working properly or having issues. As … Read more
Weeks before every Firefox release comes a huge effort from Mozilla encouraging add-on developers to make sure their extensions and themes are updated to work with the upcoming version. This … Read more
We launched Collections in June, Contributions in July, and the response to both has been amazing. What’s next for AMO? Here are some summaries of our upcoming projects. Collections Phase … Read more
With the Firefox 3.5b4 release, we’ve enabled the 3.5.* maxver in the AMO Developer tools. For the vast majority of add-ons without binary components, you can simply update your maxver … Read more
Last Friday, it was announced that Firefox 3.1 will be renamed to Firefox 3.5. What does this mean for add-on compatibility? Right now, Firefox 3.1b4pre is available as a maxVersion … Read more
This post is here to warn a subset of add-on authors that we’re making some late changes to the IID for some interfaces on the Gecko 1.9.1 branch. A very … Read more
As I’m sure you’ve noticed, we’re pretty hot on getting as many add-ons as possible up to Firefox 3.1 beta 2 compliance. For users, it’s extremely important that the add-ons … Read more
3.1 is coming! We know that many add-on developers have held off on testing for 3.1 compatibility because they’re waiting for a near-final release to test against. I’m happy to … Read more