Chrome 31 causes (some of) the RadEditor dialogs to break - they become very small and unusable when the content is received: http://screencast.com/t/XYWdPxSYloE.
This seems to be a browser issue and it does not manifest with the next official beta. The investigation is ongoing and if the problem is not fixed in the next official Chrome release fixes will be considered in our source code.
In the meantime, there are two possible workarounds:
1) force a resizing of the dialog when the command is executed:
OR
2) use browser windows instead of RadWindows for the dialogs:
This seems to be a browser issue and it does not manifest with the next official beta. The investigation is ongoing and if the problem is not fixed in the next official Chrome release fixes will be considered in our source code.
In the meantime, there are two possible workarounds:
1) force a resizing of the dialog when the command is executed:
<telerik:RadEditor runat=
"server"
ID=
"RadEditor1"
OnClientCommandExecuted=
"editorCommandExecuted"
>
</telerik:RadEditor>
<script type=
"text/javascript"
>
function
editorCommandExecuted(editor, args) {
if
(!$telerik.isChrome)
return
;
var
dialogName = args.get_commandName();
var
dialogWin = editor.get_dialogOpener()._dialogContainers[dialogName];
if
(dialogWin) {
var
cellEl = dialogWin.get_contentElement() || dialogWin.ui.contentCell || dialogWin.ui.content,
frame = dialogWin.get_contentFrame();
frame.onload =
function
() {
cellEl.style.cssText =
""
;
dialogWin.autoSize();
}
}
}
</script>
OR
2) use browser windows instead of RadWindows for the dialogs:
<asp:ScriptManager runat=
"server"
/>
<telerik:RadEditor runat=
"server"
ID=
"RadEditor1"
OnClientLoad=
"OnClientLoad"
>
</telerik:RadEditor>
<script type=
"text/javascript"
>
function
OnClientLoad(editor) {
if
($telerik.isChrome)
editor.set_useClassicDialogs(
true
);
}
</script>