Javascript errors are thrown when pie chart with custom skin is loaded. The issue is introduced as of version 2017.1.118.

Code to reproduce:
        <telerik:RadHtmlChart ID="Telerik1" runat="server" Height="250px" Width="250px" EnableEmbeddedSkins="false" Skin="CMS_Black">
            <ChartTitle Text="Financial Aid Status1112">
                <Appearance>
                    <TextStyle Color="Red" FontSize="12" FontFamily="Verdana" Margin="11" Padding="22"></TextStyle>
                </Appearance>
            </ChartTitle>
            <PlotArea>
                <Series>
                    <telerik:PieSeries Name="TypeMemberCount1" NameField="Name" DataFieldY="Value">
                        <LabelsAppearance>
                            <ClientTemplate>
                               #=dataItem.Name#: #=dataItem._Value# (#=dataItem._Percentage#%)
                            </ClientTemplate>
                        </LabelsAppearance>
                    </telerik:PieSeries>
                </Series>
            </PlotArea>
            <Legend>
                <Appearance Position="Right" Visible="true">
                </Appearance>
            </Legend>
        </telerik:RadHtmlChart>


Code bihind:

    protected void Page_Load(object sender, EventArgs e)
    {
        Telerik1.DataSource = GetData();
        Telerik1.DataBind();

    }
    private DataTable GetData()
    {
        DataTable dt = new DataTable("ChargeData");
        
        dt.Columns.Add("Id", Type.GetType("System.Int32"));

        dt.Columns.Add("Name", Type.GetType("System.String"));
        dt.Columns.Add("Value", Type.GetType("System.Int32"));
        dt.Columns.Add("_Value", Type.GetType("System.Int32"));
        dt.Columns.Add("_Percentage", Type.GetType("System.Int32"));

        dt.Rows.Add(1, "Item 1", 10, 34, 10);
        dt.Rows.Add(2, "Item 2", 65, 34, 65);
        dt.Rows.Add(3, "Item 3", 25, 34, 25);
        return dt;
    }


web.config:

    <add key="Telerik.Skin" value="CMS_Black"/>

Ticket 1113172 

This applies to data bound containers like grid template columns. 
For standalone control instances, see how to use the DataSelectedField here: https://docs.telerik.com/devtools/aspnet-ajax/controls/radiobuttonlist/data-binding/server-side-data-binding

When the items in the RadRadioButtonList are declared in the markup, the SelectedValue='<%#Bind("fieldName") %>' approach works as expected, but when the items are fetched from a data source, no item is pre-selected.

This works with the standard asp:RadioButtonList and so it must work with RadRadioButtonList.

Issue explanations and workarounds are available in the attached sample pages and videos below.

In short, the workarounds are:
- use declarative items when possible
- OR, use an <asp:RadioButtonList> and a <telerik:RadFormDecorator> to get uniform appearance of the radio buttons across browsers

I love WebForms and the wealth in the Toolbar. 
I would like to write the payload of the web page in a webform and limit the round tripping with micro webservices, so there is no PostBack. Which means I can do more clientside in a KendoUI style. This would address the criticism of the bloat that comes with ViewState in webforms offering a leaner web page, but with all the advantages of the JavaScript tooling. 
For the most part a lot of this can be done already, would just prefer not to have any limitations in the controls that I can use for this. Just that there is such a driver now with the fashion of AngularJS/SPA applications suggesting that webforms cannot compete here.

Would be nice to have a  single sign on control (eg like http://www.gigya.com/)
What this means is that you can sign on/sign up  with any social login.
Would like this to work well with ajax controls and KendoUI
This sign on is megga important on mobile, but good for conversions on standard laptop or HD websites.

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.

 I am attaching 2 pictures to show what's happening in version 2017.2.621.  In the newer release I have to set the font & size specifically or the text is larger that the box.  It was not this way on previous releases.
Here is the code  I am using to get it to display properly.  However, it did work (as in picture 1) with out the specific font items before.

<telerik:RadComboBox ID="RCB1" runat="server" DataSourceID="SqlDataState" DataTextField="abbreviation" DataValueField="abbreviation" Height="200"  MarkFirstMatch="true" Skin="Office2010Blue" Font-Names="Open Sans" Font-Size=".73em" ForeColor="#64758F" onFocus="this.select()"  Width="150px" EmptyMessage="Choose State...">
</telerik:RadComboBox>

RadGrid's footer has wrong color in Metro skin - black text over black background. The problem is specific for Classic render mode.

I think you may consider the following similar type of control(s) in future release.  I think the following is a good fit for use between a BI solution and standard reports.  It gives regular users some flexibilities to generate ad-hoc queries within an application.

http://demo.easyquerybuilder.com/asp-net-ajax/

The ASP.NET community really seems to be missing a proper property grid.
The only example I could dig out was the outdated implementation on codeplex:
http://propertygrid.codeplex.com/

I'd like to see one such implementation from Telerik.

A new control RadButtonList/Group providing RadioButton/CheckBox List controls utilizing RadButton's Radio and CheckBox ToggleTypes

You're working on a cleaner css3 approach, however sprites are still resource being downloaded...it's be great if the controls we're using on our page had iconography consistent with the site theme *automatically* instead of needing to use a custom skin.

Can you please implement a clean fontawesome enabled skin?  So instead of referencing a sprite and background position you instead would set :before or :after and content="\f002".

This makes the resulting resources much lighter...as there's no sprite (retina ready by default)

...it'd be up to us to have fontawesome loaded on our page.

(Teampulse uses fontawesome, and they have at least 1 radgrid)

http://fortawesome.github.io/Font-Awesome/icons/

Steve

Update from 4 Oct 2017: You can find a sample implementation of a CDN fallback in the following code library project: http://www.telerik.com/support/code-library/cdn-fallback



You can try implementing a fallback similar to the approach from the links below, but check for the window.$telerik variable and initiate a postback to change the web.config or the concrete page's properties to avoid the CDN.

You can find a sample implementation attached below.

- http://www.hanselman.com/blog/CDNsFailButYourScriptsDontHaveToFallbackFromCDNToLocalJQuery.aspx
- http://docs.telerik.com/kendo-ui/intro/installation/cdn-service#refer-kendo-ui-from-cdn-with-local-script-fallbacks

Alternatively, use a custom CDN of your choice that will be better for your case/have better uptime than Amazon CloudFront: http://docs.telerik.com/devtools/aspnet-ajax/controls/scriptmanager/cdn-support/custom-cdn-provider

I have a standard Asp.Net checkbox and a radcheckbox on my webform. But when I configure a sqldatasource and want to add a where clause. Set that to control and want to select the radcheckbox, then only the standard .net checkbox appears in the list. Radcheckbox does not appear. 

Check the attached screenshot for more information.

The DragAndDrop functionality of the RadAsyncUpload under Edge, works properly if DropZones property of the control is set.

Improve RadGrid's grouping, to get more items from the next page, when group in the current gets collapsed.