-
Notifications
You must be signed in to change notification settings - Fork 272
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
Incorrect Default Time in DateTimePicker #7992
Comments
Hi colleagues, Best regards, |
We are using this "data-ui5-compact-size" in our code, so we cant remove this. |
Hi team i am waiting for your reply. |
Hi Team, it's been 5 days, no response from your side. |
Hello @rahish13, the team is investigating the issue and will reply you as soon as has findings. Best regards, |
Hello @rahish13, We are currently working on a fix of the issue. Best Regards, |
Hi Team in which version of ui5 you have fixed this? |
1 similar comment
Hi Team in which version of ui5 you have fixed this? |
@rahish13 in 1.22.0 |
Bug Description
The DateTimePicker component in our UI5 web application is exhibiting unexpected behavior related to the default time when selecting a date. It consistently provides an incorrect default time instead of occasionally using the local time, which is causing usability and data entry issues for our users.
Affected Component
DateTimePicker
Expected Behaviour
When selecting a date, the DateTimePicker should automatically use the local time or, at the very least, display a time value that accurately corresponds to the selected date.
Isolated Example
https://codesandbox.io/p/sandbox/unruffled-bose-clwcy8
Steps to Reproduce
Navigate to the DateTimePicker in the application.
Select a date by clicking on the calendar icon.
Observe that the DateTimePicker sets an incorrect default time.
Log Output, Stack Trace or Screenshots
No response
Priority
High
UI5 Web Components Version
1.17.0
Browser
Edge
Operating System
No response
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: