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
some replies had mentioned to just 'filter' the data using relayout event but i'm not sure how this can be done with those range values or how that will impact the range slider 'sub chart' image if you end up 'filtering' and removing the rest of the bars.
i'm not sure if this is a bug, maybe caused by me missing property in my config, a wip feature in the plotly library that plotly is trying to add or autorange is working as intended.
i'm working with angular 16 and "angular-plotly.js": "^5.2.2", "plotly.js-dist-min": "^2.27.1",
The text was updated successfully, but these errors were encountered:
There was an older issue posting related to this that hasn't had any activity and after checking the plotlyjs issue page, i am confused as I cannot tell if autorange is behaving as i am understanding it.
e.g.:
https://community.plotly.com/t/plotly-autorescaling-y-axis-range-when-range-slider-used/73970
https://codepen.io/niwsa/details/BXBjQQ
https://community.plotly.com/t/update-y-axis-domain-when-zoomed-on-x-axis/2073
plotly/plotly.R#912
plotly/plotly.js#1876
some replies had mentioned to just 'filter' the data using relayout event but i'm not sure how this can be done with those range values or how that will impact the range slider 'sub chart' image if you end up 'filtering' and removing the rest of the bars.
in my https://stackblitz.com/~/github.com/ysk3a/angular16plotly , if you slide the range to show the smaller bars, the y-axis does not 'auto range' for the bars to be visible.
i'm not sure if this is a bug, maybe caused by me missing property in my config, a wip feature in the plotly library that plotly is trying to add or autorange is working as intended.
i'm working with angular 16 and "angular-plotly.js": "^5.2.2", "plotly.js-dist-min": "^2.27.1",
The text was updated successfully, but these errors were encountered: