Skip to content

console errors when calling Plotly.newPlot in tables #2312

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

Closed
VeraZab opened this issue Jan 31, 2018 · 1 comment · Fixed by #2314
Closed

console errors when calling Plotly.newPlot in tables #2312

VeraZab opened this issue Jan 31, 2018 · 1 comment · Fixed by #2314
Assignees
Labels
bug something broken

Comments

@VeraZab
Copy link

VeraZab commented Jan 31, 2018

See this codepen for ex:
https://codepen.io/veraz/pen/oEgRJK?editors=1010

@monfera the new (editor)[https://github.com/plotly/react-plotly.js-editor] closely relies on plotly.js.

It's failing for table traces because there's errors in the console once we're trying to gradually create a table trace. Because of the console errors, this react-plotly.js call never entirely completes and instead falls into this catch statement: https://github.com/plotly/react-plotly.js/blob/9dc4e4f8810c150c88c08c81b8432d6e9952641e/src/factory.js#L126

It should be possible to gradually create a trace without it throwing console errors.
cc @alexcjohnson

@etpinard etpinard added the bug something broken label Jan 31, 2018
@monfera
Copy link
Contributor

monfera commented Jan 31, 2018

Thanks @VeraZab I'll take a look!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants