-
Notifications
You must be signed in to change notification settings - Fork 11.9k
New issue
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
Wrong offset on bar chart with time xAxes #6024
Comments
I haven't looked closely at this issue yet, but wonder if it's the same as #5609 which was fixed in master, but not released yet |
This was fixed in #5933. Please try master build. |
Just to be sure I replaced the contents of both Please let me know if you need more information |
Can you share a jsfiddle or codepen? |
@MidNightP I don't think that alone will do anything. After you replace those files, you need to update the |
Ah great! It works with dist/Chart.bundle.min.js Any idea when this will be released? |
Ok, I'm going to close this as fixed then. I'm afraid I don't have an ETA on the release. It's been awhile since our last one and there's been lots of good improvements, so it'll happen at some point |
Same issue as #5784 (closed)
Also on Stackoverflow: https://stackoverflow.com/questions/54327783/wrong-offset-on-bar-chart-with-time-xaxes
Using Chart.js I have a bar chart with a wrong offset when the dataset has only a single t value.
Here's an example:
As can be seen, the bars are not centered.
First I suspected I did something wrong with the
offset
setting, but no. When having more than 1 time values the offset is right and the bars are centered.To show that
offset: true
on the xAxes is working when there are multiple t values, I also added an example of a proper layout;I've been reading the documentation thoroughly and it seems to me now that the issue is not caused by a wrong setting.
Current code:
Then after changing the datasets I call
this.chart.update()
Running latest version of Chart.js: 2.7.3
The text was updated successfully, but these errors were encountered: