Brandon Haynes wrote Hi Cuong, I use Telerik's RadMenu exclusively, but since no one else has responded maybe I can yield some insight into your problem. To diagnose problems like these, I suggest looking at the menu navigation provider and seeing how the relevant values are being used.  Looking in Library/Providers/NavigationProviders/DNNMenuNavigationProvider/DNNMenuNavigationProvider.vb, I see the CSSSeperator attribute being used as follows: If String.IsNullOrEmpty(SeparatorHTML) = False Then  If CSSSeparator <> "" Then strSeparatorClass = CSSSeparator  strSeparator = SeparatorHTML End If ... If String.IsNullOrEmpty(strSeparator) = False AndAlso strType = "All" Then 'strType <> "Left" AndAlso strType <> "Right" Then  objMenuItem.LeftHTML &= GetSeparatorMarkup(strSeparatorClass, strSeparator) End If So, SeperatorHTML must be specified in order for this attribute to be used.  Once the strSeparatorClass is initialized, it is only used when strSeparator is non-empty AND strType == "All".  Only then is the generated markup value appended to the results. Pretty confusing, huh? Brandon

Brandon,

Thanks for the indepth explaination. However, I did implement the SeparatorHTML along with CSSSeparator, but no luck. I think I need somebody to help set it on debug mode to test it.

Telerik is pretty good. I also use it for our clients. However, just want to fully understand how dnnMENU work in different context.

I tryed a long time ago , 2006 I think , to get  attention of the problem.

I discussed in the forums (jon H), made a few posts in gemini. Some of them still there. One even telling its fixed.

But , but the documentation and the real world doesnt match.

Maybee it is fixed in 5.0 but who knows the DnnMenu are not a function that seems to bee tested so I doubt it will work as expected in 5.0 eiter.

Maybee just the documentation that is wrong who knows ... who cares..

Maybee the core team should.. I dont know...

Been a long time since I have looked at this.  Salar is correct on one thing, those properties are carry over from Solpart's implementation.  Jan is also right, in that the document was not updated to reflect what actually got implemented.  That said, if you look at the code, you will see that if those properties were implemented all that would happen would be the SeperatorHTML (left/right) included would simply get wrapped in a SPAN tag with a class defined.  I'm guessing the reason I commented out the menus ability to do this is someone suggested this was not needed as we are already specifying HTML, which could be its own tag. 

So to get the ability to specify class tags for the seperators it should be as simple as specifying your classes in your seperators.  Instead of

SeparatorLeftHTML="LEFT" CSSLeftSeparator="myleftseparator"

You code this

SeparatorLeftHTML="<span class=myleftseparator>LEFT</span>"

This gives you complete control over how it gets rendered (you aren't stuck with SPAN tags).