Hello Bryan,
You are correct this issues are confirmed as bugs and I will log them into our feedback portal.
As a token of gratitude I am updating your Telerik points.
For the time being I succeeded to workaround the issues with the following markup:
<
table
cellpadding
=
"3"
width
=
"1000px"
border
=
"0"
>
<
tr
align
=
"left"
>
<
td
>
<
asp:Label
runat
=
"server"
ID
=
"lblName"
Text
=
"Name"
/></
td
>
</
tr
>
<
tr
align
=
"left"
>
<
td
>
<
telerik:RadTextBox
runat
=
"server"
ID
=
"txtName"
MaxLength
=
"100"
Width
=
"450px"
/></
td
>
</
tr
>
<
tr
align
=
"left"
valign
=
"top"
>
<
td
>
<
telerik:RadTabStrip
runat
=
"server"
ID
=
"ts1"
SelectedIndex
=
"0"
MultiPageID
=
"mp1"
Skin
=
"Default"
Align
=
"Justify"
<Tabs>
<
telerik:RadTab
Text
=
"Details"
Value
=
"detail"
PageViewID
=
"pvDetails"
/>
<
telerik:RadTab
Text
=
"Question"
Value
=
"qn"
PageViewID
=
"pvQn"
/>
<
telerik:RadTab
Text
=
"Guidance"
Value
=
"guidance"
PageViewID
=
"pvGuid"
/>
</
Tabs
>
</
telerik:RadTabStrip
>
<
telerik:RadMultiPage
runat
=
"server"
ID
=
"mp1"
SelectedIndex
=
"0"
CssClass
=
"multiPage"
>
<
telerik:RadPageView
runat
=
"server"
ID
=
"pvDetails"
>
<
center
>
<
h2
>Not editor</
h2
>
</
center
>
</
telerik:RadPageView
>
<
telerik:RadPageView
runat
=
"server"
ID
=
"pvQn"
>
<
center
>
<
br
/>
<
table
width
=
"95%"
>
<
tr
align
=
"left"
>
<
td
>
<
telerik:RadEditor
ID
=
"txtQuestion"
runat
=
"server"
Height
=
"350px"
Width
=
"740px"
ToolsFile
=
"CustomToolsImagesFile.xml"
ConvertTagsToLower
=
"True"
SpellEditDistan
ToolbarMode
=
"Default"
OnClientLoad
=
"OnClientLoad"
>
</
telerik:RadEditor
>
<
br
/>
</
td
>
</
tr
>
</
table
>
</
center
>
<
br
/>
</
telerik:RadPageView
>
<
telerik:RadPageView
runat
=
"server"
ID
=
"pvGuid"
>
<
center
>
<
br
/>
<
table
width
=
"95%"
>
<
tr
align
=
"left"
>
<
td
>
<
telerik:RadEditor
ID
=
"txtGuidance"
runat
=
"server"
Height
=
"400px"
Width
=
"99%"
ToolsFile
=
"CustomToolsImagesFile.xml"
ConvertTagsToLower
=
"True"
SpellEditDistan
ToolbarMode
=
"Default"
OnClientLoad
=
"OnClientLoad"
>
</
telerik:RadEditor
>
</
td
>
</
tr
>
</
table
>
</
center
>
<
br
/>
</
telerik:RadPageView
>
</
telerik:RadMultiPage
>
</
td
>
</
tr
>
</
table
>
<%-- The following script fixes the problem with the editor set with toolgroups having dockingzone=bottom attribute --%>
<
script
type
=
"text/javascript"
>
Sys.Application.add_load(function () {
var txtQuestion = $find("<%= txtQuestion.ClientID %>");
var txtGuidance = $find("<%= txtGuidance.ClientID %>");
txtQuestion.get_element().style.height = "99%"
txtGuidance.get_element().style.height = "99%"
txtQuestion.repaint();
txtGuidance.repaint();
});
var oldOnresizeEnd = Telerik.Web.UI.RadEditor.prototype.onResizeEnd;
Telerik.Web.UI.RadEditor.prototype.onResizeEnd = function () {
oldOnresizeEnd.call(this);
this.get_element().style.height = "";
}
</
script
>
<%-- The following fixes the problem with the wrong toolgroup collapsing in IE7 (compatibility mode) --%>
<
script
type
=
"text/javascript"
>
function OnClientLoad(editor, args) {
if (editor.isVisible()) {
fixToolbarsInIE(editor);
} else {
editor.add_firstShow(function () {
setTimeout(function () {
fixToolbarsInIE(editor);
}, 0);
})
}
}
function fixToolbarsInIE(editor) {
if ($telerik.isIE) {
var $ = $telerik.$;
var editorID = editor.get_id();
var topTD = document.getElementById(editorID + "Top");
var toolGroupElements = $(topTD).find(".reToolbar");
for (var i = 0, l = toolGroupElements.length; i <
l
; i++) {
calculateTools(toolGroupElements[i]);
}
}
}
function calculateTools(toolGroup) {
var
tools
=
toolGroup
.children;
var
size
=
0
;
for (var
i
=
0
,
l
=
tools
.length; i < l; i++) {
var
tool
=
tools
[i];
size += tool.offsetWidth;
}
toolGroup.style.width
=
size
+ "px";
}
</script>
The problem with the toolgroups is that under IE7 (compatibility mode) there is a logic that modifies the width of the HTML elements and restricts the inner tools to stay fixed.
The problem with the height of the editor stems from an improvement made on the resize calculation. It appears that when a dockingzone="bottom" is used the height is not calculated correctly. A better solution from the one suggested in the example markup is not using this attribute for the time being, although I hope the above fix should be working properly.
Let me know if you have further concerns.
Regards,
Ianko
Telerik
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the UI for ASP.NET AJAX, subscribe to the
blog feed now.