Skip to content

fix: use consistent timezone-based indices for availability#15

Open
netarvd wants to merge 1 commit intocsaye:mainfrom
netarvd:fix_timezone_calendar_index
Open

fix: use consistent timezone-based indices for availability#15
netarvd wants to merge 1 commit intocsaye:mainfrom
netarvd:fix_timezone_calendar_index

Conversation

@netarvd
Copy link
Copy Markdown

@netarvd netarvd commented Jan 31, 2026

Previously, availability interval indices were assigned based on the viewer's timezone display order. This caused users in different timezones to save different actual times when selecting the same visual slots.

meetingbrew-before.mp4

Now indices are assigned in meeting-timezone order using an intervalIndexMap, ensuring that index N always refers to the same absolute time slot regardless of the viewer's timezone.

meetingbrew-after.mp4

(btw sorry for the weird dark mode it's an extension)

Previously, availability interval indices were assigned based on the
viewer's timezone display order. This caused users in different
timezones to save different actual times when selecting the same
visual slots.

Now indices are assigned in meeting-timezone order using an
intervalIndexMap, ensuring that index N always refers to the same
absolute time slot regardless of the viewer's timezone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants