Firefox 5 and Add-ons

It seems some extension developers did not take Mozilla seriously when the firm release date for Firefox 5 was announced about 2-months ago. As a result these developers have neglected to update their extensions (which will work in Firefox 5) to bump up the maximum supported version. It is important to understand Firefox 4.0 is no longer supported. However, there is no change to the core of Firefox 5.0, 6.0 or 7.0 so add-ons that are already working in Firefox 4.0 will work in these newer versions if forced.

The Add-on Compatibility Reporter extension will take care of this for you. Note: this extension requires two restarts initially. This add-on has also allowed Mozilla to reach-out to these extension developers during the Aurora and Beta cycles letting them know they need to update their extension compatibility.

2 Comments on Firefox 5 and Add-ons

  1. I have to say that I was a little surprised and disappointed that I had to manually make a few add-ons compatible with the 5.0 update. Also, I was curious if anyone noticed recently some about:config settings reverting back to the default. I don’t know if this happened with the 4.0.1 or the 5.0 update or when exactly. After the 5.0 update I noticed the change on a laptop and a desktop both running W7 x64. All of my network changes and a handful of others like mousewheel acceleration for example. Weird!
    Was wondering what your thoughts are on some of the common network about:config changes. I try to stay a little conservative on my settings but that’s just my opinion of conservative.
    user_pref(“network.dnsCacheEntries”, 100);
    user_pref(“network.http.keep-alive.timeout”, 300);
    user_pref(“network.http.max-connections”, 42);
    user_pref(“network.http.max-connections-per-server”, 22);
    user_pref(“network.http.max-persistent-connections-per-server”, 16);
    user_pref(“network.http.pipelining”, true);
    user_pref(“network.http.pipelining.maxrequests”, 8);
    user_pref(“network.http.pipelining.ssl”, true);
    user_pref(“network.http.proxy.pipelining”, true);
    user_pref(“network.http.redirection-limit”, 10);
    user_pref(“network.http.request.max-start-delay”, 1);
    user_pref(“network.prefetch-next”, false);

  2. @ richard
    Here you can find a answer maybe:

    Had the same issue and it was helping me.

Comments are closed.