We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://codesandbox.io/p/sandbox/react-big-calendar-example-forked-kr3qfv?file=%2Fsrc%2FApp.js%3A25%2C1&workspaceId=aefb4e6d-7522-4f03-91d7-f1d6177ccdfa
When using the dayJS localizer, setting the default timezone incorrectly and unexpectedly shifts the min/max time range.
When switching timezones, the min/max should remain as is set (or default of 12:00am -> 11:59pm)
When switching timezones, the min/max are rendered/displayed as the tz set time but min/max is still the local time (not tz adjusted)
1.16.3
17.0.2
Chrome
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Check that this is really a bug
Reproduction link
https://codesandbox.io/p/sandbox/react-big-calendar-example-forked-kr3qfv?file=%2Fsrc%2FApp.js%3A25%2C1&workspaceId=aefb4e6d-7522-4f03-91d7-f1d6177ccdfa
Bug description
When using the dayJS localizer, setting the default timezone incorrectly and unexpectedly shifts the min/max time range.
Expected Behavior
When switching timezones, the min/max should remain as is set (or default of 12:00am -> 11:59pm)
Actual Behavior
When switching timezones, the min/max are rendered/displayed as the tz set time but min/max is still the local time (not tz adjusted)
react-big-calendar version
1.16.3
React version
17.0.2
Platform/Target and Browser Versions
Chrome
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: