Hi
Maybe having a related title to my post might elicit a response. :-)
I have a master page, which a RadMenu, to which I would like to add a RadRotator.
I am using a custom skin for the menu, so I have EnableEmbeddedBaseStyleSheet set to false.
But when I add the rotator to the master page, it loads the base css for the menu, which then overrides my custom skin.
If I comment out the RadRotator, the menu css works fine.
With the RadRotator in place, even if it has EnableEmbeddedBaseStylesheet="false", the webresource with the base css for the menu gets loaded and trashes the menu.
Does anyone have any ideas? Or is it not possible to use a rotator on a master page with the menu without the css conflicting?
Maybe having a related title to my post might elicit a response. :-)
I have a master page, which a RadMenu, to which I would like to add a RadRotator.
I am using a custom skin for the menu, so I have EnableEmbeddedBaseStyleSheet set to false.
But when I add the rotator to the master page, it loads the base css for the menu, which then overrides my custom skin.
If I comment out the RadRotator, the menu css works fine.
With the RadRotator in place, even if it has EnableEmbeddedBaseStylesheet="false", the webresource with the base css for the menu gets loaded and trashes the menu.
Does anyone have any ideas? Or is it not possible to use a rotator on a master page with the menu without the css conflicting?