smart defaults for funnel and image traces are not applied when restyling or reacting from trace with visible false
See original GitHub issueBoth pen are bare minimum for bug reproduction.
Funnel Defualt Behaviour: Pen: https://codepen.io/mafar/pen/rNNYeLX?editors=0010 initialised with default options => Observe Funnel Direction
Funnel updated with Plotly.restyle:
Pen: https://codepen.io/mafar/pen/YzzEqqN?editors=0010
initialised with empty x,y options and then x,y are updated with Plotly.restyle
=> Observe Funnel Direction
Image:
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Solved: Frustrations with Image Trace - 10251280
I'm currently doing default tracing tests in both 2019 and CS5 with one of them. I'll zip the psd file and the default...
Read more >cyrus-imapd bug fix and enhancement update
Annocheck: Do not complain about missing -mbranch-protection option in AArch64 binaries if compiled in LTO mode. - gcc-plugin: Add support for CLVC_INTEGER ...
Read more >Untitled
Los suziox fallas de origen, Islanders current lines, Enlarge image photoshop action ... Non-blood, Sillenite wiki, Ceca udace se suze moje, Working refuge, ......
Read more >Untitled
#cadaver How to trade binary options, Caifanes no dejes que hd, French literature in ... Tv diagram tcl, Turps corner grays, Tracing number...
Read more >CRFM Benchmarking
[substeps] Traditional semi-permanent dyes will generally not be ... [substeps] A non-alcohol toner can also be used after washing to remove traces of ......
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
This bug is a side-effect of our input
range
andautorange
mutations:https://github.com/plotly/plotly.js/blob/1a3d38339dc7c9b5594f94a1b1f3625f3854d2ac/src/plots/cartesian/autorange.js#L255-L256
With this piece of logic:
https://github.com/plotly/plotly.js/blob/1a3d38339dc7c9b5594f94a1b1f3625f3854d2ac/src/plots/cartesian/axis_defaults.js#L56-L62
after the first plot call (the one with empty
x
andy
coordinates), we have:On the second react/update call, we get
That is,
yaxis.autorange
gets coerced totrue
(not'reversed'
astrue
got mutated in the user layout) leading a yaxis range of[3.5, 0.5]
.So, adding
before the second react/update call is enough to work around this bug. Example: https://codepen.io/etpinard/pen/MWWxKLv?editors=0010
works . can we request an official fix please