Actually I ran into another problem w/ Safari and the Google Personalized Home. One of my gadgets (as they call them), "Google Reader (Labs)", doesn't work quiet right. Usually the title for a gadget is a link, and this one is no exception. The link doesn't work in Safari, but works just fine with Firefox. Go figure. My guess is that the new Google themes are just a tad buggy. You might write Google.

Oh, and lest you think this is something just with Macs, I found a problem the other day with Google Personalized Home using Linux and Firefox, an annoyance really, but given that Google runs on Linux, it's almost unconsionable.

I find that the usual safari problems have to do with CSS and JavaScript. I bet the centering is being done with css or js, and that safari is wiggin out on it.

See attached. The style of that div is text-align:center. even the table has align=center as a table attribute. But look at the style for div id "doc3" and it is text-align:left. So it may be that safari is honoring the wrapper div style instead. DOH!

All they had to do is wrap the table in a <center> tag. It works, but... welcome to 1998. Thanks again Safari.

As I've mentioned in several other posts, the problem is that
a) Safari is based on KDE's KHTML rendering engine
b) Safari is SORELY outdated compared to the current Webkit build
c) Try the nightly build, see if it makes a difference.

What is this nightly build? I downloaded it and launched it (the icon suggests it is Safari) but it just crashes. Is this some form of build of Safari with the latest and greatest rendering engine from KDE?

What is this nightly build? I downloaded it and launched it (the icon suggests it is Safari) but it just crashes. Is this some form of build of Safari with the latest and greatest rendering engine from KDE?

A 'nightly build' is just the latest and (sometimes) greatest code compiled in to a working app.
Builds aren't always stable, but you can always get the previous build or get the next nightly...or stick with the Safari that Apple provides.

So the nightly build should be a fully functional Safari executable? If the one I tried crashed, I should just try another one? Since it crashed, I had no idea whether it was the full app or just a framework portion of it.

voiceofra, I know that you frequently get cut if you try to live on the bleeding edge, and I am guessing I have a little incision from my attempts at the nightly build. Since my failed attempt to run it, Safari no longer shows the nice little icons next to items in my bookmark list. They are all little blue globes now, and no matter how often I visit a site, they stay little blue globes. Is there a way to change this back?

By the way, I downloaded todays build, installed it into Applications properly and tried it again. It still crashed. It offered me the chance to retry the launch and I took it. The second time it comes up and stays up. Each time I start it, I have to go through the initial crash before it will stay. So, it is of limited value for now, unless it has installed some base components elsewhere in the system...