A workaround is to add the settings in the markup, for example:

<telerik:RadPersistenceManager runat="server" ID="RadPersistenceManager1">
	<PersistenceSettings>
		<telerik:PersistenceSetting ControlID="RadTileList1" />
	</PersistenceSettings>
</telerik:RadPersistenceManager>
<telerik:RadTileList runat="server" ID="RadTileList1">
</telerik:RadTileList>

The disabled items in RadMenu have wrong styles applied and look like enabled.

WORKAROUND:

        .RadMenu .rmGroup a.rmLink.rmDisabled,
        .RadMenu .rmGroup a.rmLink.rmDisabled:hover {
            color: #677277;
        }
        .RadMenu .rmGroup a.rmLink.rmDisabled.rmFocused {
            box-shadow: inset 0 0 3px 1px;
        }




Steps to reproduce:

        <telerik:RadMenu ID="RadMenu1" runat="server" RenderMode="Classic" Skin="Glow">
            <Items>
                <telerik:RadMenuItem Text="Home" NavigateUrl="Default.aspx">
                    <Items>
                        <telerik:RadMenuItem Text="Disabled" Enabled="false"></telerik:RadMenuItem>
                        <telerik:RadMenuItem Text="Home row2"></telerik:RadMenuItem>
                        <telerik:RadMenuItem Text="Home row3"></telerik:RadMenuItem>
                        <telerik:RadMenuItem Text="Home row4"></telerik:RadMenuItem>
                    </Items>
                </telerik:RadMenuItem>
                <telerik:RadMenuItem IsSeparator="true" />
                <telerik:RadMenuItem Text="Grid Page" NavigateUrl="Grid.aspx" />
                <telerik:RadMenuItem IsSeparator="true" />
                <telerik:RadMenuItem Text="About" Enabled="false" />
                <telerik:RadMenuItem IsSeparator="true" />
            </Items>
        </telerik:RadMenu>

When zoom is applied in IE browser and button coordinates are not an integer RadImageButton tries to convert them to an integer on the server on postback and fails.

Workaround:

			<telerik:RadImageButton runat="server" ID="rib1" Width="50" Height="50" OnClick="rib1_Click" Image-Url="~/images/myImage.png"></telerik:RadImageButton>
			<script>
				Telerik.Web.UI.Button.ImageCoordsFunctionality.prototype._calculateCoords = function (e) {
					var container = this._ui.element;
					var pos = $telerik.getLocation(container);
					var scroll = $telerik.getScrollOffset(container, true);

					return new Telerik.Web.UI.Point(parseInt(e.clientX + scroll.x - pos.x), parseInt(e.clientY - pos.y + scroll.y));
				}
			</script>

Steps to reproduce:
1. Open the demo page http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx
2. Switch to the 'HTML' mode of the RTE and replace all existing HTML content with the following HTML snippet:
<div>text</div>

3. Switch to the 'Design' mode of the RTE and click once on the 'text' word;
4. Switch keyboard language to Japanese and select 'Hiragana' input type. Place focus on the 'text';
5. Type the 'a' and 'e' characters;

Expected result:
The 'あえ' characters are typed.

Actual result:
Just 'え' character is typed. The 'あ' character is replaced by the 'え'. 

Note:
The first character disappears.
You may need to try several times to reproduce the issue.
The issue is reproducible in Chrome (Version 54.0.2840.99 m).
The issue is not reproducible in Firefox and IE11.

Screencast reproduction: http://screencast.com/t/Lj6plU0di99



Workaround:

<telerik:RadEditor ID="RadEditor1" runat="server">
<Content><p>test</p></Content>
</telerik:RadEditor>

<script>
var editorPrototype = Telerik.Web.UI.RadEditor.prototype;
var onKeyDown = editorPrototype._onKeyDown;
editorPrototype._onKeyDown = function (e) {
if (e.composed) {
   this._pendingTextTypeCmd = {};
}
onKeyDown.call(this, e);
if (e.composed) {
   delete this._pendingTextTypeCmd;
}
};
</script>

RadCombobox with allowed custom text is transperant in Silk in Classic Render mode.

Video: https://www.screencast.com/t/tgubeklglq


