The focus indicator on the GridSearchBox is broken when using an outline themes like A11Y, Bootstrap etc.

Workaround:

Temporarily override the overflow style on .k-toolbar-items (e.g., overflow: unset;) using custom CSS to restore the focus indicator.

Refreshing the Grid data frequently may cause performance issues.

I want to change the default Grid loading animation to a pulsing loader indicator.

When enabling resizing and reordering for the Telerik Grid, using `MinResizableWidth` to set minimal column width will apply the constraint to the column position rather than the actual movable column. This means applying a min width of 200px to the first column will work as expected until the column is moved to another position. Now the column in question no longer has the min width applied, and the column that has moved into the first position has the 200px min width constraint. 

It appears this is due to the constraint being applied to the `data-col-index` rather than the `data-col-initialization-index`, or something to that effect.

The following example has a 200px min-width constraint applied to the "Name" first column, and no custom min-with applied to "Address" second column. Switching the columns by moving the "Name" after the "Address" will apply the constraint to the "Address" and not the "Name".

https://blazorrepl.telerik.com/QJEAcuPE41L7Uhiw44

Currently using 7.1.0 but looks to be an issue in later versions as shown by the REPL example. Tested in Firefox and Chrome.

The column position is arbitrary and the bug isn't due to the constraint being applied to the 0 column, applying the constrain to all even columns then shuffling would result in the constrain still being applied to all even columns.

Hello

The new adaptive toolbar I think doesn't follow the same style as other components, particularly scrollable tabs.

https://demos.telerik.com/blazor-ui/grid/adaptive

The UI scroll buttons shouldn't just disable, they just be hidden/removed from the UI altogether when they are not active (as it is pretty confusing to the user otherwise) - they should only appear when they need to appear. They also take up real-estate for no value.

Telerik already have the same concept in the UI for the scrollable-tabs seen here;

https://demos.telerik.com/blazor-ui/tabstrip/scrollable-tabs

So I see some inconsistency between the 2 UI's and think they should not appear as does on scrollable tabs.

The Grid component creates an invalid property value in its style for the <table> tag like shown below (some of the contents omitted for brevity). Notice the "width: ;" which should have a value in it.

<table style="height: auto; width: ;"></table>

This can be observed for example by creating a page with the below code and the using the browsers developer tools to examine the elements. Both Grids will have their CSS width property be invalid.

<TelerikGrid Data="@data" AutoGenerateColumns="true">
</TelerikGrid>

<TelerikGrid Width="200px" Data="@data" AutoGenerateColumns="true">
</TelerikGrid>

@code {
    private List<Product> data = new () { 
        new Product() {
            Id = 2,
            Name = "Hello product"
        }    
    };

 public class Product {
        public int Id { get; set; }
        public string Name { get; set; } = string.Empty;
    }
}

When attempting to utilize the FilterMenuButtonsTemplate component, after selecting any of the defined action buttons (i.e., Clear, Filter, etc.), the selection will cause the page to refresh.

Steps:

1. Proceed to the Telerik Blazor documentation page for Filter Menu Buttons Template within the Grid component.
2. View the example for Using custom filter menu buttons.
3. Ensure that this is the first time loading the component as the error will only occur on the example page when first initialized.
4. Select the filter button within the “Price” column header.
5. Press the “Clear” button.

If the GridScrollMode.Virtual is enabled for the Grid, and the NoDataTemplate exceeds the height of the Grid container, a user can infinitely scroll inside the table even when there is no data and the template is displaying.

===ADMIN EDIT===

A possible workaround is to apply "overflow-y: hidden;" when the NoDataTemplate is shown: REPL link.

Since verion 9, the new styling is doing something strange.

The issue is also observable on the Tererik demo site (as well as our published applications) but I have noticed its on webassembly more-so than server apps;

https://demos.telerik.com/blazor-ui/grid/adaptive

If I run the demo site, the new pagination style (where you can type the page you want to navigate to) will flash up for a second, then it will go back to the old style after a second or 2.

Would anyone know why this is happening?

I would like to add some custom actions into the popup window. I know I can implement a custom edit popup with an entirely custom content and actions. However, this requires a lot of custom work to just add one additional action in the popup. Please provide an easier option to add custom actions in the edit window.

After filtering a nullable int column, the SelectAll checkbox in the GridCheckboxColumn stops working.

Reproduction example: https://blazorrepl.telerik.com/mTuyHaYM44sLH2yf05

Please add support for a right-side filter panel (sidebar) that dynamically renders filter controls based on the grid’s visible columns and their editor templates. The panel would allow users to apply multiple filters at once, similar to SharePoint’s column filter experience — in a tall, narrow layout with an “Apply Filters” button.

