Embeded Skins for Navigation
It seems that if you set the Wrapper CSS class (Skin) in a navigation widget Horizontal to Forest its not displaying correct. If you use Horizontal with drop down menus it is displayed correct (menu vs. tabstrip)
Why not use RadMenu for Horizontal (without drop downs as well)
I know that Navigation widget will be reworked for 4.2 and hope that
Horizontal, Horizontal with drop down, Vertical (as well as the missing Vertical with fly outs) will all be based on RadMenu instad of mixing (just one skin to be made)
BTW: In another post I voted that when using your own skin that enabledEnbededCSS would also be set to false. This would make the use of embeded skins - like forrest impossible. You would have to download the skin somewhere. So if for any reason the embeded skins should be usable (for comunity edition maybe) then the navigation should have an option
a) use embeded skins with dropdown to choose
b) use own skin then embendedSkins embededCSS set to false
PS: would it make sense to have the Horizontal with dropdowns default set to mouse over?
PS: I am not using embeded skins in production this is just a quick and dirty site to show the navigation concept to the client. Just wanted to style it a bit so it would not look to bad :-)
This is really unpleasant experience. We apologize for the inconvenience. There is a css conflict with the default Sitefinity theme and the styles of the Forest skin. To avoid all trouble use a theme different from Sitefinity default which is aimed to provide some basic styling. Then all will be styled properly.
As you know Sitefinity widgets rely heavily on RadControls and use their implementation to serve its needs. A feature of the rad controls is to set built in skins one of which is Forest. Sitefinity community edition will remain as it is for now because it provides core functionality for free and is aimed for simple sites.
These options ( a, b) are available, but not trough the backend UI, I also expect the improvement of the navigation so I am eager as you to see it.
To ( b ) the css from the skin gets in conflict with the other css applied to the page. This is expected as css applies the last rule of the same type it has so some of the rules must be changed and changing is trough editing the Theme ( all styling is there ).
PS:When selected Horizontal the user is prompted to go trough the options and this option is expanded so it is really easy to change Click to Mouse over.
the Telerik team
There is a css conflict with the default Sitefinity theme and the styles of the Forest skin.
I don't realy need it but it would be nice if Telerik would remove the conflicts sometime in the future
This is expected as css applies the last rule of the same
It might be expected but surly not appreciated.
so it is really easy to change Click to Mouse over
I know it's easy to change the question was is it not more likely that 95 % want a mouse over instead of a click and therefor change the default.
I really hope this will resolve. Currently the Basic Theme is styling all content and if you have "rtsLink" in your navigation which is the class assigned to horizontal navigation list item when you apply a Skin you target the same class. This is the conflict if you are using !important in custom css you avoid problems.
the Telerik team
The whole idea of embended skins is that you don't have to use your own :-)
Again I don't really need the embedded skins and just thought you might want to know that there is a problem :-)