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
Check this if you would like to implement a PR, we are more than happy to help you go through the process.
Current and expected behavior
I am trying to set timezone for the chart using DateFormat to UTC (GMT + 0)
Current behavior:
The timezone of the ticks, which appear as popup on hover changes to UTC but the timezone of the x-axis still is in my local timezone.
Expected behavior:
The timezone of the ticks, which appear as popup on hover & the times on the x-axis have the UTC timezone
I went through the google chart docs, they suggested that instead of passing JS Date Object one should instead use a date-time string, I tried that as well but got the same result.
In the screenshot above, the time in tick is 5 AM UTC, whereas the corresponding x-axis point is 10:30 AM, which is my local timezone (IST)
I have provided the sandbox link in the reproduction section for the same.
Would you like to work on a fix?
Current and expected behavior
I am trying to set timezone for the chart using DateFormat to UTC (GMT + 0)
Current behavior:
The timezone of the ticks, which appear as popup on hover changes to UTC but the timezone of the x-axis still is in my local timezone.
Expected behavior:
The timezone of the ticks, which appear as popup on hover & the times on the x-axis have the UTC timezone
I went through the google chart docs, they suggested that instead of passing JS Date Object one should instead use a date-time string, I tried that as well but got the same result.
In the screenshot above, the time in tick is 5 AM UTC, whereas the corresponding x-axis point is 10:30 AM, which is my local timezone (IST)
I have provided the sandbox link in the reproduction section for the same.
Reproduction
https://codesandbox.io/s/tender-orla-hlpv8f
react-google-charts version
v4.0.0
Possible solution
No response
The text was updated successfully, but these errors were encountered: