WebResources override style

2 posts, 1 answers
  1. Joseph
    Joseph avatar
    29 posts
    Member since:
    Jun 2014

    Posted 17 Jul 2014 Link to this post

    So i followed the steps on the following page in making a skin for a RadPanelBar, but on debug (see attached image) WebResource.axd is overriding the RadPanelBar stylesheet that i've created.  Please advice.

    <telerik:RadPanelBar runat="server" ID="RadPanelBar1" EnableEmbeddedSkins="false" Skin="YPPanel">
    PanelBar.ypmnet.css
    .RadPanelBar_YPMnet .rpGroup .rpLink:hover{ background: #bddeff;}
     
    .RadPanelBar_YPMnet .rpRootGroup .rpText
    {
        font: normal 12px Arial, Verdana, Sans-serif;
        color: #ffffff !important;
        padding: 5px 7px 5px 3px;
    }
     
    .RadPanelBar_YPMnet .rpSelected .rpText
    {
        font-weight: bold;
        font-size: larger;
    }
     
    .RadPanelBar_YPMnet .rpGroup .rpSelected .rpText
    {
        font-weight: bold;
        font-size: medium;
    }
     
    .RadPanelBar_YPMnet .rpRootGroup .rpDisabled:hover
    {
        cursor: default;
        text-decoration:none;
     }
      
     .RadPanelBar_YPMnet .rpGroup .rpDisabled:hover
     {
        cursor: default; text-decoration:none;
     }


  2. Answer
    Magdalena
    Admin
    Magdalena avatar
    421 posts

    Posted 18 Jul 2014 Link to this post

    Hello Joseph,

    Thank you for contacting Telerik support.

    Actually the name of a custom skin skin should be the same as the name used in selectors. For example if the skin name is  Skin="YPPanel", the selector will be ".RadPanelBar_YPPanel" instead of ".RadPanelBar_YPMnet". If there are some inbuilt styles that overwrite your custom styles, you can make selectors in your custom file stronger, for example by adding a "html" to the selector ("html .RadPanelBar_YPPanel" ).

    Regards,
    Magdalena
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top