Figured out that in nice-menus.css the use of
visibility: hidden;
and
visibility: visible;
can cause extra space below your footer. If you have extra white space below your footer, try this solution. I assume the problem occurs because all the ul's within ul's are rendered as if they are in a single vertical list and are later absolutely positioned. This causes the site to expand vertically as far down as needed depending on how many ul's and li's you have.

To fix it, we changed those lines of CSS, respectively, to:
display: none;
and
display: block;

Comments

ohkaiby’s picture

ohkaiby commented

Unfortunately, doing that seems to break the menu in IE 6.

EDIT: Was an issue in my css. This fix works.

For clarification, the following areas of nice_menus.css were changed:

ul.nice-menu ul: "visibility: hidden" > "display: none" (line 34)
ul.nice-menu li.over ul: "visibility: visible" > "display: block" (line 38)
ul.nice-menu:after: removed "visibility: hidden", but did not change "display: block" (line 47 and 51)
the huge section starting on line 53: "visibility: visible" > "display: block" (line 68)
the huge section starting on line 71: "visibility: hidden" > "display:none" (line 97)

However, there is a side effect, and that is that screen readers will not be able to even render the extra menus where the display is initially set to none.

add1sun’s picture

add1sun commented

This is a duplicate of #348410: 30 Blank Line Breaks at Bottom of Homepage but since this has more discussion in it, I'll close that one and move the talk here.

The reason we need to use visibility rather than display is to fix the IE7 ghost bug (#136702: Disappearing links in IE 7.0), so we'll need to see if we can come up with another solution.

add1sun’s picture

add1sun commented

I think this is another report but with sideways extension #363362: nice menu in header block with down causes web browsser to think more content to right....

add1sun’s picture

add1sun commented
Version: 5.x-1.4 » 6.x-2.x-dev

Moving to the latest dev version since it needs to be fixed there first, then backported. Also, I have no idea how to fix this while still keeping the IE7 ghost bug at bay, so this isn't likely to be fixed anytime soon.

monotaga’s picture

monotaga commented

subscribing

add1sun’s picture

add1sun commented
Component: CSS » Code
Status: Active » Postponed

Setting this to postponed until someone can come up with a workable solution (for IE7).

vordude’s picture

vordude commented
Status: Postponed » Closed (won't fix)