Skip to content
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

yaxis.autorange === true unexpected behavior since 3.0 #7377

Open
EliphasNUIT opened this issue Feb 24, 2025 · 1 comment
Open

yaxis.autorange === true unexpected behavior since 3.0 #7377

EliphasNUIT opened this issue Feb 24, 2025 · 1 comment
Labels
bug something broken P2 considered for next cycle regression this used to work

Comments

@EliphasNUIT
Copy link

Hello everyone,

Since updating to 3.0, we are observing a regression on the autorange option.
https://dps.report/jkgm-20250217-204224_ura
You can see there, on "Graph", when swapping from "PS" to "cumulative", the y axis does not properly adjust anymore, despite "autorange" on it being true.

The graph's update is triggered on a "plotly_animated" event and then Plotly.relayout API is called. I could not find anything in the documentation regarding if we were doing something wrong or if there was a migration effort to be had on that area when upgrading to 3.0.
Issue is still present on 3.0.1.

Thanks.

@gvwilson
Copy link
Contributor

Thanks for the bug report @EliphasNUIT - I'll see if I can get someone to look at it in the upcoming cycle.

@gvwilson gvwilson added bug something broken P2 considered for next cycle regression this used to work labels Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken P2 considered for next cycle regression this used to work
Projects
None yet
Development

No branches or pull requests

2 participants