Web page hangs with long running script error when the Foreground color of table content is cleared in IE11. Steps to reproduce: 1. In IE 11 Go to editor demo http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx 2. Click HTML view and delete everything 3. Copy this into editor <html> <head> <title></title> </head> <body> <table> <tbody> <tr> <td style="color: #000000;">Lorem ipsum</td> </tr> </tbody> </table> </body> </html> 4. Go to design mode highlight some text and click on the "Foreground color" button, select the clear choice (upper left) 5. Web page hangs with long running script error. (It has something to do with that style on the TD)
Using the Image Map Editor to create a mapped area over the entire image, causes the image to be unelectable.
If the content contains html, head and body tags (Full HTML editing), and switching to Design mode causes a slightly slower rendering. If the same HTML is used directly in the, the design mode renders as expected.
As the selection changes when typing inside textbox, JavaScript errors are being thrown.
For example, checkboxes with plain text as labels before them do not appear selected in RadEditor: HTML: Checkbox: <input type="checkbox" />
Using the desktop MS Word, pasting is fine. Using the Online version, the HTML gets messed up with plenty of unneeded DOM attributes and additional elements. It would be best if pasting provides a cleaner HTML as it is when pasting form the desktop MS Word.
Pasting complex lists from MS Word are not properly translated to HTML list nesting. Often, the sub lists are mixed up with their parent lists.
This may result in invalid content being sent to the server or incorrect behavior of the client-side.
The resize handle of the Editor is not visible if only only edit mode is active (e.g. Design mode). Steps to reproduce: 1. Run an Editor with the following configuration: <telerik:RadEditor ID="RadEditor1" runat="server" EditModes="Design" ></telerik:RadEditor> Result: The whole module row is not visible, including the resize handle.
Workaround: <telerik:RadTabStrip ID="RadTabStrip1" runat="server" MultiPageID="RadMultiPage1"> <Tabs> <telerik:RadTab Text="tab1" Selected="true"></telerik:RadTab> <telerik:RadTab Text="tab2"></telerik:RadTab> </Tabs> </telerik:RadTabStrip> <telerik:RadMultiPage ID="RadMultiPage1" runat="server"> <telerik:RadPageView ID="RadPageView1" runat="server" Selected="true">RadPageView 1</telerik:RadPageView> <telerik:RadPageView ID="RadPageView2" runat="server"> <telerik:RadEditor ID="RadEditor1" runat="server" EnableTrackChanges="true" TrackChangesSettings-CanAcceptTrackChanges="true" ToolsFile="ToolsTrackChanges.xml"> <Content> <p>paragraph 1</p> <p>paragraph 2</p> </Content> </telerik:RadEditor> </telerik:RadPageView> </telerik:RadMultiPage> <script type="text/javascript"> $telerik.$.extend(Telerik.Web.UI.RadEditor.prototype, { _initEvents: function() { var editor = this; if (editor.__original__initEvents) { editor.__original__initEvents(); } editor.add_domChange(Function.createDelegate(editor, editor._domChangedHandler)); editor.attachInternalHandler("keypress", Function.createDelegate(editor, editor._keyPressHandler)); editor.attachInternalHandler("keydown", Function.createDelegate(editor, editor._keyDownHandlerEnableTrackChangesOverride)); editor.attachInternalHandler("keydown", Function.createDelegate(editor, editor._keyDownHandler)); } }); </script>
When the EnableTrackCahnges functionality of the Editor is set to true, a context menu is shown only if the user right-clicks over a tracked change. Clicking over a not changed element does not pop-up any context menu (neither the Editor's not the browser one). The issue is reproducible in all browsers. Steps to reproduce: 1. Run the following configuration: <telerik:RadEditor ID="RadEditor1" runat="server" EnableTrackChanges="True"> <Content> <span>SPAN dssad</span> <div>DIV fsdfksjdfkf</div> <p>Paragraph jfdshfksjdhfksdhk</p> </Content> </telerik:RadEditor> 2. Right-click over a not track-changed element. Actual result: No context menu is shown. Expected result: The Editor's default content menu (or the browser on) is shown.
When a parent control is disabled by setting Enabled to false, all children controls should inherit the behavior and act as disabled. RadEditor does not follow this logic and stays enabled.
The first div element in the content is stripped out, every time a submit occurs with opened HTML tab.
Instead of null, the String.Empty can be used.
A possible workaround is to set the import step after all other rules in the CssFile of the RadEditor. CssFile would look like: .h1 { background-color: Aqua; } .div { color: Green; } @import url(StyleSheet.css);
There some issues when both features are enabled: - Add comment to tracked change is impossible; - Context menu is broken.
Currently, this command switches from Design to HTML mode and vise versa when EditType="Inline". In Normal editing mode this tool is disabled in the HTML mode and cannot be used, although it is useful and provides yet another layout option for the default look of the RadEditor. You can test the additional layout option by running this example: <telerik:RadEditor runat="server" ID="RadEditor1" EditModes="Design" OnClientModeChange="OnClientModeChange"> <Tools> <telerik:EditorToolGroup> <telerik:EditorTool Name="Bold" /> <telerik:EditorTool Name="ToggleEditMode" /> </telerik:EditorToolGroup> </Tools> </telerik:RadEditor> <script type="text/javascript"> function OnClientModeChange(sender, args) { setTimeout(function () { sender.get_toolAdapter().getToolByName("ToggleEditMode").set_enabled(true); },0) } </script> This tool can be redesigned to be available in the HTML mode in all cases not only when Inline editing mode is enabled.
If some textarea elements are added inside the content area, focusing and typing text inside is almost impossible. There are also cases, where the text overrides the element on typing. Additionally, any text input elements are difficult to be selected. It is required to click multiple times so to appear selected.
Using code behind or localization file to change the text of the Design, Preview or HTML buttons break the functionality that enables the end-user to change the modes. The following snippet can be used as a temporary workaround. <style type="text/css"> /* Fixes the visual glitch */ .reModes a { width:auto !important; } </style> <telerik:RadEditor runat="server" ID="RadEditor1" RenderMode="Lightweight" OnClientLoad="OnClientLoad"> </telerik:RadEditor> <script type="text/javascript"> function OnClientLoad(editor, args) { var $ = $telerik.$; if (editor.get_renderMode() != Telerik.Web.UI.RenderMode.Lite) return; var designAttr = editor.get_localization()["RadEditorDesignMode".toLowerCase()]; var htmlAttr = editor.get_localization()["RadEditorHtmlMode".toLowerCase()]; var previewAttr = editor.get_localization()["RadEditorPreviewMode".toLowerCase()]; $("a[title=\"" + designAttr + "\"]").attr("title", "Design"); $("a[title=\"" + htmlAttr + "\"]").attr("title", "HTML"); $("a[title=\"" + previewAttr + "\"]").attr("title", "Preview"); } </script>
When a tool has a longer name, part of the text drops to a new line, and causes incorrect layout. To resolve you can use the following CSS rule: .reDropDownBody a.reTool.reToolText { white-space: nowrap; }