You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please confirm that the bug report does not already exist
I confirm there is no existing issue for this bug.
Steps to reproduce
Make any calendar event. Observe that the current time cursor is pointing later than the time of the event even when the event is supposed to be later than the current time.
Desired Behavior
Cursor should point at the correct time.
Project Details
NocoDB in docker: true
Version 0.255.2
Attachments
The text was updated successfully, but these errors were encountered:
Hey @pippijn! I'm here to help you with any bugs, questions, or contributions you have for NocoDB. Let's tackle this issue together!
The issue with the current time cursor being in the wrong place could be related to timezone handling. The calendar component retrieves time information based on the server's timezone (GMT by default). If the browser's timezone differs from the server's timezone, the displayed time may be incorrect [1].
To address this, ensure that the server and browser timezones are synchronized. You might also want to check if there are any discrepancies in the timezone settings within your Docker environment or the NocoDB configuration.
If the problem persists, consider reviewing the code responsible for rendering the current time cursor to ensure it correctly accounts for timezone differences.
Please confirm that the bug report does not already exist
Steps to reproduce
Make any calendar event. Observe that the current time cursor is pointing later than the time of the event even when the event is supposed to be later than the current time.
Desired Behavior
Cursor should point at the correct time.
Project Details
NocoDB in docker: true
Version 0.255.2
Attachments
The text was updated successfully, but these errors were encountered: