You can't compress something that is already compressed. Any further compression applied will increase size because of adding headers and hashes and the data will stay the same.
The RadTextBox are placed inside a asp gridview. When an item from the combo box in the page is selected. The server side logic hide one of the columns of the gridview using such approach: grdExamples.Columns.Visible = false; This, however, keeps the controls inside the vary same GridView. So during Ajax their ScriptDescriptrs got registered in the ScriptManager. When the result $create execute client side, the JS error is thrown. It can not be fixed in general, because we can not cover scenarios where the control is: 1. Visible 2. In the control collection. (have .Page!=null) 3. All it's parents are visible. 4. Does not render, because it's parent control ( the gridview) decides not to render some of it's childs. When all of 1,2,3,4 are true, the control will describe, but not visible in the output HTML resulting in error. It will happen in all controls (not only RadTextBox), when you are using the RadAjaxManager. Since the manager registers the ScriptDescriptors manually per control, before the Render of the page, therefore it can't know if the control is "Really Visible". This is limitation of the manager, that can not be changed without breaking fundamentals of how it works.
RadNumericTextBox with SelectionOnFocus="SelectAll" doesn't work in Chrome. Expected behavior: when textbox focuses, the text in the input should all be selected. Actual behavior: the cursor jumps to the end of the text in the input
Due to a bug in the WebKit-based browsers this issue could not be fixed since it will introduce another bugs in those browsers.
Can not open database created with the latest sql using 2008, same issue here.
The Response.Redirect is not supposed to work during through Ajax call.
The issue is caused by a bug in the KB3057839 windows update. The bug has been reported to Microsoft and can be tracked at the following link: https://connect.microsoft.com/VisualStudio/feedback/details/1475291 Currently the only workaround is to revert the KB3057839 update on the production server.