-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Plotly relayout autorange fails with automargins. #3106
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
Comments
Thanks @justnick21 - But I haven't managed to reproduce this error. Here's a try based on one of our existing automargin mocks: https://codepen.io/alexcjohnson/pen/wYPdBN?editors=1010 |
Sorry I am unable to reproduce this issue in a codepen. Not sure why the key is no longer on that object. Stack trace attached but without spending a lot of time reproducing this in a pen I am afraid I can't give any more details
|
OK thanks! I'll leave this report open for a while in hopes that we can figure out the root cause, but I don't think it's a good idea to address the symptom directly before that, as there are very likely to be other ways whatever this problem is can manifest itself. |
Closing due to lack of reproducible example. @justnick21 feel free to open another issue when/if you're able to reproduce this in a codepen. |
I have the exact same issue. Only happens if xaxis.autorange is set to true though. If I only set yaxis.autorange the issue goes away. And no, I have not been ble to reproduce it in a codepen. This is with a simple scatter. |
Same here with v1.58.4. Tried to reproduce it on CodePen but couldn't! If useful, I'll leave my CodePen here: https://codepen.io/federicomassa/pen/JjKXELq |
Still have this issue in 2.1.0 |
When
fixLabelOverlaps
is called (axes.js:1807) via:tester = drawing.tester.node();
insidesrc/components/drawing/index.js.drawing.bBox
fails because there is no tester node. Thejs-plotly-tester
is on the page, just not referenced in the drawing object.Can be fixed by adding
if (!drawing.tester) drawing.makeTester()
on the line above.I saw some discussion about the performance of the measuring so I thought I would raise as a bug before making a PR.
The text was updated successfully, but these errors were encountered: