MOZILLA FIREFOX ADDONS ICONS GONE UPDATE
MOZILLA FIREFOX ADDONS ICONS GONE UPGRADE
MOZILLA FIREFOX ADDONS ICONS GONE CODE
MOZILLA FIREFOX ADDONS ICONS GONE DOWNLOAD

Bug 539524 is tracking this new development. Needless to say, it won’t be removed without a suitable replacement.

MOZILLA FIREFOX ADDONS ICONS GONE CODE

In a nutshell, the profile manager hasn’t been updated for a very long time and is lacking in features, on top of some of its code causing slowdowns at startup. There’s a long discussion surrounding the reasoning behind this decision. The Profile Manager tool we’ve grown accustomed to is being taken out of Firefox. This will clear all relevant caches, to make sure you’re running the latest code. To make sure that your development profile is always picking up the changes, you should run Firefox 4 with the -purgecaches command line option. Since the XPI is not unpacked anymore, having the JAR (a package within a package) only adds overhead.įirefox is now caching code and other resources more aggressively.

It’s also recommended that you move away from the previously recommended practice of packaging all chrome files in a JAR.

However, for the final build you should aim to have your add-on installed without unpacking. The extension loader will check for either the XPI package or the unpacked directory.

You can still have you working directory in your profile as you did before.

You can also use the unpack flag if nothing else works. You can extract them using the chrome protocol or the nsIZipReader component, or find other ways to generate them.

If you read any files that are contained in your XPI from the profile dir, this won’t work anymore.

Those add-ons that need to be unpacked must add an unpack flag to their install.rdf manifest.

This also affects dictionaries and add-ons that include search plugins or window icons. Some add-ons will not work without unpacking, notably add-ons with binary components or other libraries.The same idea is now extended to add-ons, and by default they will be installed in the profile folder without unpacking them. Reading files from a package is generally much more efficient than reading them independently from the filesystem, so keeping as many files as possible packaged together is a performance win, specially on mobile platforms. Packed extensionsįirefox 4 will ship with most code files packaged in a single JAR file, also referred to as Omnijar. This includes add-on files as well, so there are a couple of changes that concern us. In order to improve Firefox performance, a lot of work is being done to improve file loading and processing at startup. Add-on Packaging and Development Environment

MOZILLA FIREFOX ADDONS ICONS GONE UPDATE

This list is as thorough as I could manage to make my objective is to make it as easy as possible for you to update your add-on so your users won’t have a hard time deciding if they should update their Firefox or not. Firefox 4 is the largest release so far in terms of code and API changes, so there’s likely something on this list that affects your add-ons. In this blog post I’m going to cover all breaking changes introduced in Firefox 4 that I’m aware of, including the ones I mentioned on my previous 2 posts ( Part 1, Part 2). Finally, you can follow the Mozilla blog and keep up with Firefox news. You can also visit the Releases page regularly.

New versions are normally being released every few weeks.

MOZILLA FIREFOX ADDONS ICONS GONE DOWNLOAD

How can you keep track of releases? One way is to download the latest beta and check for updates regularly. Firefox 4 is coming! If you want your add-on to be compatible, the time is now.

MOZILLA FIREFOX ADDONS ICONS GONE UPGRADE

Other than bug fixes and stability improvements, this the Firefox that will make it to the public, and you should be able to upgrade your add-on to work for this beta without having to worry about something being broken in the following betas and release candidates. This is the first “feature frozen” release, meaning that there will be no more major changes performed to the UI, APIs or features in Firefox. Firefox 4 beta 7 is out, and now is the best time to evaluate your add-on’s compatibility with the next major Firefox release.

Mozilla firefox addons icons gone