The div that the core code generates which holds all the view_state code at the very top of the page is actually showing up as a blank 14px high area at the top of the screen in IE7 only.  IE8 renders fine as well as other browsers.  This <div> has no class or inline styles applied, so there is nothing I can do to get rid of it without effecting ALL other div's on the page.  We have tried removing all default font-sizes, adding default font-sizes of 1px height, etc, to the html, body, form, and div tag styles in the skin.css and nothing works to resolve this.  The only thing that works is to use IE8's developer toolbar to place an inline style of height: 0px to that particular div, and then it finally becomes invisible like it should.  But of course, you can't exactly ask site visitors to do that so the page renders correctly...

The odd thing is, I cannot repeat this problem on two other locations with the same skin installed.  It only occurs on one server that is running Windows 2003 SP2 and DNN 5.0.1.  On a local install of DNN5.0.1 where the skin's html, the skin.css, the container.css, default.css, portal.css, etc. are exactly the same when compared between the two.  There are no extra modules installed, everything is the same or at least appears the same behind the scenes.  The only difference is that the one site is rendering that div 14-16px high when it should not be visible at all.  Well, that and the offending site was upgraded several times from early versions of DNN 4x, and the test site was upgraded once from DNN 4.6.2 to 5.0.1, but again, the default.aspx and all css files are exact matches between the two.

Is that div that contains the view_state code somewhere in code that we can manually edit it to add an inline style of 0px height, or is that something that is in the compiled dll's in the bin directory?  We'd like to solve the issue before going live with the new site, and assume that nothing in any 5.1 upgrade is going to change in regards to not styling that div.

Suggestions?

Link to live site:  http://www.bytesolutions.com/

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

Anyone have any clue why this would happen on one site and not on another site using exact duplicate of the skin, duplicate portal.css, duplicate default.css, etc.?  It's just baffling and I haven't found a resolution.

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

We tried the font-size: 1px trick in various ways including what you mentioned.  I'm not sure about the asp.net versions, but I believe both sites are 3.0/3.5, I didn't think to check that. My localhost test and live website were both asp.net 2, but the live site I just upgraded to asp.net 3/3.5.  I also upgraded from sql 2000 to sql 2005 on my live site, not sure which version my client is using.  I'll pass these other suggestions along to see if they help.  I had asked the client to try a second separate installation with a clean 5.1 install, not one that was upgraded through different 4x versions, but he hadn't had a chance to test that out yet to see if it was some strange anomaly with that particular installation.  Anyway, thanks for the good suggestions!

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke