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
In PR #2527, a few oddities with relayout on graphs with axis constraints (i.e. (x|y)axis.constrain: 'range' || 'domain') were detected.
From #2527 (comment) and below, tests coverage was deemed inadequate to assume anything about the current behavior. The first step would be to beef up the coverage there. Next, determine whether or not graphs with axis constraints do need to go though the editType calc on axis range relayouts. Finally, we should lock down the limitations (if any) of editType axrange for graphs with axis constraints.
introduced in 1.36.0 (probably from PR #2527) where the y-axis is getting re-position properly. This should be a good starting point for this ticket here.
Could making range relayout go through editType "plot" (instead of "calc") be sufficient?
Do we have a test of setting mutually-exclusive range values, as per the comment on that line? If we do, and the result correctly fixes them for the constraints, then go for it!
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories 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 stack. Cheers - @gvwilson
Activity
etpinard commentedon May 10, 2018
Found a bug in https://codepen.io/etpinard/pen/qYopzp
introduced in
1.36.0(probably from PR #2527) where the y-axis is getting re-position properly. This should be a good starting point for this ticket here.[-]Investigate relayout + axis constraints behavior[/-][+]Investigate relayout & react + axis constraints behavior[/+]etpinard commentedon May 14, 2018
PR #2628 fixed the 🪲 reported above in #2540 (comment), but many issues remain.
Pasting #2628 (comment) here:
A few more comments on constrained axes, that should be followed up in #2540:
plotly.js/src/plot_api/plot_api.js
Line 2039 in a132b85
with
flags.plot = true, no tests are failing.Plotly.reactis broken with constrained axes. I'm not sure if it's always been broken or if the recently-added "axrange" edit did it 😕and @alexcjohnson 's #2628 (comment)
Do we have a test of setting mutually-exclusive range values, as per the comment on that line? If we do, and the result correctly fixes them for the constraints, then go for it!
gvwilson commentedon Jun 11, 2024
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories 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 stack. Cheers - @gvwilson