keeperofstars wrote superdmon: If I am not mistaken the difference your seeing is between using the skinobject and using the module. The skinobject has to create unique id's for every element it creates since these elements are part of the physical page. While when using the module the module itself is not actually generating any skinobjects. All it is doing is reading the page structure data and then creating an unordered list from it. No different then going into the html/textbox module and creating the same unordered list. Those id's your seeing will be different per installation and can change even per list anytime you make any changes to the whole site / menu. DNN basically just starts incrementing the id element for each instance. Let me know if you need any additional information. Is there a particular reason you need those ids?

keeperofstars,

thanks for the information and quick response, but I was able to stumble upon the solution you just wrote.  I put the skin object into my ascx file and BAM, I had ID's.  Unfortunately this creates another problem.  I'm using the IDs to do replacements on the Anchor text and substituting an image.  This creates a really cool looking navbar.  However, when clicking on one of my nav's it now disappears because the id gets replaced with "navCurrentLink"  ARGHH!!!  Is there anyway to disable the navCurrentLink ID replacement?  I've gotten so close...

superdmon

I made a post on an Housemenu image menu here: http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/mid/2108/threadid/95362/scope/posts/Default.aspx#95458

It's a technique to use page icons for the menu.

an example can be seen here http://cals.verhagenit.net/nieuwegein/Onderwijsbegeleiding/Identiteit/tabid/135/Default.aspx,

Hover over "vakken" and "HOOFDMENU", this is all Housemenu,  I do use a custom JS and CSS...

make sure every single tag is properly formed. If one of them is not properly formed then IE will throw a fit while firefox just fixes the issue for you. Now one other thing could be a related issue. There is a javascript function in Housemenu.

var ieUL's = o.Menu.getElementsByTagName('UL') from what I can tell it grabs the UL's id for use in IE. Its an IE function only from the code comments around the function. Not sure if your javascript is conflicting with it or if you just have a malformed tag somewhere in the ascx file. I recently had a > missing and the menu that resulted in IE was very weird but was completely fine in firefox. Man I wish we could just burn IE, and force the world to use firefox. lol Anyways, if you wouldn't mind could you send me that javascript? I am still learning the finer details of javascript, been a C++ / VB.net / asp.net programer that I am just now getting the chance to study javascript. I might be able to look through it as well and see if it would have any conflicts with the IE function. email: mathomp3@hotmail.com.  Oh and to look at the function / error I used firebug. You can add IE tab option add-on to firefox, it lets you swap the rendering engine on a page back and forth between firefox and IE. This way you can render a page as if it was your default IE installation, but within the firefox browser which allows you to use firebug to look at just what IE is really doing. I find this is much better then IE's webdeveloper option. Just a tip.