-
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
Please can #10890 be reopened as it's not fixed? #11547
Labels
Comments
Another related issues, some of them might be closed as duplicates: |
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
Related threads for convenience:
|
Calling |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
There are comments on #10890, but I think they're being missed as the thread is closed. Can that thread be reopened as the bug still exists in the latest version? I just wanted to bring this to your attention as I thought the comments on #10890 were not being seen.
Thank you for everything you do; this package is incredible :pray
Current behavior
As in #10890
Reproducible sample
As in #10890
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
v4.4.0
Browser name and version
No response
Link to your project
No response
The text was updated successfully, but these errors were encountered: