This is a migrated thread and some comments may be shown as answers.

[Solved] Style, theme, skin problems after upgrading to Q1 2009

1 Answer 125 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Anthony
Top achievements
Rank 1
Anthony asked on 20 May 2009, 07:19 PM
I found it's frustrating that everytime I upgrade telerik controls, I got all kinds of problem. No exception this time. After spent 30+ hours to fix the skin and style sheet problems, I got my application to be functional, but the look and feel is still not exact same as before. I found all in-line style is not working correctly. My question is can I still use in-line style? For example, I add style as follows:
then later I use that class mp or ts. but the float: left doesn't take effect.
<asp:Content ID="Content2" ContentPlaceHolderID="cph2" Runat="Server"
 
    <style type="text/css"
            .mp 
            { 
                border:1px solid #898c95; 
                background-color:#f1f1f1; 
                margin-left: 2px; 
                float:left; 
                width: 100%; 
                 
            } 
            .ts  
            {   
                text-align:left; 
                width: 160px; 
                margin-right:1px; 
                 
            } 
        </style> 
</asp:Content> 

Also, I have a custom skin for RadInput, I modify most of them with current naming convention, but I can't find any equivalent example for followings:
.radHint_Custom 
{
background: infobackground;
margin-top: 5px;
border: solid 1px black;
text-align: left;
overflow: auto; 
}

.radHint_Custom a,
.radHint_Custom a:visited,
.radHint_Custom a:hover
{
margin: 2px;
color: black;
text-decoration: none;
font-size: small;
}

1 Answer, 1 is accepted

Sort by
0
Ivo
Telerik team
answered on 21 May 2009, 07:06 AM
Hi Anthony,

It is unlikely that your styles are broken after upgrading to the latest version of RadControls. We do not use global styles in our skins, and each CSS rule is encased in a wrapping class. Usually our skins break when are used on websites that use global styles due to inheritance.

I took a look at your css, but unfortunately without having the actual HTML, the DTD and the entire layout I cannot help much. From what I see - the .mp class is wide 100% and is floated, which means that its right adjacent HTML will certainly not be positioned next to it, as 100% means 100% of the parent in standards compliance mode.

As of your custom skin of RadInput, you may use our online skin converter (http://converter.telerik.com/skinconverter/) that will convert your pre Q1.2009 skins to the new rendering and naming convention of our latest release.

Regards,
Ivo
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Tags
General Discussions
Asked by
Anthony
Top achievements
Rank 1
Answers by
Ivo
Telerik team
Share this question
or