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
Parallel loading of charts with devtools open, should not have impact on performance.
Current behavior
we have a dashboard page in Angular 14 application which has multiple types of charts.
if user visits dashboard page and switches to different pages, the API calls takes a long time resolve in devtools.
This only occurs whenever we visit dashboard page(which have multiple charts).
While searching this issue came across below solution to disable async stack trace from developer tool settings and in that case it is working properly. chrome-slower-when-console-open-at-page-load
is there any configuration for chart to avoid this issue.
This does not sound like a chart.js issue if your api calls are loading slow. Also since it does not seem to reproduce inside of a stackblitz it is verry hard to almost impossible to debug
Expected behavior
Parallel loading of charts with devtools open, should not have impact on performance.
Current behavior
we have a dashboard page in Angular 14 application which has multiple types of charts.
if user visits dashboard page and switches to different pages, the API calls takes a long time resolve in devtools.
This only occurs whenever we visit dashboard page(which have multiple charts).
While searching this issue came across below solution to disable async stack trace from developer tool settings and in that case it is working properly.
chrome-slower-when-console-open-at-page-load
is there any configuration for chart to avoid this issue.
Reproducible sample
https://stackblitz.com/edit/angular-kgntsk?file=src%2Fchart-test.ts,src%2Fmain.ts
Optional extra steps/info to reproduce
It's hard to provide exact steps or environment with stack blitz.
Our case pages are inside material tab.
Possible solution
No response
Context
No response
chart.js version
4.4.2
Browser name and version
chrome v-124.0.6367.91
Link to your project
No response
The text was updated successfully, but these errors were encountered: