starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-04 05:35:44 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

RadzenDatePicker degrade performance on change page #548

New Issue
Closed
opened 2026-01-29 17:39:08 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 17:39:08 +00:00
Owner
Copy Link

Originally created by @Pmyl on GitHub (Sep 20, 2022).

Library versions
Radzen.Blazor v4.0.0
Microsoft.AspNetCore.Components.WebAssembly v6.0.9

Describe the bug
On a fresh Blazor WebAssembly application if a page contains the component RadzenDatePicker the change page action takes more time than usual. This causes the page to freeze for that time and chromium browsers to complain with [Violation] 'click' handler took XXXms.
The more RadzenDatePicker components there are in a page the slower it is and when the devtools is open it takes even longer.
Two RadzenDatePicker are enough to slow the change page by a noticeable amount compared to any other page.

This problem doesn't occur with any other Radzen component I've tried, only RadzenDatePicker.

To Reproduce
Steps to reproduce the behavior:

  1. Fresh Blazor application
  2. Install Radzen.Blazor
  3. Ensure the application has at least 2 pages (it should have them from the base Blazor template)
  4. Add the RadzenDatePicker component in one of the pages
    • Add <RadzenDatePicker @bind-Value="@FromDate" DateFormat="d" /> in the html part
    • Add private DateTime FromDate { get; set; } in the code part
  5. Switch between the two pages using the navigation menu on the left to notice the performance issue
  6. Add more of <RadzenDatePicker @bind-Value="@FromDate" DateFormat="d" /> in the same page to see the quick performance degradation

Expected behavior
Performance hit due to the page using the component RadzenDatePicker should not be noticeable when there are just few of them. The expectation is for the component to be aligned with other components from the Radzen.Blazor library in terms of performance.

Desktop:

  • OS: Windows 10
  • Browser: Latest Chrome/Brave/Edge/Firefox
Originally created by @Pmyl on GitHub (Sep 20, 2022). **Library versions** Radzen.Blazor v4.0.0 Microsoft.AspNetCore.Components.WebAssembly v6.0.9 **Describe the bug** On a fresh Blazor WebAssembly application if a page contains the component RadzenDatePicker the change page action takes more time than usual. This causes the page to freeze for that time and chromium browsers to complain with `[Violation] 'click' handler took XXXms`. The more RadzenDatePicker components there are in a page the slower it is and when the devtools is open it takes even longer. Two RadzenDatePicker are enough to slow the change page by a noticeable amount compared to any other page. This problem doesn't occur with any other Radzen component I've tried, only RadzenDatePicker. **To Reproduce** Steps to reproduce the behavior: 1. Fresh Blazor application 2. Install Radzen.Blazor 3. Ensure the application has at least 2 pages (it should have them from the base Blazor template) 4. Add the RadzenDatePicker component in one of the pages • Add `<RadzenDatePicker @bind-Value="@FromDate" DateFormat="d" />` in the html part • Add `private DateTime FromDate { get; set; }` in the code part 5. Switch between the two pages using the navigation menu on the left to notice the performance issue 6. Add more of `<RadzenDatePicker @bind-Value="@FromDate" DateFormat="d" />` in the same page to see the quick performance degradation **Expected behavior** Performance hit due to the page using the component RadzenDatePicker should not be noticeable when there are just few of them. The expectation is for the component to be aligned with other components from the Radzen.Blazor library in terms of performance. **Desktop:** - OS: Windows 10 - Browser: Latest Chrome/Brave/Edge/Firefox
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#548
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?