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
After updating a specific scale either by its index and calling chart.update() the scales should change to reflect the new value as shown in the documentation.
Current Behavior
After updating the scale and calling chart.update() nothing happens.
Possible Solution
There are a couple of bugs (#4896 , #5452) that note issues with scales.ticks but the min and the max exist outside the ticks object so I thought I should create a new issue. It may be related.
The JS fiddle is pretty much copied and pasted from my actual project but without the overhead of the code that loads the data so there aren't any datasets, but the behavior is the same regardless.
Environment
Chart.js version:2.7.2
Browser name and version: Chrome 66.0.3359.139, Firefox 59.0.3
The text was updated successfully, but these errors were encountered:
Closing this as @SENSEi-James says, min and max are the tick configuration options as described in Linear Axis and Logarithmic Axis. Once the properties in the example are changed, it works as expected.
Expected Behavior
After updating a specific scale either by its index and calling chart.update() the scales should change to reflect the new value as shown in the documentation.
Current Behavior
After updating the scale and calling chart.update() nothing happens.
Possible Solution
There are a couple of bugs (#4896 , #5452) that note issues with scales.ticks but the min and the max exist outside the ticks object so I thought I should create a new issue. It may be related.
Steps to Reproduce (for bugs)
Bug demonstrated in JS fiddle.
Context
The JS fiddle is pretty much copied and pasted from my actual project but without the overhead of the code that loads the data so there aren't any datasets, but the behavior is the same regardless.
Environment
The text was updated successfully, but these errors were encountered: