Safari Sucks
Coding for Apple's Safari browser is like having to work with the CEO's son: it does a shitty job and touts useless features like snapback, but you have to deal with it because if you decide to criticize it, you'll really hear it from the frothing-at-the-mouth Apple digerati.
Pre-1.3 Safari was just a joke. I can only imagine that the Gmail engineers were cursing it for months while trying to make it play well with their engine. 1.3 brought a bunch of much needed bug fixes, but then managed to break the onload handler six ways from Sunday. The Acid2 test is a quaint merit badge to slap on Apple's sash, but have you actually looked at some of the test cases? Nobody actually codes tables 37 levels deep with deeply disturbing border settings, so it still doesn't address some basic needs. My big peeve right now is that XSLT is not available as a service to javascript — it's only callable as an initial XSL transform with the page load.
This brings me to a more general rant against the state of the OS X browser: Safari is impotent; Firefox is ass-slow; IE is more stale than spam. God-damnit.