Navigator... it came back. Netscape was nice... until 6 bombed. 6.2 was a fix, but IE had the reins by then. Netscape from then on was tolerable, and even SeaMonkey was better(a twin of sorts). Then, Firefox 2.0+ was amazingly slow on a default Intel install without more memory or a faster hard drive than the normal 5400rpm, and Navigator 9 waltzes in, fast on a default setup, as useful as Firefox 2, and making up for Firefox programmers not having enough time to test enough on a default install on any simple new macbook. In other words, if you don't have the extra money for the RAM or the new Hitachi HD for your Intel 950 Graphics Macbook, stick with Navigator 9.
As for OmniWeb, Safari, Shiira, iCab, and Opera... I'm going nuts trying to cater a little to them. Camino, IE7, Firefox, SeaMonkey, and of course Navigator(which is Firefox with a different face and much faster on Mac than the fox) all show my floats fine that I hand programmed. Hopefully today I'll learn what one simple thing I'm missing, but until then, as amazing as OmniWeb is(and it is pretty amazing, customer support is fantastic), my floats are in a painful sort. And I would ignore them except for one glaring issue... Opera is the web browser on the Wii. Given the popularity of the Wii and that every friend of mine wants or has it, there's little choice.
Navigator 9 is nice... the Page Style selection from the server that's in Firefox, but not in Camino is present. So is page info. It doesn't pass the Acid2 test like OmniWeb. And iCab seems to pretend to pass it, I know I've crashed iCab going back and forth to the test. So, until the fox is 3.0, I suppose Navigator won't pass acid2. Safari 3 passes the acid2 test, but it's in beta. Shiira and Opera also pass the Acid2 test. My only quest is if I say float: left... shouldn't the browsers that pass acid2 float the next div by the div that says float: left ?