The multiline textbox should increase its high while the user types, after the currently available space if fulfilled. Like in Facebook "What's on your mind " textbox  

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. 

Could it be possible to see you developing a chat component to offer chat possibilities on a telerik Ajax Website?

Would be great

Thanks for all you do to simplify our developer life !

Best

Jm Hetsch

Export to PDF  functionality to RadTreeView

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>

Please please please make the Material/Uniform/Bootstrap skins you've made for KendoUI/MVC for ASP.NET AJAX. These skins are so much more modern and clean than the ones available for ASP.NET, which look like they were designed 10 years ago.

The Metro and MetroTouch skins were a step forward for the ASP.NET AJAX library but the Metro is really small and the MetroTouch is really big. Somehow ASP.NET AJAX got the bad Metro skins and the Metro skin for KendoUI/MVC is the perfect size and beautiful. It doesn't need a "Touch" version because the one skin fits both bills.

Just compare the looks of the buttons between the ASP.NET AJAX Metro version and the KendoUI/MVC Metro version:

http://demos.telerik.com/aspnet-ajax/button/examples/overview/defaultcs.aspx?skin=Metro
http://demos.telerik.com/aspnet-ajax/button/examples/overview/defaultcs.aspx?skin=MetroTouch

http://demos.telerik.com/kendo-ui/button/index

Just like your own website is now flat and clean with nice buttons.

Please provide some new modern skins for ASP.NET AJAX as these controls are looking more outdated than ever, which bothers me because you continue to innovate on their functionality.

Make them look as great as they function!

Thanks.

I know that you have developed a RadBook, but only for Silverlight and WPF, which limits the visualization in devices in which it is not possible to install that plug-in or OS, so it would be good to have an HTML5 type control for ASP.NET UI with all the functionality of a Flip Book, and that the control can read a list of images, PDF, Office files, and other.

Thank you.

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.

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.

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.

It would be helpful if the BarCode control could render DataMatrix barcodes

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 

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