Code to reproduce:
        <div style="width: 300px; background-color: red">
            <h2>Allow custom text</h2>
            <telerik:RadComboBox RenderMode="Classic" ID="RadComboBox1" runat="server" Width="100%" AllowCustomText="true" Skin="Silk">
                <Items>
                    <telerik:RadComboBoxItem Text="RadComboBoxItem1" />
                    <telerik:RadComboBoxItem Text="RadComboBoxItem2" />
                    <telerik:RadComboBoxItem Text="RadComboBoxItem3" />
                </Items>
            </telerik:RadComboBox>
        </div>

Additional white border added to the RadRibbonbar buttons in Windows7 skin. The problem is reproducible in Classic rendering.

Steps to reproduce:
1. Open http://demos.telerik.com/aspnet-ajax/ribbonbar/examples/rendermodes/defaultcs.aspx?skin=Windows7

2. Switch to Classic rendering.

Result: All buttons have white border.

The issue can be workarounded by calling preventDefault of the mousedown event when ComboBox item is clicked:
<telerik:RadScriptManager runat="server" />
<script>
	var onDocumentClick = Telerik.Web.UI.RadComboBox.prototype._onDocumentClick;
	Telerik.Web.UI.RadComboBox.prototype._onDocumentClick = function (e) {
		if (!e) e = event;

		var target = e.target || e.srcElement;

		while (target.nodeType !== 9) {
			if (!target.parentNode || target == this.get_element() || target == this.get_dropDownElement()) {
				e.preventDefault();
				return;
			}

			target = target.parentNode;
		}
		onDocumentClick.call(this, e);
	};
</script>

<telerik:RadComboBox ID="RadComboBox1" runat="server" RenderMode="Lightweight" OnClientBlur="OnClientBlur"
	CheckBoxes="true">
	<Items>
		<telerik:RadComboBoxItem Text="Item1" Value="1" />
		<telerik:RadComboBoxItem Text="Item2" Value="2" />
		<telerik:RadComboBoxItem Text="Item3" Value="3" />
		<telerik:RadComboBoxItem Text="Item4" Value="4" />
	</Items>
</telerik:RadComboBox>

<script>
	function OnClientBlur(sender, args) {
		console.log("Blur event");
	}
</script>

When the control is modal it should create a second iframe behind the modal background like it creates one behind the popup itself. This will allow the modal background to stay above heavy-weight objects in IE as well.

The sprite images for the RadButton are moved from the "Button" folder to the "Common" folder of the skins, but the Visual Style Builder searches the images in the Button folder.

The workaround is to extract the archive generated by the Visual Style Builder, move the sprites from the Common folder to the Button folder, archive the files again and import them in the Visual Style Builder. This allows you to edit them in the tool and after that you can download the skin and move the sprites back to the Common folder.

The Toolbar delete button is enabled only if the selected item's parent folder can be deleted, even if the file itself has delete permission.

Steps to reproduce:
1. Openthe following demo, the delete permissions ase given to the root "images" folder (DeletePaths="~/FileExplorer/Examples/Overview/images")
http://demos.telerik.com/aspnet-ajax/fileexplorer/examples/overview/defaultcs.aspx
2. Open the root folder from the tree (images)
3. Select an item from the grid

Actual: The Delete button is not enabled
Expected: The delete button is enabled, as the images folder is granted with delete permissions


WORKAROUND:
        <telerik:RadFileExplorer ID="RadFileExplorer1" runat="server" EnableCopy="True" EnableOpenFile="True" OnClientLoad="explorerLoad"
            Height="500px" Skin="Default" Configuration-MaxUploadFileSize="900000000">
            <Configuration  ViewPaths="~/Images_2" DeletePaths="~/Images_2" UploadPaths="~/Images_2" />
        </telerik:RadFileExplorer>
        <script>
            function explorerLoad(fileExplorer, args) {
                fileExplorer._fileList.add_itemSelect(Function.createDelegate(fileExplorer, function (fileList, args) {
                    fileExplorer._updateToolbar(null, null, args.get_item().get_permissions());
                    fileExplorer.raise_itemSelected(args.get_item());
                }));
            }
</script>

RadCheckBox is not firing the event for CheckedChanged the first time it is checked.

If you simply replace the RadCheckBox with a standard asp CheckBox all works as it should and the event is fired with the first click.