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
1️⃣ Once loaded, go to page A. You should see the chart.
2️⃣ Click on "back" home.
3️⃣ Go to page B. You don't see the chart.
In the console you should see the error: Uncaught (in promise) InternalError: too much recursion.
If you click on "back" home, you won't be able to.. and the console display the error: Uncaught (in promise) TypeError: this.w.globals.dom.Paper is undefined.
Refreshing the page solves the issue, but this is not the intended behavior.
If we don't set the responsive property on the config, then, none of those error would happen.
The text was updated successfully, but these errors were encountered:
If anyone is interested, I found a workaround.. not the best, obviously, but it solves my problem.
I'm using https://vueuse.org/core/useBreakpoints/ from the vueuse package.
So, instead of using the responsive option, I manually change the options object based on the current breakpoint.
I've also bumped into this... the issue seems to start as long as I update other chartOptions settings. If the responsive is there, it falls into "Internal Error: too much recursion" after a few seconds.
As soon as I add a
responsive
property in theconfig
object, any update to the config will trigger a "too much recursion" error.I found a similar report on StackOverflow
Reproduction
I created a simple bug reproduction there.
1️⃣ Once loaded, go to page A. You should see the chart.
2️⃣ Click on "back" home.
3️⃣ Go to page B. You don't see the chart.
In the console you should see the error:
Uncaught (in promise) InternalError: too much recursion
.If you click on "back" home, you won't be able to.. and the console display the error:
Uncaught (in promise) TypeError: this.w.globals.dom.Paper is undefined
.Refreshing the page solves the issue, but this is not the intended behavior.
If we don't set the
responsive
property on theconfig
, then, none of those error would happen.The text was updated successfully, but these errors were encountered: