Hi Lee,
All the people who work at my organization are seeing it and so are the parents who have there students in our school. I thought at first maybe I was the only one seeing it but I am now convinved it is obvious that the skin breaks during postback.
If you did not see it before would you please take a closer look, specifically at the top menu
[ Home >>Contact Us>>Giving
after postback it looks like this:
[Home>>
Contact Us>>
Giving
Also, in the left pane area, after postback, the black side gradient image does not retain the same width but is truncated and does not fill the left pane any longer.
The final thing that happens after postback is that the aggregator tabs that the repositories reside in apply a hover class even though it is not defined in the aggregator module css. This happens in both IE6/7 and FF.
As for your suggestion to use Visit instead of relying on the javascript thats used for postback, I don;t understand how this would work since all the items (URL's to external websites) are stored in the db and must be referenced somehow by the [download] token.
I did notice in your CSS code they have duplicate calls to the skin.CSS file and to the left container.CSS file - have you left in your skin.htm file the code to call up the CSS file?
I'm not sure what you're seeing here...I have one link tomy skin.css file in my ascx file. I have one left pane that has 3 smaller panes nested within it. They are all properly defined in my css.
Sorry to be a bother...this is a big deal for my site and I really need to solve the problem. If there is a work around for this, please advise. If I am mistaken about how the visit would work, please feel free to correct my thinking.
Thanks,
Paul