I just installed the latest release (Telerik_UI_for_ASP.NET_AJAX_2023_1_314) and the program gives me an error.
This is the error :
Possible Workaround: Telerik.Web.UI.Grid.PositionDragElement = function(element, mouseEvent) { var clientX = $telerik.isTouchDevice ? $telerik.getTouchEventLocation(mouseEvent).x : mouseEvent.clientX; var clientY = $telerik.isTouchDevice ? $telerik.getTouchEventLocation(mouseEvent).y : mouseEvent.clientY; element.style.top = clientY + $telerik.getDocumentElementScrollTop() + 10 + "px"; element.style.left = clientX + $telerik.getDocumentElementScrollLeft() + 10 + "px"; if ($telerik.isOpera || $telerik.isTouchDevice) { element.style.top = parseInt(element.style.top, 10) - document.body.scrollTop + "px"; } };
Under IE, when two tables are placed next to each other, the Table Properties may cause the one to appear nested inside. Currently, this can be workarounded only by assuring that there is some element between them - <br>, <p>, <div>, <span> etc.
System.Exception: 453.6 is not a valid value for Int32.
Based on customer feedback: We just observed the problem that the width where the ribbon completely collapses does not match the width where the ribbon stops being completely collapsed.
Based on customer feedback: fully collapsed groups in the ribbon bar have a smaller height, which leads to a broken layout, when only part of the ribbon groups are fully collapsed.
The R2 2021 update causes all controls in Classic RenderMode to change their layout and size due to different font-size, font-family and line-height.
Fixing this change is planned for the upcoming Service Pack.
In the meantime, you can use the styles in the attachment. Due to the fact that the selectors are the same as the ones in the built-in skin, you need to load them either in the beginning of the <body> or using RadStylesheetManager. If you are using the StylesheetManager, ensure you set a big OrderIndex for the entry:
<telerik:RadStyleSheetManager runat="server" >
<StyleSheets>
<telerik:StyleSheetReference Path="fixes.css" OrderIndex="99999" />
</StyleSheets>
</telerik:RadStyleSheetManager>
Loading the styles in the <head> tag's markup would not work as the Telerik stylesheets are added programmatically at the end of the <head> tag, meaning it will override the preceding files that have the same selector.
The attachment contains a file for each skin and inside it, it has all styles grouped by control. That means you can load only the file for the skin you are using and optionally remove the styles for controls that you are not using. Keep in mind that some more complex controls(e.g. Grid, Editor, DropDownTree, etc.) contain other Telerik controls as child controls, so you would need to keep the styles for the child controls also.
Please excuse us for the inconvenience caused and thank you for your understanding.
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>
If the body tag of the content area of RadEditor has applied font-size with em and line-height attribute in Chrome, the contents of the produced ordered/undoreded lists will be wrapped in a span tag with this formatting. Steps to reproduce: 1) Put the following CSS on the page <style> body { font-size: 0.875em; line-height: 10.4px; } </style> 2) Load this content in RadEditor line1<br /> line2<br /> line3 3) Select the three lines in Design mode and press the InsertUnorederedList button. The produced content in Google Chrome will be <ul> <li><span style="font-size: 0.875em; line-height: 10.4px;">line1</span></li> <li><span style="font-size: 0.875em; line-height: 10.4px;">line2</span></li> <li><span style="font-size: 0.875em; line-height: 10.4px;">line3</span></li> </ul> instead of the expected one: <ul> <li>line1</li> <li>line2</li> <li>line3</li> </ul> Note: This is a WebKit browser behavior which can be reproduced by firing the browser's execCommand method with the InsertOrderedList command identifier: editor.get_document().execCommand("InsertOrderedList");
Problem: With the latest version of Chrome 61 the context menu is not positioning correctly in the treeview. It only happens when the treeview is longer than the window height and there are scrollbars. The EnableScreenBoundaryDetection should be enabled too (it is enabled by default). Reproduction: see this video for a repro https://www.screencast.com/t/Reehai09gMP. The problem does not happen in the Chrome versions prior 61. Details and Resolution: The context menu positioning problem is due to the following breaking change in Chrome 61 (see release notes at https://blog.chromium.org/2017/08/chrome-61-beta-javascript-modules.html): To align with the spec and preserve browser consistency, the scrollingElement is now the documentElement in standards mode. Chrome 61 has changed the behavior of document.scrollingElement to return document.documentElement instead of document.body to match the CSSOM View specification and this broke the positioning of the context menu when the EnableScreenBoundaryDetection is enabled. Solution 1 Place the following override over the RadTreeView declaration: <script> Telerik.Web.UI.RadMenu._getViewPortSize = function () { var viewPortSize = $telerik.getViewPortSize(); // The document scroll is not included in the viewport size // calculation under FF/quirks and Edge. var quirksMode = document.compatMode != "CSS1Compat"; if (($telerik.isFirefox && quirksMode) || Telerik.Web.Browser.edge) { viewPortSize.height += document.body.scrollTop; viewPortSize.width += document.body.scrollLeft; } else if (Telerik.Web.Browser.chrome) { viewPortSize.height += Math.max(document.body.scrollTop, document.scrollingElement.scrollTop); viewPortSize.width += Math.max(document.body.scrollLeft, document.scrollingElement.scrollLeft); } return viewPortSize; }; </script> <telerik:RadTreeView RenderMode="Lightweight" ID="RadTreeView2" runat="server"> <ContextMenus> <telerik:RadTreeViewContextMenu ID="RadTreeViewContextMenu1"runat="server" RenderMode="Lightweight"> <Items> ... Solution 2 Set EnableScreenBoundaryDetection to false. This will disable the screen boundary detection and some parts of the context menu could be rendered beneath the browser borders when there isn't enough space to be rendered on the visible screen. You will have to use the browser scrollbars to show the hidden part of the menu. The issue is scheduled for fixing in R3 2017 SP1, the release date of which is not yet decided. Please use the provided solutions above until the SP1 goes out officially.