Thank you for looking into this.  I will have to look at what you have regarding the missing fourth item in the menu.  Did you happen to look at the Sandbox example I attached in the OP?  It had all the issues I mentioned.  I had the problem in that sample which is as basic as it gets.

As to the other issues. You mention editting the weddatamenu.css directly.  Where might I find that and how might I include that in my project so that the each other developers will not have to make this change, too?  Also will I have to overwrite this css each time we get a new version of Infragistics?

Hello Greg,

I have opened a support request for this forum post so we may research this behavior further.   Please use the following link to log onto your account at Infragistics.Com:

<https://www.infragistics.com/Membership/MySupport.aspx>

Once you are logged onto your account, go to My Support Activity to view the progress of this support request.  An update will be sent to you in the support request with any new information we find.

Please let me know if you have any questions.

Hi Prabha,

Will you be posting any resolution on this thread as well (better than opening a ticket for everyone who views this thread).

We've run into the same disappearing menu item issue (#1 on the original post), and our edits of ig_datamenu.css (.igdm_ClaymationMenuItemHorizontalRootLink, in our case) have not resolved the issue for us.

Charles

Hello Charles,

I will update this forum thread once there is a resolution for the missing item.

Let me know if you would like me to notify you once this is resolved. I will create a case for you and link it to development issue.

Please let me know if you have any further questions regarding this matter.

Hi Prabha,

After a *lot* of experimentation, I think I see what is happening.

It seems that the menu calculates what size it should be and then, depending on font size and weight, renders what will fit in that box, cutting off anything that won't fit.

My setup: I'm using StyleSetName="Claymation", and I've been modifying ig_datamenu.css. In my case, the class that is causing the problem turns out to be .igdm_ClaymationControlHorizontal a:link, .igdm_ClaymationControlHorizontal :visited (because of settings in .igdm_ClaymationControlHorizontal -- including overflow: hidden;).

The CSS class consists of:

    font-family:Verdana,Arial,Lucida Grande,Lucida Sans Unicode,Lucida,Helvetica,Sans-serif;   
    font-size: 10px;
    font-weight: bold;
    color: #ffffff;

With this font size and weight, all the elements of the menu display (depending on the user type, one of two menus can display, one considerably shorter than the other). Also, the full menu displays if I comment out the weight or change it to font-weight: inherit.

However, as I increase the font size, more and more items get removed from the right-hand side of the menu (the only time nothing gets lost is for size = 10px or size = inherit). Eyeballing both the shorter and longer menus, I can approximate where the cutoff point will be, and that point is different for the two menus, supporting my conjecture that an internal calculation is done for each menu, not that there is some absolute cutoff point.

The easiest way to attempt to replicate this is to focus on the font size rather than the font weight, as using the size is obviously easier to increase/decrease the overall size of the menu.

HTH,

Charles

As a follow-up to my previous post:

• Changing the overflow setting did not make a difference.
• What did make a difference: The CSS class has a bunch of fonts listed in font-family, presumably using the first one on the list that the browser supports. Removing Verdana with a font-size of 12px displayed the complete menu. Since Verdana is a wider font (by eyeball) than Arial or Sans-serif (both of which I tested), that would indicate to me that rendering occurs after the size of the menu has already been determined (and, to possibly anticipate a question, width of the menu is set to 100%).

Charles

Hello Charles,

I heard back from development team that setting Enablescrolling property to false will resolve the issue of missing item. By default this property is true.

Setting EnableScrolling to true will result to fixed width of the <ul> element which holds all the root menu items. The problem comes when there is bold style applied to the menu container, because in the calculation of the <ul> element width is not taken.

Please let me know if you have any further questions regarding this matter.

Thanks, Prabha, that did the trick.

For others reading this thread, EnableScrolling is a WebDataMenu property, not some obscure CSS tag.

Charles

What if I do need my menu to scroll? My horizontal menu is limited by certain width, and the items are added to it in server-side code at runtime. So when there're more items than menu can fit, I need it to scroll. And it works - it scrolls and all items appear correctly - in all browsers but FireFox. In FireFox last item is always missing.

Any idea how to make this work with scrolling enabled? thanks