Combining rangemode tozero and tickformat set to "," produces unexpected results
Open
Nobody has claimed this yet.
bug
P3
- Dominant language
- JavaScript
- Stars
- 18.3k
- Forks
- 2k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 28
Description
Hello, as described in the title, using a combination of these two parameters sometimes causes very unusual tick labels (xyz...e-17). Whether it happens or not depends on the data provided. Here is one example causing it.
const data = [
{
"x": [1],
"y": [-0.6],
"yaxis": "y"
}
];
const layout = {
"yaxis": {
"rangemode": "tozero",
"tickformat": ","
},
};
const graph = document.getElementById("graph")
Plotly.newPlot(graph, data, layout, {displaylogo: false});
The same issue happens if "rangemode": "tozero" is replaced with "range": [-0.7, 0]
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 by running the provided JavaScript example or opening the linked CodePen, using the data and y-axis settings from the issue. Trace how rangemode or the explicit range interacts with tickformat "," and verify that the resulting tick labels no longer show unexpected floating-point notation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100