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.
Ticket # 541004
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>
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
The popular control will be similar to Kendo UI drawer widget: https://demos.telerik.com/kendo-ui/drawer/index.
It will be nice to have a countDown control with all the client/server events and the suite skins, which will enable the developer to show a visitor with a timer to complete a task (like finsih a purchase with a guranteed price for few minutes) and call a web service when the timer got to zero, and show a message to the client (with integrated Notificatoin object) about the price (changed or staed the same etc.) and let the developer decide if he wants to start the timer again or not. Thanks, ilan.
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>
Add ability to define Telerik specific ConfigSectionHandler for their settings like others (e.g.,log4Net) do. This makes configuring environments much easier. All I need to do is point to *.Dev.config, *.Stage.config and my application is ready for the new environment. For example, the following settings: <configuration> <configSections> <section name="myConfigSection" type="CurrentApp.ConfigurationSectionHandler, Current" /> </configSections> <myConfigSettings configSource="App_Data\Configs\MyConfigSection.config" /> <appSettings> <add key="Environment" value="Local.Local"/> ... <add key="Telerik.ScriptManager.TelerikCdn" value="Enabled"/> <add key="Telerik.ScriptManager.TelerikCdn.BaseSecureUrl" value="https://yourSite.com/cdn/TelerikScripts" /> <add key="Telerik.ScriptManager.TelerikCdn.BaseUrl" value="http://yourSite.com/cdn/TelerikScripts" /> <add key="Telerik.ScriptManager.TelerikCdn.CombinedScript" value="Enabled" /> <add key="Telerik.Skin" value="Bootstrap" /> <add key="Telerik.StyleSheetManager.TelerikCdn" value="Enabled"/> <add key="Telerik.StyleSheetManager.TelerikCdn.BaseSecureUrl" value="https://yourSite.com/cdn/TelerikSkins" /> <add key="Telerik.StyleSheetManager.TelerikCdn.BaseUrl" value="http://yourSite.com/cdn/TelerikSkins" /> <add key="Telerik.StyleSheetManager.TelerikCdn.CombinedResource" value="Disabled" /> <add key="Telerik.Web.UI.StyleSheetFolders" value="~/Content/; ~/" /> ... <appSettings> <configuration> can be changed to: <configuration> <configSections> <section name="telerikSettings" type="Telerik.ConfigurationSectionHandler, Telerik" /> </configSections> <appSettings configSource="App_Data\Configs\Local.config" /> <telerikSettings> <!-- This section does not exist and the keys are currently inside the local.config file --> <add key="Telerik.ScriptManager.TelerikCdn" value="Enabled"/> <add key="Telerik.ScriptManager.TelerikCdn.BaseSecureUrl" value="https://yourSite.com/cdn/TelerikScripts" /> <add key="Telerik.ScriptManager.TelerikCdn.BaseUrl" value="http://yourSite.com/cdn/TelerikScripts" /> <add key="Telerik.ScriptManager.TelerikCdn.CombinedScript" value="Enabled" /> <add key="Telerik.Skin" value="Bootstrap" /> <add key="Telerik.StyleSheetManager.TelerikCdn" value="Enabled"/> <add key="Telerik.StyleSheetManager.TelerikCdn.BaseSecureUrl" value="https://yourSite.com/cdn/TelerikSkins" /> <add key="Telerik.StyleSheetManager.TelerikCdn.BaseUrl" value="http://yourSite.com/cdn/TelerikSkins" /> <add key="Telerik.StyleSheetManager.TelerikCdn.CombinedResource" value="Disabled" /> <add key="Telerik.Web.UI.StyleSheetFolders" value="~/Content/; ~/" /> </telerikSettings> ... </configuration> or directly point to external configuration file: <configuration> <configSections> <section name="telerikSettings" type="Telerik.ConfigurationSectionHandler, Telerik" /> </configSections> <appSettings configSource="App_Data\Configs\Local.config" /> <telerikSettings configSource="App_Data\Configs\Telerik.config" /> ... </configuration>
As part of the Fall Creators update, Microsoft are releasing SDKs for their Fluent design system for UWP app design. It would be great if Telerik could expand their skins to include controls designed to mimic the look and feel of the Fluent design including, where possible, Acrylic, Parallax, and Reveal. I believe that light or dark themes will be standard on the Fluent design, but users will be able to incorporate the their accent colour preference. So, at the least it would be great to have fluent light, and fluent dark skins with an easy method of similarly changing the accent colour. Of course, not all of the functionality of UWP will be possible for ASP.NET AJAX, but since Fluent is likely to become the new standard for UWP app design, I believe that users will come to expect similar skins in their web-apps. See https://docs.microsoft.com/en-us/windows/uwp/layout/design-and-ui-intro for more info.