frontend
frontend copied to clipboard
[local calendar]: Time selector changes on date change.
Checklist
- [X] I have updated to the latest available Home Assistant version.
- [X] I have cleared the cache of my browser.
- [X] I have tried a different browser to see if it is related to my browser.
Describe the issue you are experiencing
When I try to add new event to local calendar from my Home Assistant app selected start and end time changes whenever new date in the datepicker is selected. I was able to reproduce it in HA app, as well as on mobile in Firefox browser. The behavior is the same in both cases, so I consider that this bug is somewhere in frontend.
Describe the behavior you expected
Time and date doesn't change after they were set to some value. If that behavior is triggered by "autofix" for negative intervals (when start time of event is after end time), then possibly it should be some checkbox to prevent that autofix.
Steps to reproduce the issue
- Maybe important precondition: Set your device timezone to a different one than configured in HA
- Go to local calendar and add new event
- Enter 12:00 to event start time
- Change the start date of event
- Observe that time in timepicker had changed.
- Repeat 3-5 steps and see that it continue changing. ...
See video for details: https://drive.google.com/file/d/1OFnjTVxoq92g3MwN0kkr-_z-2WuwoPfy/view?usp=sharing
What version of Home Assistant Core has the issue?
core-2022.12.1, frontend 20221208.0 core-2022.12.4, frontend 20221212.0
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Firefox mobile 107.2.0, Chrome desktop 108.0.5359.71, Firefox desktop
Which operating system are you using to run this browser?
Android, Linux
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
UPD: if browser timezone is set to the same as HA instance, the bug is not reproduced.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.