yaxis.autorange === true unexpected behavior since 3.0
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 18.3k
- Forks
- 2k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 28
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked graph reproduction and compare the behavior between Plotly 3.0 and 3.0.1. Trace the plotly_animated event followed by the Plotly.relayout call, focusing on why yaxis.autorange remains true without adjusting when switching from PS to cumulative. Done means the y-axis updates correctly after that swap or the migration requirement is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100