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

Upgrading to 5.0.1 from 4.34.4 has caused UI issues. #1309

New Issue
Closed
opened 2026-01-29 17:51:56 +00:00 by claunia · 3 comments
claunia commented 2026-01-29 17:51:56 +00:00
Owner
Copy Link

Originally created by @freyfrey01 on GitHub (Jul 22, 2024).

Describe the bug
A clear and concise description of what the bug is.
Updating from Radzen.Blazor 4.34.4 to 5.0.1 has broken many of our date pickers. The calendar view no longer displays when selecting the calendar button on the date picker. Calendar button is very far off the intended input box.

To Reproduce

  1. Create a page with Radzen.Blazor 4.34.4 and add the DatePicker component, modify however you please.
  2. Update Radzen.Blazor to 5.0.1, notice DatePicker no longer works.

Expected behavior
A clear and concise description of what you expected to happen.
Expect updates between Radzen.Blazor to have no major effects on the functionality of razor pages. Keep the general layout and component visuals the same but improve backend performance or functionality. Do not expect several aspects to be broken due to production updates.

Screenshots
Radzen.Blazor 4.34.4 date picker component on razor page:
image

Radzen.Blazor 5.0.1:
image

Desktop (please complete the following information):

  • OS: Windows
  • Chrome
  • Chrome v126.0.6478.128

Additional context
Noticed this only occurs sometimes. With enough refreshes, the issue typically goes away but it has not been consistent with the date picker properly loading.

Originally created by @freyfrey01 on GitHub (Jul 22, 2024). **Describe the bug** A clear and concise description of what the bug is. Updating from Radzen.Blazor 4.34.4 to 5.0.1 has broken many of our date pickers. The calendar view no longer displays when selecting the calendar button on the date picker. Calendar button is very far off the intended input box. **To Reproduce** 1. Create a page with Radzen.Blazor 4.34.4 and add the DatePicker component, modify however you please. 2. Update Radzen.Blazor to 5.0.1, notice DatePicker no longer works. **Expected behavior** A clear and concise description of what you expected to happen. Expect updates between Radzen.Blazor to have no major effects on the functionality of razor pages. Keep the general layout and component visuals the same but improve backend performance or functionality. Do not expect several aspects to be broken due to production updates. **Screenshots** Radzen.Blazor 4.34.4 date picker component on razor page: ![image](https://github.com/user-attachments/assets/d90b30aa-c0e3-4ae7-ab4e-080cb2a5499e) Radzen.Blazor 5.0.1: ![image](https://github.com/user-attachments/assets/cc085194-773d-4d4f-ab90-1a2cbd43be70) **Desktop (please complete the following information):** - OS: Windows - Chrome - Chrome v126.0.6478.128 **Additional context** Noticed this only occurs sometimes. With enough refreshes, the issue typically goes away but it has not been consistent with the date picker properly loading.
claunia commented 2026-01-29 17:51:57 +00:00
Author
Owner
Copy Link

@akorchev commented on GitHub (Jul 22, 2024):

Try clearing your browser cache.

@akorchev commented on GitHub (Jul 22, 2024): Try clearing your browser cache.
claunia commented 2026-01-29 17:51:57 +00:00
Author
Owner
Copy Link

@freyfrey01 commented on GitHub (Aug 6, 2024):

Try clearing your browser cache.

@akorchev this resolved the issue but my site is open and regularly used by 500+ employees. Is there a way to force cache refresh or for the team to possibly add version control to CSS to prevent using cached CSS files such a cache-busting mechanism? I've already taken the action of putting no-cache headers for Javascript and CSS files to prevent this in the future

@freyfrey01 commented on GitHub (Aug 6, 2024): > Try clearing your browser cache. @akorchev this resolved the issue but my site is open and regularly used by 500+ employees. Is there a way to force cache refresh or for the team to possibly add version control to CSS to prevent using cached CSS files such a cache-busting mechanism? I've already taken the action of putting no-cache headers for Javascript and CSS files to prevent this in the future
claunia commented 2026-01-29 17:51:57 +00:00
Author
Owner
Copy Link

@akorchev commented on GitHub (Aug 6, 2024):

RadzenTheme does it out of the box. You can either use it or implement a similar versioning approach.

@akorchev commented on GitHub (Aug 6, 2024): [RadzenTheme](https://github.com/radzenhq/radzen-blazor/blob/master/Radzen.Blazor/RadzenTheme.razor.cs#L30) does it out of the box. You can either [use it](https://blazor.radzen.com/get-started/net8?theme=material3#theme) or implement a similar versioning approach.
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#1309
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?