The problem is due to the IE native focusing behavior of editable DIV elements. You can workaround this problem by overriding the setFocus method and implement an if statement that does not focus the content if the AutoResizeHeight is enabled: <telerik:RadEditor ID="RadEditor1" runat="server" AutoResizeHeight="True" ContentAreaMode="Div"> </telerik:RadEditor> <script type="text/javascript"> Telerik.Web.UI.RadEditor.prototype.setFocus = function () { try { if ($telerik.isIE && this.getSelection().isControl()) return; var area = this.get_mode() != $T.EditModes.Html ? this.get_contentWindow() : this._getTextArea(); if (this.get_contentAreaMode() == $T.EditorContentAreaMode.Div) area = this.get_contentArea(); if (area && area.focus && !this.get_autoResizeHeight()) area.focus(); } catch (e) { } }; </script>
With RadCloudUpload control the users will be able to upload files to Amazon S3 and Azure Blob storage. Also the developers could implement own storage providers and upload files to custom locations.
Can be reproduced with the following page setup: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="Default" %> <%@ Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head runat="server"> <title></title> </head> <body> <form id="form1" runat="server"> <telerik:RadScriptManager ID="RadScriptManager1" runat="server"> </telerik:RadScriptManager> <div style="height:930px"> Scroll down to bottom of the page and right mouse click to see context menu miss placement.... </div> <telerik:RadEditor RenderMode="Classic" ID="redHtmlEditor" runat="server" ContentAreaMode="Div"> <Content> Right-click on image to see custom menu <img style="marign-left: 6px" src="http://demos.telerik.com/aspnet-ajax/Editor/Img/productLogoLight.gif" /> <br/><br/> <p>Right-click here to see the custom Paragraph menu.<br/></p><br/> Right-click on the link to see the default link menu disabled: <a href="/">www.telerik.com</a> </Content> </telerik:RadEditor> </form> </body> </html>
Take the following code and paste it into the editor in HTML mode... Copy Code <html> <head> <title></title> <style type="text/css"> OL LI {LIST-STYLE-TYPE: upper-roman;} OL LI OL LI {LIST-STYLE-TYPE: upper-alpha;} OL LI OL LI OL LI {LIST-STYLE-TYPE: decimal;} </style> </head> <body> <ol> <li>Test... <ol> <li>add sub bullet after this item... </li> <li>it most likely got formatted with an "A" and not a "1"<br /> <ol> <li>It should have been a 1 like this line</li> </ol> </li> </ol> </li> </ol> </body> </html> Flip back to design view and it looks great. Then in design view add a sub bullet to bullet A. It will be formatted with an "A" instead of a "1" that the css style defines. But, if you switch back to HTML view and then back to Design view the formatting is correct. Am I doing something wrong or is this a known issue? Telerik Comment: The Indent button (which fires a browser command) which is used to insert a sub bullet produced the following non XHTML compliant content: <OL> <LI>Test... <OL> <LI>add sub bullet after this item... </LI> <OL> <LI>new sub bullet</LI></OL> <LI>it most likely got formatted with an "A" and not a "1"<BR> <OL> <LI>It should have been a 1 like this line </LI></OL></LI></OL></LI></OL> When you switch to HTML mode, the ConvertToXhtml filter of RadEditor corrects the content and it becomes: <ol> <li>Test... <ol> <li>add sub bullet after this item... <ol> <li>new sub bullet</li> </ol> </li> <li>it most likely got formatted with an "A" and not a "1"<br /> <ol> <li>It should have been a 1 like this line </li> </ol> </li> </ol> </li> </ol> For this reason there is a difference how the bullets are rendered.
Hi guys, In Q3 2014, we will introduce a new FormView-like control for ASP.NET AJAX called DataForm. To see what FormView looks like, visit the MSDN article at http://bit.ly/1pZd0RT. What additional features (not present in FormView) would you like to see in this new control? Best regards, Rumen
If I create a table and add some content to one of the cells, when I click on the content and click either the ordered or unordered list buttons, the <td> tag gets replaced the the <ul> or <ol> tag. I was able to replicate this on all browsers I tried using the demo at http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx
Ticket # 541004
The NuGet packages should not install directories into the project. If these directories are not needed when referencing the dlls traditionally, I can't see why they are needed with the Nuget package. Adding nuget references to ASP.Net AJAX in a non-website/application project results in a silly set of directories. Like, if you want to write a plain assembly that simply uses the Telerik controls in a Server Control. An install.pl file should handle any web.config alteration on install. The
There are two ways to avoid this: - Define a tab order on the entire page so all necessary controls will have their TabIndex attribute set - Remove the attribute from the menu with JS. Here follow a couple of examples. Using RenderMode="Lightweight" also may improve the situation if you do not use the NavigateUrl of the items, so <a> elements are not rendered. - Solution 1: Executes when the entire page has loaded function removeMenuTabIndex() { $telerik.$(".RadMenu[tabindex=0]").removeAttr("tabindex"); Sys.Application.remove_load(removeMenuTabIndex); } Sys.Application.add_load(removeMenuTabIndex); - Solution 2: Add just after the menu so it executes while the DOM is loading, perhaps this can facilitate screen reader compatibility <telerik:RadMenu runat="server" ID="rm1" RenderMode="Lightweight"> <Items> <telerik:RadMenuItem Text="first"></telerik:RadMenuItem> <telerik:RadMenuItem Text="second"></telerik:RadMenuItem> </Items> </telerik:RadMenu> <script> document.getElementById("<%=rm1.ClientID%>").removeAttribute("tabIndex"); </script>
The popular control will be similar to Kendo UI drawer widget: https://demos.telerik.com/kendo-ui/drawer/index.
Client Export Manager Control Export to PDF feature should be improved 1] Exported PDF should be accessible as per Section 508 Compliance. current exported PDF is not readable to accessibility tools like JAWS and Dragon Natural specking tool. 2] Control should have properties to set the width and height of output pdf 3] Multiple page PDF feature should be available. 4] Page Header and Page Footer template should be included to the control.