Preparing for Firefox 3.1: add-on fixes

- Image via Wikipedia
It’s that time of the Firefox release cycle again: we’re at the verge of the 3.1 release, code named Shiretoko. The betas are getting pretty stable and usable for everyday use.
This usually means also that many of our tried and trusted add-ons stop working, because they have not been marked compatible with the latest Firefox version yet.
So for your convenience links to add-ons with incremented maxVersion number in their install manifest.
- livehttpheaders 1.14 updated for Firefox 3.1
- openprofilefolder 1.1.7 updated v1.1.6 for Firefox 3.1, see Open Firefox Profile (add-on)
These are not changed in any other way than setting the maxVersion number – but you should’nt trust me and verify for yourself!
Related articles by Zemanta
- First look: Firefox 3.1 beta 2, now with private browsing (arstechnica.com)
- Second Firefox 3.1 beta brings significant changes (news.cnet.com)
- Firefox 3.1 beta 2 now available! (lockergnome.com)
- Mozilla boudoir shoots out second Firefox 3.1 beta (theregister.co.uk)
Popularity: 9%



![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=5c64289f-f433-434f-9686-a791027d1e19)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=e4d94470-d3d6-48a2-9a69-c8ebbd68d2ec)
It is easy to get lost if you’re working with many development profiles in FIrefox: what profile is currently running? There is no easy way to find out from the browser.
If you’re developing add-ons for Firefox, you likely know the
What’s annoying me is that I read on a blog that you can set extensions.checkUpdateSecurity to “false” in the pre-release versions of FF3, but I can’t find that property anywhere in my about:config for the final version released in June… Just as I’m starting to learn about that crazy XUL soup, and I was referred to the Extensions Developers’ extension by Mozilla’s own tutorial.