Steve Jobs has sold out and forgotten Apple's core customers by moving to Intel.

The Mozilla Foundation should boycott the Macintosh platform, and encourage other software developers to do the same, until he relents.

Apple ported Firefox to Mactel themselves to show their commitment to developers, you poo.

Hey, maybe MoFo should boycott Microsoft and Windows too? Heh. BTW: People use Macs not for the processor, but for the OS.

van hornet,

Do you think that would do anything to sway Apple? With Safari as a great in-house browser, do you think they would change policy for MoFo? And how does this sellout core customers as long as they keep their promise to only release the OS with Mac hardware?

Not a single comment on the experimental build?

The problem with Intosh isnt the hardware but the DRM.

I for one really like the new build. Plugin context menus work properly now, and the browser does seem a bit sped up. Good work, and I hope this feature makes it into 1.1.

Great build. Huge performance improvement, no regressions detected so far

I have been playing with the build for some time now, and it feels good. I tried it on several "bad" pages I know. So far, it has done well.

@ van hornet: What kind of processors should Apple use, in you opinion? IBM does not deliver. We could use steam engines...

I agree, it's definitely a performance improvement for plugin use. E.g. the only
two pages that almost didn't work on Deer Park Alpha 1 for me because of massive swf problems do work on the plevent build now. Although they still require a CPU usage of about 65-70% while e.g. Safari just requires less than 45%.

Nevertheless it's clearly a step forward, and it'd great to see the feature in the next Deer Park Alpha.

Testing several dozens of other pages didn't reveal any new problems in comparison to the latest nightlies.

Thanks for the great work, keep it up!!

So are we likely to see a Mac build of firefox that isn't butt ugly and completely isolated from the OS integration-wise?

Asa - are the blank-menu-items-after-closing-browser-windows a known issue in the nightlies?

Nice jobs guys!

Just playing around with some java applets and the speed boost is huge. Java applets run clearly faster then safari even now. Nice!

I did manage to crash ff however after loading my 3rd applet to test. I havent been able to reproduce this yet but I do have the crash log/trace I sent to apple.. not sure if that would help here or not. All I did was load an applet hit back load another one.. after the 3rd one it crashed.. I'll play around with it some more to try to reproduce it.

Thanks,
Greg

Yeah, sites with lots of flash content that used to lock up Firefox (and sent me running to Safari to actually be able to use the site) actually work in Firefox now. :) Impressive! (Even the stuff at NASA :)

I see a lot of repaint problems with this build on OS X 10.4 in conjunction with the bfcache.

Really great work! I've been using nightlies (updating every couple of days) and haven't noticed any major problems with this new build. I encountered an odd issue with scrolling, but the performance improvements are good enough that I'd say go ahead and include this in standard nightly builds. I want to keep testing nightlies, but I don't want to go to a build without this patch!

For example, sites like threadless.com and weebls-stuff.com (Flash heavy) now function an order of magnitude faster. Any issues this has introduced are surely worth fixing for 1.1.

Don't feed the bitter Mactel trolls.

Between this version of Firefox, the new Camino 0.9a1, and WebCore nightlies the Mac browsing situation has never looked better.

You know... The people who are so bitter about Mactel just make me laugh out loud.

The current ones are from IBM.

BIG BLUE.

C'mon, people, does nobody have a memory longer than a decade in this business?

I too am seeing a lot of repaint problems. I am on 10.3.9. Other than those problems, which require me to be constantly hitting the refresh button, I am enjoying this build. It does seem to be more responsive.