My own interest in firefox is very low, although I can always share pointers with anyone willing to work on it. Personally I'd rather work on WebKit, as it is very much cleaner, very much more open to ports and more in the BeOS spirit. Remember that firefox is very much a moving target, and the port has been standing still for three years. The code base in the near same size as Haiku. So it requires a lot of work to get back to speed, and I suspect that at this point it would be easier to finish the webkit port. These are some of the things that needs to be done: * The port of firefox to gcc4 and Haiku isn't in their repo so it will need redoing. * Rendering needs a complete rewrite for adopting Cairo, and fonts needs special care (either port pango or write native handling). * NSPR needs rewriting or adoption. The nspr patch is probably very outdated, especially now that they are switching to having one process per tab. * The firefox2 and firefox trunk trees are inconsistent in beos/haiku code and would need syncing. Right now apps is a very low priority for me though as I can't run Haiku at a decent resolution. /Fredrik Holmqvist, TQH