-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
drillUp. Cannot set property 'length' of undefined #8324
Comments
Hi @balkarov, Demo: Internal note |
Calling Normal async flow:
Programmatic flow (as suggested above):
Now, if I need to support both programmatic and user-click events, it becomes annoying because I will have to cancel the next I looked through the code, and I believe the absence of So, it feels like calling Or, maybe just initialize |
As a workaround, I'm currently just adding these lines after a programmatic drilldown: if (!chart.ddDupes) { // https://github.com/highcharts/highcharts/issues/8324
chart.ddDupes = [];
} |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
Hello. Why you close this issue? Did you fix it? What’s the release? |
Hi @balkarov, |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
Hello. Why you close this issue? Did you fix it? What’s the release? |
Hello @balkarov, This issue is still not fixed. The stale bot marks the issues, which are inactive for a long period of time as stale, and then closes them due to the inactivity. I will move this issue to the inbox so that it will be prioritized. Sorry for the inconvenience. |
Cannot set property 'length' of undefined
when calldrillUp()
afterchart.applyDrilldown();
Screenshot:
Expected behaviour
Not error
Actual behaviour
Error
Live demo with steps to reproduce
https://jsfiddle.net/jus3gc2n/
Product version
Highcharts version 6.1.0
Affected browser(s)
Chrome 66.0.3359.139
The text was updated successfully, but these errors were encountered: