well there has always been issues with the dnn menu for as long as I have developed for it. So the first thing I did in every dnn install was get a menu that actually works and follow standards or even better allow for custom html. I would advice you to ditch dnn:nav. I never saw the thing you descibed before but another reason to ditch it in my opinion. In firefox do a view generated source and you will see an even more crappy generated unordreded list structure with inline styles even

Just go with DDRMenu from dnngarden.com using tempaltes you can control any part of the html layout you want I use it for all my menus and because of the tempalting there isnt a menu I cannot recreate.

Armand Datema

Get my new skin ( lots of design variations [18 headers, 30 titlebars, 30 breadcrumbs, 3 footers ], 50+ typography containers , 50+ page templates and an online theme builder for unlimited skin variations) Aura>

For all your skin conversions

2DNN

Follow me on Twitter

 I can't argue with this statement.  I was so happy to find out about the Unordered list option, but once again it is something I have to learn instead of being able to use the very common unordered list style of navigation so many other sites use.

I would love to see DotNetNuke fix this so that I can start to use this as my default menu/navigation.  I don't want to have to use another nav, but I feel sort of forced to .

Michael Silva
Member of SeaDUG | www.seadug.com
President of Cornerpixel | www.cornerpixel.net