Wrong calculation of min/max with annotation and `autorange: "reversed"`
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
Min/max with annotation and autorange: "reversed" is wrongly calculated and the annotation end up outside of the perimeter of the graph.
Intended
Wrongly
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 JSFiddle reproduction linked in the issue and inspect the min/max calculation path for annotations when autorange is set to "reversed". Confirm the current and intended screenshots, then verify that the annotation remains within the graph perimeter and that the reversed range is calculated correctly.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100