Unplanned
Last Updated: 12 Dec 2025 09:02 by ADMIN
Andrew
Created on: 17 Nov 2025 13:54
Category: Grid
Type: Bug Report
4
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

  1. 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

2 comments
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! :)