Timo - definitely the ones you have mentioned, but a couple of other ones that come up - more specifically are:

1. Horizontal Item Separators - A decent, cross-browser working example.
2. Getting rid of icons / customising icons / including icons
3. Styling the Module Drop-down Menu
4. Sorting out dropdown menu "dissappearing" behind flash - though the solution doesn't really lie with the menu
5. How absolute positioning "messes up" the flyouts / display of the menu
6. For DNN 5 NavMenu - the rendermode for UL rendering and the new pseudo classes .first, etc... (in this thread there is reference to some notes and video on this

Basically people want a few good, clean, semantic, cross-browser, css-commented examples of the menu - for both DNN4.9+ and DNN5+ installations.

Jon

Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

I had actually forgotten about that video. I'd watched it way back when DNNNav 2 was in beta, guess I have some homework over the weekend.

One other question - I'd mentioned this in an earlier thread, but I keep getting an annoying dotted-border around my DNNNav object when the mouse is clicked (verified as showing in Firefox 3.5.1). A site displaying this can be found at http://smc.dev.netmds.com (I'm not thrilled with the look, but a committee made the decisions, not me).

The code for the menu (both ASCX token and CSS Styles) were adapted from Lee Sykes' recent article on styling DNNNav, but I've seen this effect before in my style-from-scratch DNNNav elements. I've checked the code against the Extropy skin, and I don't see any styles that could create such an effect, like a border style. It reminds me alot of the box we'd see back when the object/embed issue was being addressed with Flash media a couple years back... Thoughts?

Quick Update:  I tried a couple tricks, the a:focus { border:0; } trick, and tried focusing the CSS selector more precisely, but the way I've fixed it (for now, I guess) was to add:   * {border:0;} to my skin.css file. I'm hoping this doesn't cascade badly and cause more problems, but it works for now I guess.