Skip to content
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

Bug: Mathjax problem with multiaxis markers #4361

Closed
kndidox opened this issue Nov 18, 2019 · 3 comments
Closed

Bug: Mathjax problem with multiaxis markers #4361

kndidox opened this issue Nov 18, 2019 · 3 comments
Labels
bug something broken

Comments

@kndidox
Copy link

kndidox commented Nov 18, 2019

Hello guys, first of all thanks for such an amazing work with Plotly.

I am experiencing a curios bug when i try to create some plots with multiple axis and legends in latex.

When the mathjax library is loaded, the plot paint some markers to the right of the desired position, my first "solution" to this was to call the relayout method, and this kinda works, but when i call the toImage method to save my plot my markers are now again in the wrong position.

You can reproduce all the mentioned above in this: Fix Issue with MathJax + relayout

Edit: i have created two more codepen's explaining the problem
1- Correct marker display without mathjax & relayout
2- Incorrect marker display without mathjax & relayout

@etpinard
Copy link
Contributor

Thanks very much for reporting!

I suspect the Plotly.plot promise (used internally by Plotly.react and Plotly.toImage) resolves before the auto-range <--> auto-margin computation loop is completed.

Next, we should try to "fix" the problem by setting the axis range for all the axes on the graph AND setting the layout.margin before calling Plotly.toImage to see if the problem persist.

cc #2704

@etpinard etpinard added the bug something broken label Nov 28, 2019
@kndidox
Copy link
Author

kndidox commented Jan 14, 2020

Hello guys, thanks very much for your answer. Do you have an estimated date for fix this bug?

@gvwilson
Copy link
Contributor

Hi - we are currently trying to tidy up Plotly's public repositories to help us focus our efforts on things that will help users most. Since this issue has been sitting for several years, I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our backlog. Thanks for your help - @gvwilson

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

No branches or pull requests

3 participants