Why is the submenu showing up on the top instead of the bottom? and this if I place a <p> </p > otherwise I would not even see the submenu at all<form id="form1" runat="server"> <div> <p> </p> <ignav:UltraWebMenu ID="UltraWebMenu1" runat="server"> <ExpandEffects ShadowColor="LightGray" Type="Slide" Opacity="80" ></ExpandEffects> <Items> <ignav:Item Text="options A"> <Items> <ignav:Item Text="1a"></ignav:Item> <ignav:Item Text="2a"></ignav:Item> </Items> </ignav:Item> <ignav:Item Text="options B"> <Items> <ignav:Item Text="1b"></ignav:Item> <ignav:Item Text="2b"></ignav:Item> </Items> </ignav:Item> </Items> </ignav:UltraWebMenu> </div> </form>
It happens because of lack of content on the page. Because of standards mode (well defined DOCTYPE) IE does not return actual height of visible document, but just content area. Which in case of lack of content is empty and very short in height. That's why menu is "thinking" here is not enough free space to display on bottom and tries to display on top.
Possible workaround is to make content on page (just BR works) or to remove DOCTYPE declaration.
Hi, This is not the case since what I was demoing was just a snippet of the entire page.
The real page as part of a master page. This aspx page also has a usercontrol been the menu. There is a lots of content within the entire rendered page. With 2008 vol3 was no problem with submenu but upgrade to 2009 vol1 and then my submenu was gone. The solution found was to set the property "EnhancedRendering="False".
No idea why got to do this!
Is there a definitive answer on this one yet?
I have a submenu that used to display correctly in 8.2. However, it no longer shows up after upgrading to 9.1. Setting "EnhancedRendering = False" makes the submenu show up, but I lost the island background, so I would prefer to keep "EnhancedRendering = True". While there is plenty of content on the page, my menu is the sole control inside a standard Panel control and the panel height = the top-level menu height.
We made a fix or that. However it will be include in July Service Release, which is expected to come out by the end of this month.
I did not see this fix listed in the release notes for the July service release. Can you please confirm it did indeed get released?