3 Answers, 1 is accepted
0
Hi Falk,
Please open a support ticket and send us some screenshots (and video if possible) that demonstrate the problem, along with a detailed information about your exact scenario. Once we have a better understanding on your exact scenario, we will do our best to provide a solution.
In addition, please check for some global CSS styles applied to the editor's tools.
Have a great weekend,
George
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Please open a support ticket and send us some screenshots (and video if possible) that demonstrate the problem, along with a detailed information about your exact scenario. Once we have a better understanding on your exact scenario, we will do our best to provide a solution.
In addition, please check for some global CSS styles applied to the editor's tools.
Have a great weekend,
George
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Falk
Top achievements
Rank 1
Rank 1
answered on 13 Jun 2008, 03:27 PM
Hi George,
I don't know how to demonstrate it, because there is nothing to show. If I click in the fullscreenmode on the fontsize dropdownbox the menu to choose the fontsize does not show up. The same thing for all the other dropdownboxes. We use it in Sharepoint Moss (german version Servicepack 1) and made no configurations on the standard css.
Gest regards
Falk
I don't know how to demonstrate it, because there is nothing to show. If I click in the fullscreenmode on the fontsize dropdownbox the menu to choose the fontsize does not show up. The same thing for all the other dropdownboxes. We use it in Sharepoint Moss (german version Servicepack 1) and made no configurations on the standard css.
Gest regards
Falk
0
Hi Falk,
Thanks for reporting this. We are actually aware of this issue. It is caused by the fact that MOSS 2007 does not use a XHTML compliant doctype by default. Our controls are designed to run primarily in a compliant environment, which is why there are some problems in the default MOSS scenario. In this case, we did some research and managed to find a workaround for the problem. We plan to release an updated RadEditor for MOSS build at the end of next week (together with the RadControls for ASP.NET AJAX service pack release).
If you do not wish to wait until then, you can try adding a doctype to your MOSS master page. For example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
We apologize for the inconvenience.
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thanks for reporting this. We are actually aware of this issue. It is caused by the fact that MOSS 2007 does not use a XHTML compliant doctype by default. Our controls are designed to run primarily in a compliant environment, which is why there are some problems in the default MOSS scenario. In this case, we did some research and managed to find a workaround for the problem. We plan to release an updated RadEditor for MOSS build at the end of next week (together with the RadControls for ASP.NET AJAX service pack release).
If you do not wish to wait until then, you can try adding a doctype to your MOSS master page. For example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
We apologize for the inconvenience.
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center