[v11.0.x] DateTimePicker: Alternate timezones now behave correctly #87041
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport 7fab894 from #86750
What is this feature?
It's a bugfix for the timezone issue with the
DateTimePicker
Why do we need this feature?
Currently, users that have one timezone in Grafana (
bootData
) and another on in their client/browser, cannot use theDateTimePicker
as it changes the dateonBlur
as well as showing invalid date/time information in date/time modal.Who is this feature for?
Developers who wants to use
DateTimePicker
as well as users that already are interacting withDateTimePicker
in published pluginsWhich issue(s) does this PR fix?:
86305
Fixes #86305
Special notes for your reviewer:
setTimeZoneResolver
needs to be used to change timezone.There are notes in #86305 how you could do this.
I just added the blow snippe to
DateTimePicker.story.tsx
:Please check that: