Delay in applying Grid row hover styles in .NET10

Progress® Telerik® UI for Blazor Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Unplanned

Last Updated: 15 Jan 2026 07:28 by ADMIN

Andrew

Created on: 17 Nov 2025 13:54

Category: Grid

Type: Bug Report

Delay in applying Grid row hover styles in .NET10

Description

When going fast over the Grid rows with the mouse cursor, the rows are highlighted after a delay. The delay is more noticeable on higher resolutions (2560x1440 or higher).

Steps To Reproduce

Hover the first Grid row and move the mouse cursor towards the last row (or vice versa).

Actual Behavior

In the app that targets .NET10 the row hover styles are applied with a delay, whereas in the app that targets .NET8 the hover styles are applied as soon as the mouse enters the boundaries of a row.

Expected Behavior

Similar performance in applying hover-related styles.

Browser

All

Last working version of Telerik UI for Blazor (if regression)

No response

4 comments

ADMIN

Dimo

Posted on: 15 Jan 2026 07:28

Hello Andrew,

Thanks a lot for the update, I appreciate it!

I doubt that there is a direct relationship between our packages and the WPF ones. More likely this is a matter of pure CSS behavior.

Consider the following test page with three different use cases: https://blazorrepl.telerik.com/wqEbFzYV266qvw5905

Please copy that markup to your WPF app and check if the mouseover performance is the same in all three tables. You can even split the three scenarios to three separate pages for full isolation.

Regards,
Dimo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Andrew

Posted on: 14 Jan 2026 22:43

After doing some more debugging, it seems like this specific nuget is the problem:

Microsoft.AspNetCore.Components.WebView.Wpf

I found an old app that was still using Telerik.UI.for.Blazor 8.1.1. I updated the project's target platform to .NET 10, ran it, and it worked fine. I then updated every AspNetCore nuget EXCEPT that one to the newest version. App works fine.

But the moment I update that WebView.Wpf from 8.0.100 to 10.0.20, everything gets super slow. Even with the old telerik library.

I thought that updating telerik to 12.2.0 was causing the issue, but nope, this problem even happens with an older telerik library still. It's the WebView.Wpf causing the problem with the telerik libraries. Or maybe the telerik libraries aren't playing well with the new Wpf code from microsoft?

So for now I've updated to telerik 12.2.0 and everything else to .NET 10, except that Wpf nuget, and the app is fine now. So there's something fishing with that Wpf nuget and telerik's components somehow...???

just wanted to update this ticket with my findings today.

ADMIN

Dimo

Posted on: 12 Dec 2025 09:02

Hi Andrew,

Given that the problem occurs only in Blazor hybrid WPF apps and this item has only one vote, its priority is unfortunately low.

Thus, please plan with the assumption that we won't be allocating time on this task in the foreseeable future. Sorry about that.

Regards,
Dimo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Andrew

Posted on: 08 Dec 2025 22:42

NOTE: This appears to just be a problem for Windows Blazor Hybrid WPF Desktop apps. For server side web pages, and for MAUI desktop apps it does not seem to be an issue.

I realize this is in the "Unplanned" category, but since .NET 8 is going Out-of-Support by Microsoft in November 2026, we would like to see if you had a "rough" timeline if you think this will realistically be fixed in the next year or not?

If realistically, or 50+% probability, that it will NOT be fixed, please let us know as soon as you can so we can plan accordingly (either migrating JUST that one app to MAUI, or staying on .NET 8 until it's fixed; neither seems palatable. or some other unknown-as-of-yet workaround).

Thanks! :)