Firefox Build for x86 Macs and Firefox with Cocoa Widgets

Here it is, x86 Mac only (not for PPC machines):

I’ll put it in the experimental directory of’s FTP server this coming week. Most things seem to work fine except for plugins. Only Quicktime is reliable. Most others crash the browser. I’ll work on a fix for that soon. Keep in mind that this build has whatever bugs exist on the Firefox trunk now in addition to whatever else might come up as a result of being ported to x86. Hopefully the two people that will use this build will file bugs on x86 port issues only, and not duplicate reports of bugs that exist on PPC as well. That said, enjoy.

This morning I got Firefox to build and run with cocoa widgets. Patch is already checked into cvs. We’re on our way. Note: cocoa widget builds do not have a menu bar right now, but who still uses that 20th century menu bar crap anyway?

17 thoughts on “Firefox Build for x86 Macs and Firefox with Cocoa Widgets

  1. I still have hard time believing that Apple is migrating from a 64-bit platform to a 32-bit one. Are you sure it was plain x86 rather than x86_64 or IA-64?

    If Apple is so stupid to go back to 32 bits, how are they going to support more than 4 Gb of RAM? And if they are not going to support it, they will lose the workstation market. Somebody with enough money should start a company to take that niche, perhaps using AMD64 processors.

  2. At the risk of sounding like a n00b: do you think the Fox will be able to be built as a universal binary once the time comes?

  3. Nice work, Josh! Thanks for all of the hard work you’ve been putting into Mac, build config, and the Mac Intel port. We appreciate it so much!

  4. Actually, the first round of Intel Macs will *not* support x86_64. But they will be replacing 32-bit G4s in Powerbooks and Mac Minis, where >4GB configurations wouldn’t have been available anyways. Intel Macs will get x86_64 in time for the switch to take place in the Power Mac line, sometime in 2007.

  5. Paul: Josh is a Mozilla developer, not an Apple spokesperson. He can’t speak for Apple’s business decisions, or their future plans–on top of which anything he did happen to know that you can’t find out through Apple would be under an NDA.

    In short, his blog really isn’t the place to for questions/complaints about what you think you know about developer transition systems or future plans. There are plenty of rumor sites with forums for that sort of thing.

  6. Seconding Jon Hick’s thoughts — that will one awesome browser for web development and general usage. Right now using Saft-powered Safari for regular stuff and Firefox for web development isn’t ideal, but it works. I can’t wait to see this go mainstream.

  7. Any chance we can see some screenshots of how this looks? Lack of native interface elements has been a big sticking point with me when using Firefox on my powerbook. Does this also mean select elements are displayed in the Aqua style rather than a pseudo-Windows style too? This method is so much better. So better, in fact, that I wouldn’t mind seeing it in the Windows build (although I imagine that’d be a real PITA to implement).

  8. I’m hoping the Cocoa widgets are of the smaller Safari/OmniWeb style and not the larger/stranger looking Camino mish-mash.

  9. “When will the native Cocoa widgets show up in the DeerPark nightlies?”

    Never. DeerPark is the name for prerelease Firefox 1.1, and cocoa widgets won’t be enabled until after FF 1.1. As I said in a prior blog post, maybe they’ll show up a couple of weeks past FF 1.1. I’ll certainly post a build before that once we have a menu bar.

  10. Yes, yes, a screenshot. The impatient masses want to see it.

    And I agree with Rob C above: Safari style widgets rather than the Camino/Opera type.

  11. FF will have the same form widget implementaion as Camino, the whole point of what Josh is doing is creating a shared widget base for FF osx and Camino.

  12. Does it mean that when you will implement the menu bar, there will be the possibility of having icons in the bookmarks menu, as in Windows (or Safari and Camino)?

Comments are closed.