The ability to choose which options to appear in the ContextMenu.

=====

TELERIK EDIT: In the meantime, here is how to hide context menu items with CSS:

    /* Hide the Rename item in the FileManager context menu */
    .k-context-menu:has(.k-svg-i-download) .k-menu-item:nth-of-type(1) {
        display: none;
    }

    /* Hide the Delete item in the FileManager context menu */
    .k-context-menu:has(.k-svg-i-download) .k-menu-item:nth-of-type(3) {
        display: none;
    }

Here is a complete example: https://blazorrepl.telerik.com/cpPkuBEq408A36p010

Hi,

The ask is for a feature request to take the already wonderfully done globally applied filter features down to a per column basis without the overhead and burden of resorting to the custom FilterMenuTemplate approach.

The current way of doing business creates much overhead in code particularly when several columns are involved.

Something like:

<TelerikGrid Data="@MyData"
FilterMode="@GridFilterMode.PerColumn"

<GridColumns>
<GridColumn Field="MyField01" FilterMode="@GridFilterColumnMode.FilterRow" />

<GridColumn Field="MyField02" FilterMode="@GridFilterColumnMode.FilterMenu" />

<GridColumn Field="MyField03" Filterable="false"/>

etc..

</GridColumns>

</TelerikGrid>

Thanks!

Ron

Hello,

I need to be able to set the colors of x-axis category labels conditionally. My current use case for this is that I'm displaying dates and need weekends and holidays to be their own colors. As far as I'm aware this cannot be accomplished in any way currently:

• ChartCategoryAxisLabels Color parameter cannot be conditional and applies to all labels
• ChartCategoryAxisLabels Template parameter must return plain text and cannot render styling or HTML
• The labels are drawn via canvas and therefore cannot be styled externally

The two solutions I could suggest are as follows:

1. Make the ChartCategoryAxisLabels Color parameter able to be Kendo UI parsed like the Template Parameter
2. In addition to the ChartCategoryAxis Categories parameter, support providing categories as render fragment children, with each having its own Color parameter

Thanks,
Robert

Goal

Our application needs to allow end users to dynamically customize the Telerik Blazor DockManager at runtime by:

• Adding new panels
• Removing existing panels
• Rearranging and resizing panels

These changes should be fully user-driven and persisted so that:

• The layout is restored when the user returns
• The layout is consistent across browsers and devices

In short, we want the DockManager to behave as a customizable dashboard whose state can be reliably stored and reloaded from our database.

Problem

The current Telerik Blazor DockManager implementation requires panels to be declared in Razor markup (markup driven) and managed through an external data source.

This creates several challenges:

• The component state (DockState) is tightly coupled to the initial panel definitions.
• Dynamically adding or removing panels from the data source conflicts with the internal DockState.
• To synchronize changes, we must manually manipulate the DockState object using custom code.
• This manipulation relies on internal behavior that is not formally supported and may break in future Telerik releases.

As a result, implementing a truly dynamic and persistent DockManager layout requires complex workarounds that are fragile and difficult to maintain.

Feature Request

We propose enhancing the DockManager with first-class support for dynamic panel synchronization by introducing:

Two coordinated parameters:

• Data – the collection of panels
• DockState – the persisted layout information

Expected behavior:

• If the Data collection contains a panel that is not present in the DockState, the component should automatically:
  • Add the new panel to the layout
  • Place it at the end of the current structure (bottom or right, depending on layout)
  • Update the DockState accordingly
• If the DockState contains a panel that is no longer present in the Data collection, the component should automatically:
  • Remove that panel from the layout
  • Update the DockState accordingly

This would allow developers to treat the DockManager as a true data-driven component, similar to other Telerik Blazor controls, without needing to manually modify internal state structures.

If LoadGroupsOnDemand="false", I am able to programmatically expand the groups through the state. However, this is not possible when loading group data on demand.

Please allow programmatically expanding the groups when LoadGroupsOnDemand="true". This should go together with an event (OnStateChanged?) that will fire when LOD groups are expanded or collapsed.

Currently, on mobile devices (where is no hover), to open the child menu you need to click/tap the parent and the only way close it afterwards is if you click away. This is not very convenient for mobile usage. I want to be able to close the child menu on click/tap of the parent as well.

Currently, a TextField value of empty string will produce a blank item in the dropdown.

On the other hand, a null TextField value will produce the fully qualified class name.

Here are possible workarounds: https://blazorrepl.telerik.com/myOlFpFb1465jW8E07

Draft feature request (copy/paste)

Title: Add per-column value converters (WPF-style) to Telerik Blazor Grid columns

Product: UI for Blazor → Grid
Type: Feature Request

Description:
In Telerik UI for WPF, grid column definitions can reference a converter by name (e.g., IValueConverter) to transform values for display without writing a custom cell template for each column.

In Telerik UI for Blazor Grid, templates are currently the primary way to change how values render in a column (which works, but becomes repetitive across many columns/grids).

Request:
Add a column-level conversion API that allows specifying a converter/formatter function for display (and optionally editing). Example concepts:

• Converter="nameof(MyConverters.StatusToText)"

• or DisplayConverter="(item) => …" / ValueFormatter="Func<TItem, object, string>"

