Hi.
I've been having problems getting the ASP.NET AJAX controls to work. No problems with the beta, so I'm a bit puzzled when there has been no change in our code. Now we have a problem with RadEditor.
We're using the default skin and create the editor in code behind. We're using a user control for editing RadGrid records. We link to the CSS on the page using this code:
<link href="/Skins/Default/Editor.Default.css" rel="stylesheet" type="text/css" />
This has been working until we upgraded to ASP.NET AJAX.
The skinning is perfect in IE7. In Firefox 3 it doesn't work, assuming the same problem with Firefox 2. Look at this:
http://temp.kg-grude.no/editor_problem.jpg
Any ideas what could be causing this?
Kind regards,
Kjell
I've been having problems getting the ASP.NET AJAX controls to work. No problems with the beta, so I'm a bit puzzled when there has been no change in our code. Now we have a problem with RadEditor.
We're using the default skin and create the editor in code behind. We're using a user control for editing RadGrid records. We link to the CSS on the page using this code:
<link href="/Skins/Default/Editor.Default.css" rel="stylesheet" type="text/css" />
This has been working until we upgraded to ASP.NET AJAX.
The skinning is perfect in IE7. In Firefox 3 it doesn't work, assuming the same problem with Firefox 2. Look at this:
http://temp.kg-grude.no/editor_problem.jpg
Any ideas what could be causing this?
Kind regards,
Kjell
2 Answers, 1 is accepted
0
Accepted
Hi Kjell,
Thank you for the screenshot - most probably you have some global style (applied to LI tags) that spoils the editor's design. Please check your global styles and isolate the problem.
If you are not able to isolate the problem please open a support ticket and send us your runnable project or a sample one in which the problem can be reproduced. Once we are able to reproduce the problem on our side we will do our best to provide a solution.
In general, it is not recommended to use global styles with third party controls because obviously the third party controls consist HTML and the global styles can easily ruin their design.
Best regards,
George
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thank you for the screenshot - most probably you have some global style (applied to LI tags) that spoils the editor's design. Please check your global styles and isolate the problem.
If you are not able to isolate the problem please open a support ticket and send us your runnable project or a sample one in which the problem can be reproduced. Once we are able to reproduce the problem on our side we will do our best to provide a solution.
In general, it is not recommended to use global styles with third party controls because obviously the third party controls consist HTML and the global styles can easily ruin their design.
Best regards,
George
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
kgg
Top achievements
Rank 1
Rank 1
answered on 09 May 2008, 02:18 PM
In case your're interested I manaaged to figure out the problem. The only global styles I have is div positioning and header/font tags, but the problem did have something to do with global styles nevertheless.
I have the following in my master page:
<link rel="stylesheet" media="print" title="Printer-Friendly Style"
type="text/css" href="/Office2007Client/Css/PrinterFriendly.css" />
I managed to isolate the problem to this:
title="Printer-Friendly Style"
By removing this the editor was skinned perfectly in both IE and Firefox.
Kjell
I have the following in my master page:
<link rel="stylesheet" media="print" title="Printer-Friendly Style"
type="text/css" href="/Office2007Client/Css/PrinterFriendly.css" />
I managed to isolate the problem to this:
title="Printer-Friendly Style"
By removing this the editor was skinned perfectly in both IE and Firefox.
Kjell