tortuga - 9:55 pm on Mar 13, 2007 (gmt 0)

Hi,

Thanks for the replies. Sorry I didn't respond ealier, but I never got an email saying somebody had replied. I guess I didn't expect anyone too.

I may have been thinking about this the wrong way. I was assuming it was the browser onLoad or window resize that was causing the problem. I figured the print version would come out of cache, only with the print css applied. What you seem to be saying is that when the user goes to print, it actually loads the page again and triggers the onload function. It never occurred to me it would happen that way. Silly me.

So, with this new perspective, I'll be I can figure something out. Thanks for the insights. It's funny how we can have blindspots like that.