SplitButton occasionally does not fire OnClick for its child items in UI for Blazor 3.7. and .NET 7

Progress® Telerik® UI for Blazor Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 01 Mar 2023 09:13 by ADMIN

Release 4.0.0 (18 Jan 2023) (R1 2023)

Michael

Created on: 17 Nov 2022 08:44

Category: SplitButton

Type: Bug Report

SplitButton occasionally does not fire OnClick for its child items in UI for Blazor 3.7. and .NET 7

I recently upgraded the target framework to .NET 7 and the UI for Blazor package to 3.7. With this configuration in my WASM app, it looks like the OnClick event for the child buttons is sometimes not fired. It happens occasionally and not for all child buttons.

===

ADMIN EDIT

===

Last working version: UI for Blazor 3.6.1. and .NET 6. You may revert to that configuration until the fix is live.

4 comments

ADMIN

Yanislav

Posted on: 01 Mar 2023 09:13

Hello Thomas,

Thank you for the confirmation.

I'm glad to hear that you've managed to resolve the issue and it is no more reproducible.

Regards,
Yanislav
Progress Telerik

Learn about the important changes coming in UI for Blazor 4.0 in January 2023!

Thomas

Posted on: 22 Feb 2023 13:59

Hi, managed to get it to work and it was related to a version missmatch. I can confirm that in version 4.0.1 it now works fine.

ADMIN

Yanislav

Posted on: 16 Feb 2023 12:49

Hello Thomas,

I've tested the behavior in a REPL example and on my side, the event handler is triggered correctly.

May I ask you to double-check if the version of the Telerik UI for Blazor package and especially the telerik.blazor.js file version is the latest one (4.0.0 / 4.0.1)?

Also, It is also possible that after the upgrade, the static files are cached.
With that being stated, could you try to clear the cache of your browser, perform a hard reload of the page, and inform me of the results?

If this does not resolve the problem, can you provide a runnable sample that reproduces the issue? This way, we can properly investigate and determine the cause of the problem.

Thank you for your cooperation in advance.

Regards,
Yanislav
Progress Telerik

Learn about the important changes coming in UI for Blazor 4.0 in January 2023!

Thomas

Posted on: 09 Feb 2023 13:57

We still have this problem i release 4.0.0 and with .NET 7.

We have found out that it is some kind of timing problem and related to the property "AnimationDuration". If we set the "AnimationDuration" to 0 or a low value like 100 or 200 it is much easier to reproduce the problem.