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

Time in DayView of Scheduler is displayed wrong for some cultures #235

New Issue
Closed
opened 2026-01-29 17:33:55 +00:00 by claunia · 1 comment
claunia commented 2026-01-29 17:33:55 +00:00
Owner
Copy Link

Originally created by @Mrxx99 on GitHub (Oct 30, 2021).

Describe the bug
The time is displayed wrong in the DayView of the Scheduler when local culture is German ("de-DE").
It is displayed the following way:

8
9
10
11
12
1
2
3
...

As you can see they are just shown as number and after 12 it just starts with 1 again, which is very confusing because if you scroll down a bit so 12 is not shown anymore you wouldn't even know it is the time past midday. In German culture and I think in many other cultures besides US/GB the time counts up after 12 and does not start with 1 again. Also maybe it would be better to also display the time formatted as actual time for the selected culture not just as a number:
08:00
..
12:00
13:00
...

To Reproduce
Steps to reproduce the behavior:

  1. Go to the Startup.cs of the RadzenBlazorDemo in this repository
  2. Uncomment the localization sample code in "ConfigureServices" and "Configure" methods (which conveniently already use German culture as a sample)
  3. Start the sample and navigate to the Scheduler sample page (/scheduler)
  4. In the scheduler switch to day view

Expected behavior
I would expect the time displayed fitting to the current culture of the user. So:
08:00
..
12:00
13:00
14:00
...

or at least the right number used for each hour of the day for the user culture.

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Edge
  • Version 95.0.1020.30

Additional context
This was tested with both the current stable release package 3.11.10 as with the current commit on the master branch 07e61cd1d3

Originally created by @Mrxx99 on GitHub (Oct 30, 2021). <!-- IMPORTANT: Read this first!!! 1. If you own a Radzen Professional or Еnterprise subscription you can report your issue or ask us a question via email at info@radzen.com. Radzen staff will reply within 24 hours (Professional) or 16 hours (Enterprise) 2. The Radzen staff guarantees a response to issues in this repo only to paid subscribers. 3. If you have a HOW TO question start a new forum thread in the Radzen Community forum: https://forum.radzen.com. Radzen staff will close issues that are HOWTO questions. 4. Please adhere to the issue template. Specify all the steps required to reproduce the issue or link a project which reproduces it easily (without requiring extra steps such as restoring a database). --> **Describe the bug** The time is displayed wrong in the DayView of the Scheduler when local culture is German ("de-DE"). It is displayed the following way: ``` 8 9 10 11 12 1 2 3 ... ``` As you can see they are just shown as number and after 12 it just starts with 1 again, which is very confusing because if you scroll down a bit so 12 is not shown anymore you wouldn't even know it is the time past midday. In German culture and I think in many other cultures besides US/GB the time counts up after 12 and does not start with 1 again. Also maybe it would be better to also display the time formatted as actual time for the selected culture not just as a number: 08:00 .. 12:00 13:00 ... **To Reproduce** Steps to reproduce the behavior: 1. Go to the Startup.cs of the RadzenBlazorDemo in this repository 2. Uncomment the localization sample code in "ConfigureServices" and "Configure" methods (which conveniently already use German culture as a sample) 3. Start the sample and navigate to the Scheduler sample page (/scheduler) 4. In the scheduler switch to day view **Expected behavior** I would expect the time displayed fitting to the current culture of the user. So: 08:00 .. 12:00 13:00 14:00 ... or at least the right number used for each hour of the day for the user culture. **Screenshots** ![image](https://user-images.githubusercontent.com/33566379/139538255-1175ac01-df2b-468a-94ee-4a1975b77d84.png) **Desktop (please complete the following information):** - OS: Windows 10 - Browser Edge - Version 95.0.1020.30 **Additional context** This was tested with both the current stable release package 3.11.10 as with the current commit on the master branch https://github.com/radzenhq/radzen-blazor/commit/07e61cd1d3fc4895d17d2b39afad66ae28ba1953
claunia commented 2026-01-29 17:33:56 +00:00
Author
Owner
Copy Link

@akorchev commented on GitHub (Nov 1, 2021):

That setting is exposed as a property and you can set it as you need.

@akorchev commented on GitHub (Nov 1, 2021): That setting is [exposed as a property](https://github.com/radzenhq/radzen-blazor/blob/master/Radzen.Blazor/RadzenDayView.razor.cs#L27) and you can set it as you need.
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#235
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?