Load in IE this demo: http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx Enter in HTML mode - <p><a href="stm:b4f0c9ac-9a08-4c9f-8caf-39ccd4a83fc9" class="stm" contenteditable="false">Statement 111</a></p> Switch to Design mode Search for Statement with the Find and Replace dialog The dialog won't be able to locate and highlight the link
Hi there, The problem appeared to be due to IE selection API and range (setStart, setEnd and select) which does not select/highlight the HTML elements having applied contentEditable attribute. The only possible workaround is to replace the contenteditable attribute with _contenteditable when opening the dialog in the OnClientCommandExecuting event of RadEditor, and return back the original attribute from _contenteditable to contenteditable when closing the dialog. For your convenience I developed a solution which you can apply to its project: <script type="text/javascript"> function OnClientCommandExecuted(editor, args) { if ("FindAndReplace" == args.get_commandName() && Telerik.Web.Browser.ie) { editor.set_html(editor.get_html(true).replace(/contenteditable/gi, "_contenteditable")); alert(editor.get_html(true)); //Get reference to parent RadWindow var wnd = Telerik.Web.UI.RadWindowController.get_activeWindow(); //When closing the dialog var handler = function (sender, args) { //Restore the original contenteditable attributes editor.set_html(editor.get_html(true).replace(/_contenteditable/gi, "contenteditable")); alert(editor.get_html(true)); //Remove the close handler wnd.remove_close(handler); } wnd.add_close(handler); } } </script> <telerik:RadEditor ID="RadEditor1" runat="server" OnClientCommandExecuted="OnClientCommandExecuted"> <Content> <p>test</p> <p contenteditable="false">line one</p> <p>line two</p> <p contenteditable="true">line three</p> </Content> </telerik:RadEditor>
Hi Rumen, Just checking back to see if you could provide any update on this item. Regards, Manju.
Question - This item is being approved and shows as scheduled R3 2017, does it mean the fix will be available in Q3 of 2017? May be by Sep! We are looking forward to having this fix incorporated in our Oct release as this is one important feature in the application. Appreciate your help.