_fullLayout.*axis.autorange is never "reversed"
See original GitHub issueEven when I set layout.xaxis.autorange = "reversed"
, it seems that it gets overwritten to true
and so does _fullLayout.xaxis.autorange
, making it impossible to build an RCE control for reversing the autorange.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Can not set a range when the ax is reversed -plotly
I found the answer. Apparently to reverse an axis you don't need to autorange it, but just set the range backwards layout1= go....
Read more >Autorange 'reversed' doesn't allow specifying range #3176
The yaxis range isn't respected in this example: https://codepen.io/anon/pen/yRrKpN Potentially related to #3075 and #553 .
Read more >Reversed axis with range specified - Plotly Community Forum
An xaxis range greater then the real range of the x-values of your data points is displayed in a Plotly plot only when...
Read more >Plotting and reversing axis direction - MATLAB Answers
Hello, I want to plot a graph with one x axis and two y axes. I want one of the y axes to...
Read more >Axis Ranging - AutoRange and VisibleRange - SciChart
Axis AutoRanging The AxisCore.AutoRange property defines how the axis autoranges when data is added.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m not sure this is just “a bug to be fixed” - the autorange operation never reverses the axis direction, so currently setting
ax.autorange: true
whenax.range = [bigger, smaller]
will give you a reversed range.In principle it would be nice to have
ax.autorange = 'reversed'
be a real setting, and the on-graph interactions look at the existing range to determine whether to settrue
or'reversed'
. But that would be a breaking change for anyone currently sending inautorange: true
with a reversed dummy range - currently the “official” way to get a reversed autorange from the beginning.Discussed out loud 😃