If I change the hieght on the menu, it seems like the menus under it don't line up correctly.
<
ig:WebDataMenu ID="menuAction" runat="server" StyleSetName="VerusActionMenu" StyleSetPath="~/Styles" onitemclick="menuAction_ItemClick" Height="21px">
If you look closelt, you will see there is a gap between the "Select an action..." item and the box around the child menu items. I suspect I am missing something from the style , but I can't figure it out. Any ideas?
It would be greatly appreciated.
Thanks in advance.
Hi,
I see that you are using a custom styleset that you have done on your own. I would say to try this when you use the Default theme of the control, if there is no problem, which most probably will be the case, then try to determine where is the problem in you custom datamenu.css file.
I would point you too look at the MenuGroup* classes. Also if you are using 10.3 release the menu has changed rendering. It now supports scrolling and there is additional scrolling DIV rendered - you have to adjust your custom themes to it.
Hope this helps.
Thanks,
Lubomir
Thanks for the reply, but it also happens with the default style.
It is using the default style and the gap is still there.
I know exactly what is the problem. Setting height on the WebDataMenu adds style="height:21px" to the main control DIV. It clips any content that goes beyond the DIV. But when menu items are opened their subgroups are positioned relatively to the menu item dimensions. So the contents of root item "File" are positioned relatively to the "File" LI element size.
Until there is a fix you can workaround the issue by setting negative offset of the corresponding menu groups like this. <GroupSettings OffsetY="-7" /> Then the gap will close. But when we fix this, then your menu groups will appear above the parent menu. So you have to get it back to 0. You can contact developer support to create a support case for this problem.
Even better solution is to add <GroupSettings Height="21px" /> to the menu. Then you will not need to add OffsetY to all of the children of the root items. This way when we fix it your fix will still work and there will be no need to worry for regressions.