I finally downloaded Chrome and tested my site that's under development. It's using all the standard settings when you install it, like most people do. They claim to have faster page loads, but I think it's a psychological effect on _how the pages load.

The solution I seek is from the developer's perspective, not the end user/browser setting.

When I navigate from one page to another, there's an annoying white flash that occurs. The entire page is white and can be irritating. According to google discussion, it's the browser tab background that is flashing (http://code.google.com/p/chromium/issues/detail?id=311).

It happens when the page is first loaded, as most of my customers experience. It goes away if I quickly navigate, but if I wait a moment before moving to a new page, the white flash happens.

The style sheet for the body tag has a grey background color as well as a background image.
I tried changing the body tag to include the grey background but that doesn't work.

In the g discussion cited above, someone put the background style tag inline with the <html> tag. http://thesis-blogs.com/annoying-whi...google-chrome/ said that it had to go right after the DOCTYPE.
I tried that but it hides elements with a z-index<0, even if I apply the z-index to very negative (and the required position) to this tag. This is a complex site and I am not going back to re-do absolutely everything. Browsers should all play nice with us developers.
Besides, this tag trick cannot be validated.

I tried a transition, but no go. Is this depreciated?
<META HTTP-EQUIV="Page-Enter" CONTENT="revealTrans(Duration=1,Transition=23)">
and
<meta http-equiv="page-enter" content="blendtrans(duration=3)">

Is there anything more that I can do on the development side to force a nicer transition in Chrome?