Sometimes with a dropdown button I would like to have Category headers or Separators to breakup the list. To accomplish a seperator it needs to be added to another existing DropDownItem. To create a category header you can style an existing DropDownItem, however it's still clickable so it becomes obvious to the user that this is a bit of a misuse of the control. Native support for Categories or Separators would be ideal, however, just having control over the click behavior and perhaps a Template property for full control over this one items rendering would make it more extensible.

Thank you,

-Andy

Hi Team,

It might be a better user experience if the user does not have a valid license key to either:

a) make it clear that if the downloader does not have a license assigned the downloaded license key will not be valid

or

b) do not let anyone without a license assigned download the key file (that seems preferable & probably easier to implement)

Thank you!

Since <TelerikGrid> is implemented as two separate <table>s, one for the headers and a second for the grid, it does not show repeated headers on subsequent pages when using the browser's Print feature. 

Due to limitations of the <TelerikGrid> export functionality, I use the browser print function to export PDFs.

I need the table headers to duplicate on subsequent printed and exported pages. 

I wonder if there is a way to duplicate the <thead> info in the second table and suppress its display but enable it for @media Print.

More details in ticket 1691848

Hi Telerik Team!

We’ve noticed that your official website uses anchor scrolling (clicking on links to scroll to specific sections smoothly), and we’d love to see that as a Telerik Blazor component.

This would be super useful in scenarios where:

• The only way to present content is via long scrollable pages

• Tabs aren’t a good UX fit

What we’re looking for:

-Smooth scrolling to internal page anchors (sections)

-Scrollspy-like feature to highlight active section

-Optional scroll offset for sticky headers

-Lightweight, flexible integration (with or without Telerik Form/Layout components)

We feel this would be a great addition to the Telerik Blazor suite — especially for documentation-style pages, long forms, or configuration panels.

Thanks a lot and keep up the awesome work!

Best regards,
Bohdan

In the docs https://www.telerik.com/blazor-ui/documentation/components/chart/overview#styling-with-css-variables there is an example on using CSS variables to set colours of the Chart component. And yes, if I set the --kendo-chart-bg CSS variable to some colour, the chart background is coloured with it. But, I can't change the colour at runtime, for example for switching between light and dark themes at user request.

But, shouldn't this be possible as the SVG is rendered inline? I see the chart being rendered as elements like below where the fill propertys value comes from the --kendo-chart-bg variable. But if the fill was instead set to "var(--kendo-chart-bg)" I would be able to change --kendo-chart-bg at runtime and the chart would reflect the change without needing to be refreshed separately? Same should go for all the text and series' colours.

<svg>
<g>
<path d="M0 0 L 400 0 400 240 0 240Z" stroke="none" fill="#0f0"></path>
</g>
</svg>

I also saw this, but I think this is before you added the CSS colouring? https://feedback.telerik.com/blazor/1496389-using-custom-themes-changing-at-runtime-does-not-change-the-chart-component-style

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

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 OnPaneResize (and SizeChanged) event does NOT fire when a pane is unpinned. When it flies out from the left, resizing the flyout does not fire events that would letus refresh the chart to fill the new size.

Reproduced in this REPL:  https://blazorrepl.telerik.com/mfkqODwk35srscZe46

Hi,

I'm using two TelerikListBox elements, one left, one right. The right ones Data attribute is bound to already selected items that I get from the DB through EF Core. As you know, EF Core makes use of navigation properties. As you probably also know, the TelerikListBox recursively copies elements on binding. This causes a documented StackOverflowException, as written here -> https://www.telerik.com/blazor-ui/documentation/knowledge-base/common-stackoverflowexception-editing-circular-references.

I fixed the issue by calling 

.Select(x => x.RemoveNavigation())

before binding, with RemoveNavigation being a simple "NavigationProp = null; return this;" function.

Eventhough this works, I think

a) the documented solution is not great, because the navigation properties are very useful, are one of the big reasons to even use EF Core in the first place and are automatically generated by, for example, EF Core Power Tools. Expecting the users to remove them from affected models is not a viable long term solution.

b) it would be better for Telerik to fix the issue by implementing some kind of logic to prevent the issue alltogether. My suggestion would be to ignore virtual, non-collection object properties on copy. 

I my understanding, the simplest way to get a coding agent provide better assistance to a very specific product like telerik blazor, is by just providing the documentation. 

My first experiments with the telerik mcp server are not succesful. I would think that linking the full documentation directly to the coding agent can seriously lead to better results.

AI Coding agents are doing a great job with more standard frontend framework like react, they seem to be common knowledge. We know that Blazor and in particular Telerik blazor is a niche product (not only niche, but also NICE), so coding agents needs to have clear instructions on everything.

Of course, i don't know how your documentation system works, and how easy it would be to generate .md files from this?

Thanks for looking into this matter

Don't hesitate to contact me directly for further questions or whatsoever.

warm regards

paul