Why This Matters

While column-level filters are useful, in real-world business apps:

• Users often want to set multiple filters at once without interacting with tiny filter icons.
• They need to see all available filters in one place — especially in cutover task lists, audit views, or reporting grids.
• This UI pattern is familiar from tools like SharePoint, Power BI, and Microsoft Lists.

Please add a built-in way to define a list of predefined filters (filter presets) within the ToolbarTemplate of a grid. This would allow users to quickly select a filter configuration, which is then automatically applied to the grid’s DataSourceRequest.

Why This Is InvaluablE

In enterprise apps with dense, multi-column grids, users often need to:

• Filter to common scenarios (e.g., “My Tasks”, “Due This Week”, “Unassigned Only”).
• Avoid re-entering the same filters repeatedly.
• See role- or context-based presets applied consistently

Currently, implementing this requires custom filter logic, state management, and manual data reloading — even though the concept is straightforward from a user’s perspective.

Please add a ToolbarTitle property to grid components, with an optional ToolbarTitleTooltip or ToolbarTitleAdornmentTemplate. This would allow developers to display a title with optional help text directly in the toolbar — giving users immediate context on the data being displayed.

Why This Is Valuable

In enterprise apps — particularly in areas like dashboards, scheduling, and ERP grids — users are often viewing:

• Similar grids across multiple tabs or modules
• Role-specific data views (e.g., “My Open Tasks”, “Org View Only”)
• Filtered subsets or critical cutover lists

Providing a toolbar-level title with a subtle help icon improves discoverability and reduces confusion — especially when filters or dynamic data shaping is in play.

Please consider altering or providing configuration for how DateTime values are formatted in filter expressions generated by ToDataSourceRequest(). Currently, the format includes full precision (e.g., 2025-04-04T00:00:00.0000000), which causes issues when passed to Entity Framework Core with SQL Server, as SQL Server expects precision up to milliseconds (.fff), not ticks (.fffffff).

Why This Is a Problem

• When passing filter expressions from ToDataSourceRequest() directly into a LINQ-to-EF query, the resulting SQL query fails if the DateTime string has 0000000 (7 digits of precision).
• SQL Server’s datetime and datetime2 types don’t support nanosecond-level precision.
• EF Core attempts to translate it, but fails with SQL conversion errors

Please consider adding new grid-level properties to control visual styling and editing behavior more intuitively:

• HeaderThemeColor
• ShowGridLines
• EditModeDisplay (e.g., None, ValueOnly, All, Auto)
  

These options would provide teams with greater flexibility to align grids with branding, accessibility, and user interaction standards.

Why This Is Valuable

Grids are the centerpiece of most enterprise applications — and users rely on visual consistency and responsive interaction. Today’s grids need to:

• Match branding and accessibility guidelines (dark/light, color accessibility).
• Visually separate data (e.g., grid lines on for financial reports, off for dashboards).
• Clearly communicate edit state (inline, batch, or value-only editing).
  

These settings would empower developers to deliver purpose-built grids without deep CSS overrides or workarounds.

Please consider adding support for an optional header row indicator that can display a conditional icon + themed tooltip, used to show non-field-level validation or status messages — especially during inline or in-cell editing, and ideally in batch edit scenarios.

Why This Is Needed

In enterprise applications — especially those with batch entry workflows, cutover planning, or financial approvals — validation needs often extend beyond just field-level errors. Common use cases include:

• Rule-level messages (e.g., “Only one Primary Owner allowed per group”).
• Cross-row or cross-field issues (e.g., overlapping dates, missing dependencies).
• Batch edit feedback (e.g., conflict indicators before submit).

Currently, there’s no clean way to show column-specific validation or guidance in a visual, inline way that:

• Doesn’t clutter the cell.
• Surfaces at the column level (just like a header).
• Feels native to the grid.

Please consider extending the GridColumn component to include fine-grained header presentation properties, such as:

• HeaderAlignment (e.g., Left, Center, Right)
• WrapHeaderText (bool)
• HeaderTooltip or HeaderAdornmentTemplate
  

These enhancements would dramatically improve clarity and usability in complex data grids.

Why This Is Important

In enterprise-grade applications — like ERP dashboards, financial reporting, or cutover schedules — grids are dense and loaded with meaning. Users rely heavily on headers to interpret the data beneath, especially when:

• Column headers are long or require abbreviations.
• Users need contextual guidance without clutter.
• Alignment improves visual scanning and aesthetics.