Hovering over a node doesn't count as a hover over its parent when it is positioned above an element with overflow:auto. The practical use for this technique lies in CSS menus on sites that make use of the pre element.
Test page Workaround is not included
Reported by: Damien Bezborodow.
Mozilla | Reported on 23 February 2005.
This site is no longer maintained. I’m sorry, but it’s just too much work for too little return. You can continue to browse old bug reports, though.
Search reports by browser:
1 Posted by Tim Gross on 25 February 2005 | Permalink
I've actually recently ran into this bug on a new test Site I've been messing with. and I found that a work around is to not use Display:none; and Display:block;. But Rather position the child element off-screen, then reposition it by resetting it to auto.
It actually works quite well.
However, Moz1.4 due some other settings in my stylesheet would refuse to reposition the child element.
The reason the solution didn't work in Moz1.4 seems connected to borders/padding on the child elements and Display:Block on the parent element. I found that I could sort of get it working in Moz 1.4 by setting display:inline; on the parent element, but as soon as I added back the borders and padding on the child elements Moz1.4 would cause the parent element to mysteriously set the overflow on the parent element to hidden, even if you explicitly set it to overflow:show;. However now that I had set the parent elements to display:inline; moz1.0 would trigger the bug that repositioning originally fixed in moz1.0. However, even though moz1.4 was setting overflow:hidden on the parent moz1.0 was still trigger the focus bug, the fix worked if the child element had an older sibling that is an image.