April 8th, 2008
Since I bought my Mac, Safari has been my primary browser of choice. I have been using Firefox sporadically too - you can’t do serious web development without FireBug! Safari is light, zippy and renders wonderfully looking OS X look’n'feel pages - however with the arrival of Firefox 3 I am really pondering to ditch it in favor of FF (still no OS X look in there, tho’
). Firefox 3 beta 5 is just phenomenal - fast, powerful, and it has all the stuff I am missing from Safari (FireBug, del.icio.us toolbar, DOM Inspector, ton of other extensions) so I am really thinking that I will remain a Safari user on my iPhone only.
However, FF3 is missing some functionality I am depending on - most notably jssh support - DOM inspector was removed too, but can be installed as an add-on, and since beta 4 FireBug is working, so no major hurdles there. However, jssh, as usually was a harder nut to crack.
Fortunately Angrez, FireWatir’s author pointed me to the right direction - which was in this case compiling Firefox 3 with jssh support! Here’s how:
- Download the latest tarball (currently Firefox 3.0b5) from the FireFox source code ftp
- Follow these steps up to the 3rd point
- My .mozconfig file - assembled from this post and the mozilla developer docs (put it into our home folder)
- Compile time!
- cd mozilla; make -f client.mk build
That’s it! Easy, huh?
Sit back, enjoy your coffee and in a few minutes you’ll have your own, new hot FF build with jssh support!
By the way, FireWatir 1.1 hit the streets just today! Grab it and let the testing commence!
tags:FireWatir Mac Mozilla/Firefox News Ruby
April 8th, 2008 at 11:21 am
Although the Firefox 3 default theme is a great step forward to a more OS X like look & feel I highly recommend the themes from http://takebacktheweb.org/!
May 5th, 2008 at 2:45 pm
Thanks for the helpful information.
I’ve built a firefox 3 + jssh executable using the above, but am unable to generate the MacOS Firefox.app structure. Running ‘make -C $SRCDIR/fx-jssh/browser/installer’ returns the message that either static of libxul is required for packaging. Is there a better way to do this?
May 6th, 2008 at 2:04 am
Dan,
Unfortunately I am a total Mac n00b, so I don’t know… I was running it from the command line. I hope someone finds it out though and lets me know