• optionally ConvertBack-like support for editing scenarios (or separate EditConverter)

Why this is needed:

• Reduces repeated <Template> markup for simple formatting/transformations

• Centralizes formatting/conversion logic in reusable code

• Improves maintainability and consistency across grids

• Eases migration for teams coming from Telerik WPF where converters are a common pattern

Use cases:

• Enum/int → user-friendly text

• Boolean → “Yes/No”, icons, badges

• Null/empty → placeholder text

• Code → display name (via lookup)

• Domain-specific formatting shared across many grids

Workarounds today:

• Column <Template> or computed properties (both valid, but not as concise/reusable for large grids)

• Extracting RenderFragments can reduce repetition, but still requires templating infrastructure for what is logically a simple conversion step

Expected behavior:

• Converter applies consistently anywhere the column renders (cell, export if applicable, etc.)

• Works with sorting/filtering in a predictable way (ideally sorting/filtering still uses raw field value unless explicitly configured)

Hi,

I would like to have a Expand/Collapse All Grid Groups button in the Grid Header. I know this is possible to do so programmatically outside of the grid but my users want it inside the Grid. 

Thanks,

Humayoon

This public feature request:

• Explains how the TelerikRootComponent works.
• Outlines the problems of the current software design in static .NET 8 Blazor apps.
• Measures customer demand for a major change that may possibly resolve the current limitations.

How the TelerikRootComponent Works

Historically, the TelerikRootComponent was designed with the following purposes:

• To host and render all Telerik Blazor popups as RenderFragments. This means that all popups are rendered where the TelerikRootComponent is defined in the application's component hierarchy. In most cases, correct popup position requires the TelerikRootComponent to wrap all the content on the web page. Otherwise the correct position is not guaranteed and this is documented. In addition, the TelerikRootComponent instance is a CascadingValue, which allows it to collect all popup RenderFragments.
• The TelerikRootComponent exposes parameters for global application-wide Telerik settings, such as icon type or RTL support. This is another reason why it makes sense to have a single TelerikRootComponent that wraps all the page content.

Problems and Limitations in .NET 8 Blazor Static Apps

.NET 8 Blazor apps with "Per Component" interactivity location create a big challenge for the above state of affairs:

• Cascading values do not pass across render mode boundaries. .NET 8 includes a new feature for passing cascading values to interactive components (builder.Services.AddCascadingValues()), but this mechanism does not support passing of RenderFragments, because they are not JSON serializable. This brings the requirement that the TelerikRootComponent is part of an interactive component hierarchy.
• When the TelerikRootComponent is in a non-layout .razor file, it triggers more re-renders than normally. They are related to internal MediaQuery instances and all popups, which the root component manages.

So, developers who work with a globally static app with specific interactive components ("islands of interactivity") may need to:

• Place the TelerikRootComponent somewhere inside the component hierarchy, so it can't wrap all the page content. This will lead to wrong popup position.
• Use multiple TelerikRootComponents. This requires to define the same parameters for each TelerikRootComponent instance.

Next Steps

All developers who develop static .NET 8 Blazor apps with "Per Component" interactivity location:

1. Please vote for this feature request, so that we can measure how many customers are affected by the described limitations.
2. Post here and describe:
   • Why do you need to use apps with "Per Component" interactivity.
   • Your specific challenges with the current TelerikRootComponent setup.

Possible to add in the FileManager preview pane, a preview of the actual file, if the file type is simple; i.e. image or video (or pdf); or provide functionality to add preview.

Cheers

Phil

Currently working on moving from winform to Blazor and found a feature not supported in Telerik atm.

Getting current error when trying to enable Virtualiztion inside a grid

Groupable is not supported with the Virtualization feature of Telerik Grid

Where im already setting grouping on one of the columns

It is a very common occurrence to need to open a menu link in a new tab. Currently the prescribed way to do this is to create a Template for the Menu Items. This involves a lot of manual implementation  (verbose template code,  helper methods, changing the menu item object to not use the Url property so as to override the default UrlField behavior). This is a lot of extra work to accomplish a very common and simple task. 

I propose that a new property be introduced to the Menu component (to be added to Menu Items) - a boolean field that defines whether or not to open the link in a new tab (i.e. "NewTab", or "External", or something of the like). It could default to false so that, in most cases, it could be ignored. But if set to true, the Menu component would handle adding "target='_blank'" and "rel='noopener noreferer'" to the link, while leaving all of the other functionality and styling in place. 

It would greatly simplify the usage. And I would suggest that every programming who is building navigation menus would have a case where it's needed.

I would think, though I haven't looked at the core code yet, that this would be a relatively simple feature to add.   

public class MenuItem
{
    public string Text { get; set; }
    public ISvgIcon? Icon { get; set; }
    public string Url { get; set; } = string.Empty;
    public bool NewTab { get; set; } = false;
    public List<MenuItem>? Items { get; set; }

    public MenuItem(string text, ISvgIcon? icon, string url, bool newTab, List<MenuItem>? items)
    {
        Text = text;
        Icon = icon;
        Url= url;
        NewTab = newTab;
        Items = items;
    }
}