New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DatePicker] February day value is set before checking the year #1688
Comments
Any update on this guys? |
Hi @krishnachaitanya137 It is currently in an unplanned stage so I increased the item's priority to Priority 2. |
I have the same problem in Angular. My clients are complaining about it these days as the current month is affected by it. |
Same problem in Telerik Blazor components. |
Hi @hallerupnet and @ryanbuening |
@ryanbuening for Blazor, I would suggest checking this feedback item that you can vote for and is related to this issue: If you have any further questions on this, I would suggest submitting a support ticket in the support system or their public forum. @hallerupnet As for this issue in Angular, I would suggest checking the following comment that addresses this behaviour. In addition, we have the same scenario as the one explained in the comment, and therefore, I will also close this issue since this is expected behaviour. If there are any further questions, please let me know about them. |
@WissamProgress Is this not gonna be fixed for react too? Is the response same as angular? |
Hi @krishnachaitanya137 , The fix should be related to handling this scenario specifically -> |
When setting the month to February and then setting the day to 29, it is automatically changed to 28. However, the day value in this case also depends on the year. For example, for a leap year like 2024, February has 29 days.
Therefore, the day value should be changed only after setting both the month and they year.
Step to reproduce:
It is automatically changed to 28 before setting the year which could be a leap year.
Related to Ticket ID: 1621932
The text was updated successfully, but these errors were encountered: