It becomes hard to see the checked checkboxes because of the selected color it has by default matches the select color of the grid Solution: .RadGrid_BlackMetroTouch .rgSelectedRow .RadCheckBox.RadButton_BlackMetroTouch .rbToggleCheckboxChecked::before, .RadGrid_Bootstrap .rgSelectedRow .RadCheckBox.RadButton_Bootstrap .rbToggleCheckboxChecked::before, .RadGrid_Metro .rgSelectedRow .RadCheckBox.RadButton_Metro .rbToggleCheckboxChecked::before, .RadGrid_MetroTouch .rgSelectedRow .RadCheckBox.RadButton_MetroTouch .rbToggleCheckboxChecked::before { color: white; } .RadGrid_Glow .rgSelectedRow .RadCheckBox.RadButton_Glow .rbToggleCheckboxChecked::before, .RadGrid_Office2010Black .rgSelectedRow .RadCheckBox.RadButton_Office2010Black .rbToggleCheckboxChecked::before, .RadGrid_Telerik .rgSelectedRow .RadCheckBox.RadButton_Telerik .rbToggleCheckboxChecked::before, .RadGrid_WebBlue .rgSelectedRow .RadCheckBox.RadButton_WebBlue .rbToggleCheckboxChecked::before { color: black; } Sample to reproduce the behavior and compare the default colors in other states/cases: <telerik:RadCheckBox runat="server" ID="rcb1"></telerik:RadCheckBox> <br /> <telerik:RadCheckBox runat="server" ID="rcb2" Checked="true"></telerik:RadCheckBox> <telerik:RadSkinManager runat="server" ID="RadSkinManager1" Skin="Bootstrap" ShowChooser="true"> </telerik:RadSkinManager> <telerik:RadFormDecorator ID="RadFormDecorator1" runat="server" DecoratedControls="All" RenderMode="Lightweight" /> <asp:CheckBox ID="Checkbox1" Text="some checkbox" runat="server" /> <telerik:RadGrid ID="RadGrid1" runat="server" OnNeedDataSource="RadGrid1_NeedDataSource" RenderMode="Lightweight"> <MasterTableView> <Columns> <telerik:GridClientSelectColumn></telerik:GridClientSelectColumn> <telerik:GridTemplateColumn HeaderText="rad check box column"> <ItemTemplate> <telerik:RadCheckBox runat="server" ID="RadCheckBox1"></telerik:RadCheckBox> <br /> <telerik:RadCheckBox runat="server" ID="RadCheckBox2" Checked="true"></telerik:RadCheckBox> </ItemTemplate> </telerik:GridTemplateColumn> </Columns> </MasterTableView> <ClientSettings> <Selecting AllowRowSelect="true" /> </ClientSettings> </telerik:RadGrid> And a dummy data source that is not a good data source in general, but it will suffice to get this running so one can observe protected void RadGrid1_NeedDataSource(object sender, GridNeedDataSourceEventArgs e) { (sender as RadGrid).DataSource = "abcdef"; }
When AJAX is enabled for the Grid with the <PagerStyle Mode="Advanced"> or <PagerStyle Mode="NextPrevNumericAndAdvanced"> the Go To Page by Number and Change Page Size Bugtons would not work.
On the other hand, if changing the Page or PageSize by typing and hitting the ENTER key instead of clicking the buttons, the Grid will behave accordingly.
Issue appears in RenderMode="Lightweight"
RadGrid base styles override skins e.g. "border: 1px solid" will override any value for "border-color" that come from non-embed skins.
with client-side databinding when setting sort/filter expressions on button click and then calling the rebind or set_currentPageIndex methods the control makes multiple requests to the web service.
The RadGrid OnDataBindingFailed event does not fire when WCF/WebService returns an IIS 500 Errror page. It DOES, however, fire when IIS returns a proper 500 error JSON response. In my case, the former was happening because my ASP.NET WCF services were incorrectly configured and thus throwing a standard IIS 500 error page. RadGrid should recognize the IIS 500 page as failure and spawned a OnDataBindingFailed event. NOTE: For example, RadScheduler *does* correctly interpret the IIS 500 page as a failure (RE: OnClientRequestFailed).
Since Q3 a change in the client-side binding of the GridTemplateColumn has been introduced. The column no longer automatically populates controls in the ItemTemplate. The change is result of an optimization in code regarding the virtualization and batch editing features of the grid. The new behavior is far more optimized and ensures much faster and robust operation of the control in various cases of client-side binding.
The problem could be replicated in the attached page.
RadGrid VirtualScrolling does not scroll to the bottom when StaticHeaders are enabled. The issue could be observed in the attached project.
Selecting a cell from horizontally scrolled RadGrid with allowed Keyboard Navigationcauses the page to be scrolled to the left in IE 11. video: https://www.screencast.com/t/4NDOq9Qx Comment: If the Batch editing is enabled the cell is selected, but the batch editing is not started. Code to reproduce the issue: <div style="width: 4000px"> <telerik:RadGrid ID="RadGrid1" runat="server" AutoGenerateColumns="true" AllowSorting="true" Skin="Telerik" RenderMode="Lightweight" OnNeedDataSource="RadGrid1_NeedDataSource"> <ClientSettings AllowKeyboardNavigation="true" Scrolling-AllowScroll="true" Scrolling-SaveScrollPosition="true"> <Selecting CellSelectionMode="SingleCell" /> </ClientSettings> <GroupingSettings ShowUnGroupButton="true"></GroupingSettings> <MasterTableView CommandItemDisplay="Top" Frame="Border" ShowFooter="true" AllowPaging="True" AllowCustomPaging="true" ShowGroupFooter="true"> </MasterTableView> </telerik:RadGrid> </div>
Steps to replicate the issue:
Observe: The Grid makes a PostBack and sorts the items, CurrentPage index gets reset back to 1.
Hi,
How can I translate the "clear" button in the mobile Filter Window? I manage to translate everything in that window except the clear button:
King regards
Blas González
We have telerik Radgrid on the pages in our application. When viewed in the windows phone 8 browser the horizontal touch scroll does not work. Moreover the color of the scrollbar is almost invisible. Requests anyone to please suggest how to overcome this issue. we tried providing a skin as "Balck Metro touch" and also tried enabling "embedded skins" but none of this works.
I've used the Telerik Themebuilder to create a css file for the grid and set up my application to use the theme. This is working however, there are many classes that are not being output by the themebuilder. For instance, the buttons on the pager don't work.