Thanks for letting us know. Unfortunately it looks like this is an issue with Safari 3 beta -- we did some testing, and it appears they've fixed this in the latest nightly build. We don't 'officially' support beta/preview versions of browsers, as they can have quirks that aren't ironed out until the final release, but we'll try to keep an eye on Safari 3. Hope this helps!