Forum Moderators: not2easy
Here goes… I have a site I am building and I cross browser checked before I had it posted to a beta test site. All worked fine in all browsers, until I posted to the beta version.
Now in IE 6 the main background I use (#main_repeted_bg) will show up as the page loads but then disappears. It is a png but not a transparent on that needs a “twin helix” fix. I mean, it really makes no sense for it to show up for a second and then disappear. Anyone ever have this issue. Or is this just one of those things that only happens to me
CSS and basic HTML layout listed below.
CSS
#main_repeted_bg {
background: url(../images/avc-main-bg.png) repeat-y center top;
width: 840px;
margin-right: auto;
margin-left: auto;
}
#main_container {
background: url(../images/gold-bars.jpg) no-repeat right top;
width: 790px;
margin-right: auto;
margin-left: auto;
padding: 15px;
overflow: hidden;
}
HTML
<body>
<div id="main_repeted-bg" style="height:100%">
<div id="main_container">
<div class="page_content">
Content on the Page.
</div>
</div>
</div>
</body>
Any Help would be appreciated.
Thanks
Fixes to try: let the parent gain the IE proprietary "hasLayout" property (by e.g. setting a conditional comment with "zoom:1;" in it.
Give the parent position: relative (without nudging).
I'm not sure it's that but nor if the fixes help (they don't always help unfortunately)
* {
padding:0px;
margin:0px;
}
I know most wont agree with that but I have been using it forever in order to even out all browsers. It has always worked so I don't think that it's the issue. I have set up pages like this before... Same CSS, without any issues.
I am considering that it might be the background png... I know sometimes that usually freaks IE 6 out on occasion. so I am changing it to a gif and we shall see if that works.
Another thing I think should be noted is that I do have some javascript on the page for some random pictures and quotes.
I would also check to make sure the png isn't part of the JavaScript element or inside an ID/class being used by the JS. If something hasn't been closed correctly and is still open that could cause no end of problems and would also cause an anomaly like this one.
Sorry for all the trouble, but thanks for the info!
[edited by: swa66 at 6:43 pm (utc) on Mar. 4, 2009]
[edit reason] Links [/edit]