Bear with me, please. I'm not trying to be a jerk in this post...I'm just not sure I understand the benefits of this CSS Friendly menu control. A few issues I've encountered while using a horizontally-oriented menu:

1. some menu items extend beyond the visible portion of the page. The default asp:net control handles this gracefully by wrapping the menu items to the left when necessary. This issue was raised back in Oct 2006 and again in January 2007...it still isn't fixed, though.
2. if you add enough menu items would normally extend beyond the visible portion of the page, the "visibility:hidden/visible" attribute ensures that the browser will display a horizontal scrollbar wide enough to cover the area that would be displayed if all items were visible. Modifying the code to use "display:none/inline" helps a bit but the scrollbar re-appears on mouse-over thanks to the previous issue (menus extend beyond page width).

I know that this is free code but there don't appear to have been any updates since the initial release. Is anyone really working on it? (And the Codeplex DLL-based solution isn't what I'm looking for since [a] the last update was back in March and doesn't fix these issues; and [b] I'd prefer to avoid adding another DLL when I only need a menu. I'd love to say that I can help but quite frankly I don't have the time...nor the CSS skills, I suspect.)

Again, I'm just not sure what's the benefit of using these controls. Right out of the box...the menu has some fairly big issues. Say what you want about the default, table-based asp:menu control that MS offers, it does work. The only reason I'm not using the default asp:menu control provided by Microsoft is that I wanted to show the complete "trail" of active menu items (hover color displayed down the hierarchy rather than just the active menu item) and I noticed that the CSS Friendly menu control offers that feature by default...that is, by the way, an excellent feature. That said, I just want to have a functional menu control that provides a nice look & feel...ideally, out of the box. I'm just a corporate wage slave and I'd much rather spend my time solving actual business problems than tweak JS code to ensure a control behaves the way it should....especially when I suspect that the issues I mentioned above have already been encountered and solved in the community.

It's been a reallllllllllllllly long Monday, folks. Tell me, am I missing something? (It's distinctly possible!) Or should I just go back to the default menu control? Seriously, I would appreciate any constructive suggestions. Thanks!

The project is still maintained, the last update was 1 month ago. You can open up a work item, although it's up to the developer to decide its priority. The nice thing is that other people can vote your work item after you have created it, which is a way to increase priority by popular demand.

The highlighting of menu items all the way up the hierarchy can be done with a few lines of code for the default menu adapter as well, so you might still consider that.

You're not going to believe me but I too am not trying to be a jerk in responding...but if you have so many items in a dropdown list that they extend beyond the borders of your lowest-resolution target browser, then you have an information architecture problem -- not a menu problem.  No one likes to scroll dropdown menus.  You're using the wrong control for the job at that point.  The fact that the MS menus handle this situation is admirable but (in my opinion and only mine) they're handling a situation that should not occur.  My suggestion is to use the MS menus and come back to the CSS menus when you can tame your site's architecture.  Others here would probably disagree with me.

michielvoo

 Thanks for the helpful response! I do see now that there have been updates to the Codeplex source. I was originally looking at this page...

http://www.codeplex.com/cssfriendly/Release/ProjectReleases.aspx?ReleaseId=2159

...and saw that there hadn't been any DLL releases. My bad. As you suggested, I'll probably just go back to using the default menu control and tweak things to display the highlighted hierarchy. I'm guessing this is a just a CSS change...? Anyhow, thank you!

/*************************************************************/

camera

Actually, I don't think you were trying to be a jerk and didn't take your response as such. Let me clarify, though...the problem I'm facing is not that the menus extend beyond the bottom of the page. Rather it's that the menu is aligned against the right side of the page and the right-most top-level element has submenus. That all works fine but any submenus for those menu items (top-level >> submenu >> submenu) will disappear off the right side of the browser window. That's not a wildly atypical scenario and I think that most modern dynamic menus handle such situations gracefully. If you disagree and can offer some further suggestions, please do let me know.

 Thank you both for your responses!