jump to navigation

Firefox 3 beta 2 and incompatible extension workarounds December 19, 2007

Posted by Aditya in Beta, Browsers, Firefox.
trackback

I had posted earlier on my initial experiences with the Firefox 3 beta inside a sandbox, and decided to hold off on a full time switch to the beta as most of my favourite extensions were incompatible. The incompatibility status for the extensions has not changed, but I discovered an easy workaround (no hacking around xpi) today when looking around for a working mousse gestures extension.

All I had to do was to create a “extensions.checkCompatibility” boolean field in the Firefox about:config and set it to false. As you can guess, this disables the compatibility check for the extensions, and all the disabled incompatible extensions are enabled (with warning messages). Of course, this does not guarantee that the extension will work. Also the browser crashed on the first restart (the subsequent restart was fine though).

However, I was able to get most of the required extensions working this way (not extensively tested). They include Mouse Gestures, del.icio.us bookmarks, Greasemonkey (Update 22/01/2008: Greasemonkey just got an update today and is now supported on Firefox 3 beta), MR Tech Local Install (this one can override extension compatibility versions) and PDF download. Some extensions remain unusable though like Tab Mix Plus (possibly due to the architectural changes) and Google Gears (might be because I’m running inside a sandbox). Not a major loss, though I miss some of the tab tweaks provided by Tab Mix Plus.

I plan to use the beta inside the sandbox as my primary browser now that the extensions problems has been worked around. I’ll post my findings in in a few weeks, by which time some updates are likely to be available.

As for the changes from beta 1 to 2, check out the release notes. Of note is the fact that the rich interfaces of Yahoo Mail and Windows Live Mail are still unsupported.

There seem to be further tweaks to the memory usage (image below) and rendering. The interface hasn’t changed much, though a Smart Bookmarks folder seems to have been added to the bookmarks toolbar. The earlier location bar update that includes suggests autocomplete entries based on the page titles and not just the link text is quite a useful feature.

And to sign off here’s a comparison of the memory usage of v2 (top – gray) vs v3b2 (bottom – blue) with the same 8 tabs open in each, taken using process explorer. Note that there are fewer extensions in v3b2 and it is running in a sandbox.

Firefox 2 vs 3b2

Comments»

1. Firefox 3 beta 2 JavaScript benchmark plus why Flock is faster than Firefox 2 « AB’s reflections - December 20, 2007

[...] for different browsers. His list do not include the browser betas though. Since I’ve been trying out Firefox 3 beta, and it seems a lot snappier than version 2, I decided to give it a try. To make things [...]

2. Lawk Salih - December 26, 2007

This is helpful information. Thanks for sharing.

3. Cui - On My Way » Blog Archive » Say Goodbye To Firefox 2 - December 28, 2007

[...] some googling i got this work-around today. I tried immediately by adding the boolean “extensions.checkCompatibility” with [...]

4. Firefox 3 Beta and your favourite extensions - Frank-Leonardo Quednau - January 5, 2008

[...] than happy to find a workaround to install extensions that have not yet been ported to version 3. Check it out here.read [...]

5. Helder - January 24, 2008

Beta 2 apparently doesn’t have that option in the about:config. Do you know of an equivalent I could use to do that trick? Thanks!

6. Aditya - January 24, 2008

Hi Helder. You need to create the variable in case it is not present. Just open the about:config page in Firefox, right click and create a new boolean variable with the said name and set it to false.

7. Dalamar - February 10, 2008

Hi!
First of all thanks for this article!
I’d like to provide additional receipt to turn ON those extensions that left locked even after applying extensions.checkCompatibility.
Here is another one parameter: extensions.checkUpdateSecurity.
Set it to ‘false’ and all of those extensions that has unsecure update URL in section will be unlocked!

8. phroton - February 12, 2008

Thanks! Gestures was the one thing stopping me from using the FF3 beta full-time :)

9. Dan - February 13, 2008

Nice article. Thanks for sharing.

10. Fading Roses & Raging Viruses » Blog Archive » I moved to Firefox 3 and so can you - February 29, 2008

[...] me because they were incompatible with FF3 was a showstopper for me. Now however I have found a workaround: extensions.checkCompatibility With this value set to true in the about:config screen you can use [...]

11. Sebastians mainzBlog » Blog Archiv » Firefox 3 beta 2 and incompatible extension workarounds « AB’s reflections - March 4, 2008

[...] haben aber nur die Sperre in der Versionsnummer; funktionieren aber sonst (fast) einwandfrei. Unter Firefox 3 beta 2 and incompatible extension workarounds habe ich jetzt die Lösung gefunden. Im Browser “about:config” eingeben und den Wert [...]

12. fragility » Blog Archive » Upgrading to Firefox 3 - March 16, 2008

[...] ended up using a hack which bypasses the check for extension compatibility, but if this turns out to cause any [...]

13. Firefox3, Your Old Extensions, And You | moving parts of the kasper clan - April 24, 2008

[...] aren’t released for FF3 yet. TinyURL Creator, for one, is notably absent. Well, thanks to this page, I found a really simple workaround to enable (possibly dangerous and a bad idea to do) your old [...]

14. Enabling incompatible extensions with FireFox 3 Beta 5 at Aral Balkan - May 3, 2008

[...] Also feeling the loss of my del.icio.us bookmarks, HTML Validator plugin, and Alexa rating graph, I googled for a possible solution and came across this useful tip: [...]

15. Randall - May 27, 2008

I tried the hack and most of my extensions now work in FireFox 3

Anyone know how to get “Always Remember Password” to work in
FireFox 3

16. Extension compatibility status for Firefox 3 « AB’s reflections - May 28, 2008

[...] * – these extensions work using the extensions.checkCompatibility=false hack [...]

17. Aditya - June 18, 2008

For all Tab Mix Plus fans out there, there’s a developer version available on the TMP site. I got the link from a comment on the Firefox addon site.

18. Giovanni - June 19, 2008

Finally I have my dotComplete extension working on Firefox 3. Thank you.

19. Aditya - June 20, 2008

MR Tech Local Install (now called Toolkit) is now compatible with Firefox 3.

20. reeloo - July 2, 2008

If You can’t wait for extension authors to update… just use this little trick to break/skip extension verification and use any obsolete add-on in FF3 (FF2).
http://www.reeloo.net/wordpress/how-to-manually-update-firefox-xpi-extensions

21. Aditya - July 3, 2008

Actually now that MR Tech Toolkit is Firefox 3 compatible, we don’t need any hacks as it provides a version check override option.

22. Tigran - November 6, 2008

1. Subscribe.

23. romonoeroetoko - July 8, 2009

Hm that sounds good but I would like to know more details.

24. romonoeroetoko - July 15, 2009

Your news is a cool stuff man, keep it going.

25. amenodimeno - July 31, 2009

That’s good man, keep it going.

26. amenodimeno - August 6, 2009

Good story for me but please more details.

27. queroeropoo - August 7, 2009

Good information to me.

28. adamoerikom - September 20, 2009

Stunning blog and good article. High 5 for u man !