Discovering Add-ons in Firefox 4 « fligtar's blog. Back in March I blogged about an idea to make the Get Add-ons pane of the Add-ons Manager in Firefox 4 remotely hosted and much-improved. It would help users learn about and discover new add-ons through fresh content and recommendations. This afternoon we launched something extremely close to that: You can see it for yourself by opening the Add-ons Manager in a Firefox 4 beta or nightly build and going to the Get Add-ons pane.
(Note: if you see the mozilla.org homepage instead, switch to the Extensions pane and back to fix it. This bug has already been fixed with today’s nightly build.) There are a few things to keep in mind when exploring this page: Because this page is only viewed in Firefox 4, the web developers working on it were able to take advantage of two recent CSS features. It’s really exciting to see this come together thanks to the help of many people. Add-on compatibility for Firefox 4 – time to get started « Mozilla Add-ons Blog. As most of you are already well aware of, Firefox 4 Beta 1 was released a few weeks ago. Beta 2 will follow very soon, and the final version is expected late this year. This relatively long transition period is great for add-on developers, because it gives us plenty of time to update and test our add-ons for Firefox 4. On the other hand, this new major release is going to sport a ton of new features, and it will break a great deal of stuff we need, so it won’t be trivial to upgrade most add-ons to support it.
This is the first of many posts that inform add-on developers about Firefox 4 compatibility. First of all, MDC is your friend: Firefox 4 for developers. Here are some highlights from the document. The new Add-on Manager object The nsIExtensionManager interface is no more, along with its RDF backend. A key difference in this new interface is that requesting add-on data is now asynchronous. XPCOM Registration Components now need to be explicitly declared in the chrome.manifest file. Add-ons Forum • View topic - Firefox 4 Compatibility. Fri Sep 10, 2010 4:34 pm by jorge-villalobos Re: Firefox 4 Compatibility The bug (and its duplicate) are both flagged as blocking the Firefox 4.0 release, so at the moment they're scheduled to be fixed in an upcoming beta, or even a release candidate.
They're definitely not very high priority at the moment, judging by their activity. If you can include more useful information, the bug can progress faster. For example, you could try to identify the timeframe where the bug began to appear. Or you could also try to identify in the source code where the bug is occurring, and maybe suggest a patch. Otherwise you'll have to wait for somebody else to pay attention to it. Top.