Peek-a-Boo Bug

[createErrorMsg]

I am suffering from a particularly annoying strain of the peek-a-boo bug. I have tried every fix I can find (all five of the one's listed on Position Is Everything, including the Holly hack, position: relative and explicit widths) plus a few others such as specifying line-heights. Nothing has worked thus far.

Here's the story: I added a css drop-menu to the content div of a page, which places it beside a right floated sidebar, along with some content which, at the bottom of the float, extends over as it should. The drop-menu is actually a horizontal nav bar, now with the drop effect of putting another horizontal SUB-nav bar underneath it.

As soon as I added this drop nav bar, the peek-a-boo occured, only (here's the weird part) it peek-a-boo's (causes to disappear) all of the BACKGROUND in the content <div> over which the sidebar floats, but not any of the content itself. As soon as I mouse over any link in the nav bar, the background reappears.

I have had no luck finding information about backgrounds disappearing, so I thought I'd bring the problem here and see if anyone has any advice.

The bug, obviously, occurs only in IE6 (actually, I haven't tested it in IE 5 or NS, but Firefox handles it fine).

I'm going to hold off on posting code, hopeing for now that someone out there will know a possible solution without having to see the code. I recognize that this is most unlikely, but if I can solve this without flooding the forum with more code samples, I'd like to.

If nobody can propose a solution, I'll post the relevant code.

I know this a long shot, but if you think you have ANY ideas, please share them. PLEASE.

Thanks.

[DrDoc]

I've come across this problem in the past too... I tried all sorts of "medicine", but neither seemed to have any effect on the bug. That's when I realized that the element triggering the bug was actually the parent of the element experiencing the bug (if you follow me)... in which case the bug was transferred from the parent to the child because of yet another margin related bug. Solution? Like you said, neither "common" solution worked, which got me thinking to reverse the hacks. In my particular case, explicitly setting

position:static

got rid of the bug.

[createErrorMsg]

I applied position:static to the parent element, like you said, and it appears to have fixed things! The computer I'm on now only has access to IE5.0 (don't laugh) so I'll have to text later on IE 6.

Doc, you are a master. Send me the bill, I'll pay even if the insurance won't.

Question: If the parent element in question already has a position:relative (because it contains absolutely positioned elements) is the only choice to nest another <div> and give it the position: static?

[DrDoc]

...or apply position:static to the child...