State of the Add-ons Report: May 22nd
May 22nd, 2008Here we are again. Since we last spoke, RC1 has been released and add-ons can claim full compatibility with 3.0.*. Time to update status on some of the popular add-ons that are not yet compatible.
Firebug - 2.0.0.* (bug) - 1.2 version should be pretty set for Firefox 3. Not on AMO yet — but will be before Fx3 ships!
MinimizeToTray - 2.0.0.* (bug) - Not going to be updated without help. If you are an add-on developer, and are willing to mess around with some pretty scary add-ons code, please step-up and try to help get MinimizeToTray (and their 500,000 users) ready for Fx3.
Tab Mix Plus - 3.0a5 (bug) - Beta available here. Please test and comment on this thread.
Noia 2.0 (eXtreme) - 2.0.0.* (bug) - Getting a little nervous about this one. I’ve heard rumors it is being worked on — but no communication with the developer, and no updates in the bug.
FireFTP - 2.0.0.* (bug) - Should be ready for Fx3!
Foxmarks Bookmark Synchronizer - 2.0.0.* (bug) - not available yet on addons.mozilla.org, but I’m confident it will land before Firefox 3.
RedShift V2 RC1 - 2.0.0.* (bug) - after last weeks plea for help, no results. Cameron, the developer, still needs help getting updated to Firefox 3. See the bug and sources.
That’s it for now. MinimizeToTray extension and RedShift theme needs help!
May 23rd, 2008 at 8:47 am
I’m curious about minimizetotray. I have been using it with forced compatibility since I first started back up on the current Minefield Branch (nee Trunk) nightlies last year and have not seen any issues. I looked at the bug, too, and saw no steps to reproduce or extension settings that may be causing problems. I have mine set to all minimize to tray but neither minimize to tray on close nor require double-click to restore if that matters. I’d like to hear what the issues are.
May 27th, 2008 at 5:24 pm
Foxmarks Bookmark Synchronizer has a public beta of their extension for Firefox 3 RC. You can access it on their website if you have an account setup.
May 27th, 2008 at 6:06 pm
i would like to see the all-in-one sidebar compatible with firefox 3, it was so helpful!!!!
May 27th, 2008 at 6:17 pm
Greasemonkey also hasn’t been updated
May 27th, 2008 at 6:23 pm
[...] still need to get updated for Firefox 3. Here’s 20 add-ons that are Firefox 3-compatible, and seven that aren’t yet. If you’re testing the Firefox 3 Release Candidate, you can force Firefox to use incompatible [...]
May 27th, 2008 at 7:01 pm
I’d like to mention that Greasemonkey is quite popular and isn’t officially updated to work with Firefox 3 yet. It works fine when forced, but getting it requires that you use something that’s not showing as Firefox 3 or AMO will block you from being able to download it.
I just use the user agent switcher and pretend to be IE7.
May 27th, 2008 at 7:24 pm
Foxmarks actually has a beta out that is FF3 compatible.
-Adam
May 27th, 2008 at 7:45 pm
Good!
The long-awaited of Firebug.
May 27th, 2008 at 9:00 pm
What about the Official Google Toolbar? I’m thinking of going back to FF2 despite the amazing speed boost I experience with FF3, especially on sites like gmail which load ridiculously fast.
May 27th, 2008 at 9:49 pm
I’m using the beta of Fixmarks with FF3RC1 and it works fine ;-)
May 27th, 2008 at 10:27 pm
[...] Extension compatibility status for Firefox 3 May 28, 2008 Posted by Aditya in Compatibility, Extensions, Firefox, Status. trackback I was thinking about compiling my list for the compatibility status of extensions for Firefox 3, but it looks like the folks at lifehacker have already found a couple of sites that do the same: Here’s 20 add-ons that are Firefox 3-compatible, and seven that aren’t yet. [...]
May 27th, 2008 at 11:07 pm
I just want my google gears, dangit.
May 27th, 2008 at 11:32 pm
Sage RSS reader is not compatible with FF3.x
i may have to stick with FF2.xxxx
May 27th, 2008 at 11:44 pm
[...] para Firefox 3 totalmente funcionales. Sin embargo, hay siete conocidas que aún no lo son: alex.polvi.net/2008/05/22/state-of-the-add-ons-report-may-22nd/ sin comentarios en: tecnología, software libre karma: 13 etiquetas: firefox 3, extensiones, [...]
May 28th, 2008 at 12:18 am
Google toolbar (linux) does not work on FF 3 beta 5 on Hardy
May 28th, 2008 at 5:42 am
[...] kelis įskiepių suderinamumo sąrašus: 20-ies populiarių priedų, kurie jau suderinami su RC1 ir septynių, kurie dar ne. Iš tų septynių du man mirtinai reikalingi: Tab Mix Plus ir Foxmarks. Kol jie neveiks, aš nė [...]
May 28th, 2008 at 6:55 am
[...] compatible now. 20 top add-ons that are ready for Firefox 3…And there has been much rejoicing.9 that ain’t…boo hoo.The one that I am missing most? FireFTP is a handy little thing if you have your own [...]
May 28th, 2008 at 8:51 am
hey guys, Google Toolbar is on its way!
May 28th, 2008 at 3:22 pm
Foxmarks just updated itself… just fyi
May 28th, 2008 at 4:11 pm
Intercepting RedShift V2 RC1 by not restarting Firefox indicates that the install.rdf file needs to have maxVersion updated from 2.0.0.* to something like either 3.0 or 3.0* or 3.0+ to work for FF 3 at the very least. I would also create and set extensions.checkCompatibility to false in about:config in the meantime.
I could not check whether MinimizeToTray suffers the same problem because there is no version for Linux (which is what I run), but that would be my guess as a minimal modification.
May 28th, 2008 at 4:19 pm
@tom: Those are not updates — they are just hacks to force firefox to run
it. Forcing compatibility is generally not a good idea for add-ons
that are not updated to work with Firefox 3.
May 28th, 2008 at 9:53 pm
@Blob: You can stay with Firefox 2 to keep using Sage, or try the freshly available Sage-Too with Firefox 3 … decisions decisions :D
June 6th, 2008 at 7:21 am
@Ray: Minimizetotray currently won’t build against trunk due to various build system changes and other changes in the source (there was stuff from plasticmillion to do the icon thing better, for example). That’s the problem with having to include binary bits, which is pretty likely to get you into trouble when Gecko internals changes and you had some nasty dependency on those internals that ideally you shouldn’t have had but had to have…
Those binary bits also means forcing compatibility is a particularly bad idea in this case :(