Hi,

At first I received the same error in this thread and applied the fixed as suggested. This works ok until I Edit Fields in the Designer. On saving the changes the OLAP settings are placed back into the code. I am then required to delete the code to fix this problem. I am constantly back-and-forth using Edit Fields while building my application.

I don't see this as a Feature Request as suggested in the thread, rather a Bug based on this behavior.

https://www.telerik.com/forums/pivotgrid-problem 

<OlapSettings>
<XmlaConnectionSettings Encoding="utf-8"></XmlaConnectionSettings>
</OlapSettings>

If one opens a dialog/window containing a RadSignature-control and resizes the dialog (e.g. make it twice as large) then the position of the cursor on the canvas does not match the position of the strokes anymore. Painting in the top-left corner is sort of okay/close, but the further one moves the cursor towards the bottom-right, the bigger the offset will be.

A possible workaround would be tweaking the ItemRequestTimeout property of the ComboBox

<telerik:RadComboBox ItemRequestTimeout="380" runat="server" ... >
        ...
 </telerik:RadComboBox>

It seems the element somehow considmes the scrolling/touch action and the grid does not scroll unless you hit the gap where the custom element does not reach.

A workaround is to enforce overflow: auto to the scrollable element of the grid. A sample is attached below.

        div.rgDataDiv {
            overflow: auto !important;
        }

If the same text is typed into the input field as the one set for EmptyMessage and page is submitted, validator evaluates True.

Current workaround is to subscribe the RadComboBox to OnClientFocus client event handler, and clear the EmptyMessage manually, thus preventing the EmptyMessage text to be sent to server.

<telerik:RadComboBox ... OnClientFocus="comboFocus">

<script type="text/javascript">
	function comboFocus(sender, args) {
		sender.set_emptyMessage("");
	}
</script>

Repro: 

<telerik:RadStyleSheetManager runat="server"></telerik:RadStyleSheetManager>

<asp:UpdatePanel runat="server">
    <ContentTemplate>
        <asp:Button Text="Postback" OnClick="Unnamed_Click" runat="server" />
        <telerik:RadButton runat="server" Visible="false" ID="RadButton1" Text="Telerik button" AutoPostBack="true" />
    </ContentTemplate>
</asp:UpdatePanel>

protected void Unnamed_Click(object sender, EventArgs e)
{
    RadButton1.Visible = true;
}

<add key="Telerik.ScriptManager.EnableHandlerEncryption" value="true" />

Workaround:

Temporarily set EnableHandlerEncryption to false or do not use a StyleSheetManager

<add key="Telerik.ScriptManager.EnableHandlerEncryption" value="false" />

The color picker doesn't looks good when zooming in the browser.

Try zooming to 120% and run your demo:

http://demos.telerik.com/aspnet-ajax/colorpicker/examples/overview/defaultcs.aspx

You need to reload the page after zooming!

The Web colors wraps, and the HSB/HSV tabs also wraps a lot!

Also see this thread:
http://www.telerik.com/forums/looks-really-bad-when-zooming

The FooterAggregateFormatString functionality of the Grid does not affect the Aggregates values format in a client-bound Grid.

Code to reproduce:
            <telerik:RadGrid RenderMode="Lightweight" ID="RadGrid1" runat="server" ClientDataSourceID="RadClientDataSource1" AllowPaging="true" AllowSorting="true" AllowFilteringByColumn="true" ShowFooter="true">
                <MasterTableView ClientDataKeyNames="CustomerID" EditMode="Batch" CommandItemDisplay="Top" BatchEditingSettings-HighlightDeletedRows="true">
                    <Columns>
                        <telerik:GridBoundColumn DataField="CustomerID" HeaderText="Customer ID"  Aggregate="Count" FooterAggregateFormatString="No currency sign here: {0:C}">
                        </telerik:GridBoundColumn>
                        <telerik:GridBoundColumn DataField="CompanyName" HeaderText="Company Name" ColumnEditorID="GridTextBoxEditor">
                        </telerik:GridBoundColumn>
                        <telerik:GridBoundColumn DataField="ContactName" HeaderText="Contact Name" ColumnEditorID="GridTextBoxEditor">
                        </telerik:GridBoundColumn>
                        <telerik:GridBoundColumn DataField="ContactTitle" HeaderText="Contact Title" ColumnEditorID="GridTextBoxEditor">
                        </telerik:GridBoundColumn>
                        <telerik:GridClientDeleteColumn HeaderText="Delete">
                            <HeaderStyle Width="70px" />
                        </telerik:GridClientDeleteColumn>
                    </Columns>
                </MasterTableView>
                <ClientSettings>
                    <ClientEvents OnUserAction="UserAction" />
                </ClientSettings>
            </telerik:RadGrid>

RadDropDownList has an attribute "DropdownWidth" that controls the width of the LIST when it drops down.   

If you set the width to a specific number of pixels (say 200px) then there is no issue.   But if you set it to "100%"  then I would have expected it to be 100% of the owner controls width.   But this is not the case, and it becomes very evident when the RadDropDownList is used with a template column of a RadGrid.  

In a RadGrid template column, this setting causes the LIST width to expand all the way to the right edge of the screen.   This seems to me to be a bug, as it makes no sense to behave this way.   You can see this behavior in the screenshot I have attached.  

It becomes more evident that this was not the intended functionality (and must be a bug) when you substitute the control with a RadComboBox, having exactly the same attributes.  This will use the combo's default settings and show a dropdown list.  With the RadCombBox the LIST does not expand to the far right of the screen, it behaves as expected, having 100% of the combobox width.  

I would expect both controls to work identically with their LISTS when setting the "DropdownWidth" attribute to "100%".

Due to recent changes to the keyboard accessibility of the RadMenu (i.e. it is now only accessible using the arrow keys instead of moving around using tabs), mega menus are no longer keyboard accessible.

We have designed a mega menu using a telerik RadSiteMap embedded in a RadMenu control, as suggested in the Telerik Demo site: http://demos.telerik.com/aspnet-ajax/menu/examples/megadropdown/defaultcs.aspx

However, this is no longer accessible. Previously, you could open the dropdown by pressing the down button, then move around in the dropdown using tab. Now, however, pressing tab just closes the dropdown.

We need the menu to be accessible in one way or another.