The popular control will be similar to Kendo UI drawer widget: https://demos.telerik.com/kendo-ui/drawer/index.

You can give your vote if you want to have a switch button in the Telerik UI for ASP.NET AJAX suite. See the attachment for more information.

MetroTouch "DragHandleDown.png" resource appears to be missing from 2015.1.225.40 version of Telerik.Web.UI.Skins.dll.

Got the following in my event logs:

Event message: An error occurred processing a web or script resource request. The requested resource 'pTelerik.Web.UI.Skins|Telerik.Web.UI.Skins.MetroTouch.Slider.DragHandleDown.png' does not exist or there was a problem loading it. 

Checked in the .dll for any reference to said resource. Found instances of "DragHandleDown.gif" for other skins (Black, Office2010Black, etc.) but nothing for MetroTouch.

Putting an SVG element in the editor content will throw an exception under IE.

Workaround (Make sure to add the script element with the fix right after the RadEditor declaration):

<telerik:RadEditor runat="server" ID="RadEditor1">
    <Content>
        <svg height="100" width="100">
          <circle cx="50" cy="50" r="40" stroke="black" stroke-width="3" fill="red" />
        </svg>
    </Content>
</telerik:RadEditor>

<script type="text/javascript">
    var oldMarkListItems = Telerik.Web.UI.Editor.WordListConverter.prototype.markListItems;

    Telerik.Web.UI.Editor.WordListConverter.prototype.markListItems = function(htmlText)
    {
        if (!htmlText)
            return htmlText;

        return oldMarkListItems.call(this, htmlText);
    };
 </script>

The current filtering of the grid wastes a lot of screen space If for example I want to filter a column to have values between X and Y. the column width especially on date column will need much more space for the filter than for the data actually shown.
On the current filter of the grid the user cannot filter on columns he is not seeing

My proposed implementation is simple but should work:
The control will be similar to the Menu control and will render just like in the video two lines of filters: static and optional. It will have a filters collection. Each filter will have these basic properties:
1. AlwaysDisplay - if true the filter is always displayed and cannot be removed.
2. Displayed - if true the filter is displayed. if not it is displayed on the static list last button as an optional filter
3 Type - Can be single value, Multiple values (checkbox list), Single date, Date range, Textbox (for free text search in all of the columns). obviously with needed properties for values etc.
4. Text - the name of the filter
5. The actual property to filter by
* pressing each filter will display a popup similar to the Custom menu sample with the needed filter type. selecting the value will update the filter text shown.
* the static filter list will show a button for optional filters which can be shown on the line below. filters on the optional line can be removed with a click on a X button
* all UI changes (adding/removing filters) should be on client side so the control will be very responsive.
* over time filters can evolve so that the date range filter popup for example can show except for the obvious option of from X to Y other options for the user (e.g. last X weeks/days/years) and other ideas shown on the video I sent you
The result the control produces is a LINQ expression which can be applied to the data source in a LINQ Where statement (my usage case) or other values (SQL where statement) that can be used by other users.


The proposed new control has the following advantages:
1. It can be positioned anywhere 
2. It can show fixed filters and optional filters
3. It can filter based on columns not visible on the grid
4. Optional filters can be removed quickly with the X button which provides faster change of filters for the user.

The end result of this filter is a much easier UX for filtering data. it uses far less screen space and is modular enough for future columns and to filter data sources for things other than the grid

Issue: Export to Excel Functionality developed using Telerik Grid doesnt work in IE 11 browser.

In one my applications the Export to excel Functionality is not working in IE 11. When the export to Excel Functionality is button is clicked , it gives a blank excel workbook without any data in IE 11 browser where as this works fine in IE 8 browser. I have attached the document with screenshots.

Code snippets:

  //Start- script to enable controls after export to excel
    if (typeof (_spBodyOnLoadFunctionNames) != 'undefined' && _spBodyOnLoadFunctionNames != null) {
        _spBodyOnLoadFunctionNames.push("supressSubmitWraper");
    }
    function supressSubmitWraper() {
        _spSuppressFormOnSubmitWrapper = true;
    }
    //End- script to enable controls after export to excel

    function click_handlerConsumptionReport() {
        theForm.__EVENTTARGET.value = '__Page';
        theForm.__EVENTARGUMENT.value = 'Export';
        theForm.submit();
        theForm.__EVENTARGUMENT.value = '';
    }

The layout of these dialogs in SharePoint's Editor is broken to the point where the user would be unable to use them. 

If you like the Google Material design, you can vote for this item. This will help us prioritize the item and decide when to implement a Material skin for the Telerik UI for ASP.NET AJAX controls.

RadImageGallery fullscreen mode overrides viewport meta tag set on page.
If the user sets the following meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1, maximum-scale=1.0, user-scalable=no, height=device-height" />

initially the page is not scalable. When the Gallery enters fullscreen mode, the page is zoomed out.
And when you exit fullscreen, the page stays zoomed out, the gallery proportions are changed and fonts are smaller.

as you know we purchased DevCraft Complete and it is really hard to download everything file by file.

I really wish if you have one magic button which when i click it it will download the entire files for all DevCraft Complete updates for ajax, kendu, reporting etc

Removing the vertical scrolling of the source code container will make the code much easier for reading, both for desktop and mobile devices.