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
No response
I suspect it's because devicePixelRatio, but if I set it to 1 the canvas quality is worse
my chart options in Vue.js 2 options: { layout: { padding: 40, }, responsive: false, maintainAspectRatio: false, animation: { animateScale: true, }, plugins: { legend: { display: this.isLegend, }, tooltip: { enabled: this.chartType === 'single', }, }, },
options: { layout: { padding: 40, }, responsive: false, maintainAspectRatio: false, animation: { animateScale: true, }, plugins: { legend: { display: this.isLegend, }, tooltip: { enabled: this.chartType === 'single', }, }, },
v4.2.1
Mozilla Firefox
The text was updated successfully, but these errors were encountered:
We were having a similar issue where opening or closing Chrome's dev console was causing the graph to visually break.
We were able to resolve it by removing this line from options:
options
devicePixelRatio: 4,
Related threads for convenience:
Sorry, something went wrong.
Calling mychart.resize() also reproduces the bad scaling issue.
mychart.resize()
No branches or pull requests
Expected behavior
Current behavior
Optional extra steps/info to reproduce
No response
Possible solution
I suspect it's because devicePixelRatio, but if I set it to 1 the canvas quality is worse
Context
my chart options in Vue.js 2
options: { layout: { padding: 40, }, responsive: false, maintainAspectRatio: false, animation: { animateScale: true, }, plugins: { legend: { display: this.isLegend, }, tooltip: { enabled: this.chartType === 'single', }, }, },
chart.js version
v4.2.1
Browser name and version
Mozilla Firefox
Link to your project
No response
The text was updated successfully, but these errors were encountered: