Instead of pages like this, which exist for every control and aren't very helpful:
http://www.telerik.com/help/aspnet-ajax/scheduler-appearance-skins.html

I think the skins page should actually render the control and allow developers/designers to select a skin from a drop down to properly demonstrate how the control appears in that skin. 

The logic behind this is somewhat similar to the property explorer pages. As with the property explorer pages, the RenderMode should also be selectable from the proposed skin page because it affects the way the skin is rendered. 

Without this feature I find myself starting a test page, typing in a skin name, save changes, load page, new skin name... repeat, repeat. Please add this feature to make this process a whole lot easier.

All dialog windows triggered from SmartTags (ODataDataSource configuration wizard per say) are distorted and mostly or completely unusable in HDPI environments (150% scaling).

In particular we can observe few main points:

* Window too big to fit on the screen
* Text too big to fit in designated area
* Layout completely distorted
* Icons not showing correctly

Has telerik ever thought of writing an SSO class or control that would allow someone to add the functionality to sign on to their website using sso and SAML 2.0 for secure login?

None of the demos are displaying correctly.  Take a look at: http://demos.telerik.com/aspnet-ajax/orgchart/examples/overview/defaultcs.aspx.  It appears that the stylesheet might be missing.

The markup intellisense doesn't work in VS 2008 with Q1 2014.

There is an on your live demo

http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/rows/detailitemtemplate/defaultcs.aspx

The current behavior of the table insertion works by adding the cursor outside the table. This behavior causes inconsistent issues (e.g. In IE the cursor appears in the last TD, but the typed text is after the table) and faulty user experience.

In desktop rich text editors (e.g. MS Word), when a table is inserted the first table cell is selected and this is the users' expected behavior.

You can test the modified command by following this example:

<telerik:RadEditor runat="server" ID="RadEditor1" OnClientPasteHtml="OnClientPasteHtml">
</telerik:RadEditor>

<script type="text/javascript">
    var identifierID = "RadEditor_AfterTable";

    function OnClientPasteHtml(editor, args) {
        var commandName = args.get_commandName();

        if (commandName === "InsertTable" || commandName === "TableWizard" ) {
            var currValue = args.get_value();
            currValue = currValue.replace(/<\/table>/gi, "</table><div id=" + identifierID + ">&#x200B;</div>");
            //currValue = currValue + "<div id=" + identifierID + ">&#x200B;</div>";
            
            args.set_value(currValue);
            setTimeout(function () {
                selectFirstTD(editor)
            }, 0);
        }
    }

    function selectFirstTD(editor) {
        var $ = $telerik.$;
        var contBody = editor.get_contentArea();
        var identifier = $(contBody).find("#" + identifierID);
        var table = identifier.prev();
        var elmToSelect = table.find("th")[0] || table.find("td")[0];

        if (elmToSelect.childNodes && !$telerik.isIE) {
            elmToSelect = elmToSelect.childNodes[0].nodeName === "#text" && elmToSelect.childNodes[0];
        }

        var hasNextElement = identifier.next()[0];
        
        while (hasNextElement && $(hasNextElement).is("style")) {
            hasNextElement = $(hasNextElement).next()[0];
        }
        
        editor.selectElement(elmToSelect);

        if (!hasNextElement) {
            table.after("<br/>");
        }

        identifier.remove();
    }
</script>

Allow persisting of column widths
Allow persisting of what columns are displayed when a user selects them. (via EnableHeaderContextMenu) 

Thanks