[BUG]: Return of #3619 - Issue with hovermode default logic for horizontal traces.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- data-visualization
Research direction
Start with the attached "Plotly.js Bug 3619 returns.html" reproduction and compare its behavior across the listed versions. Read issue #3619 and the fix in pull request #3646 for the earlier hovermode logic. Done means horizontal scatter and bar charts select the correct hovermode and mode-bar buttons, including hovermode 'y'.
Written by the indexing model from the issue text.
Description
I reported back in 2019 issue #3619 which was fixed in #3646 (v1.45.3) We have been using v1.47.4 until recently when we moved to v2.35.3 (latest at the time). I had to add v1hovermode to the mode bar to get the to hover/comparison buttons back but discovered that the issue with hovermode behaviour with horizontal scatter based charts has returned and also seems to affect bar charts too now:
The compare mode bar button behaviour is for 'x' axis rather than even when you set all the traces to horizontal (orientation of 'h').
If you set the traces as horizontal the Mode Bar and set the hovermode to 'y' the button is unselected (so is the closest button) even though the expected 'y' hovermode behaviour occurs when hovering.
I have grabbed my example page from #3619 and updated it by adding in v1hovermode and some more scatter chart variants. The first chart is still the stacked bar chart that now doesn't work anymore, the last is still the scatter chart with my workaround. The other three show the incorrect behaviour.
Plotly.js Bug 3619 returns.html
I tested it with various versions here are my results:
v1.58.4 (last v1.x.x) - Pass
v2.0.0 - Fail
v2.35.3 - Fail
v3.3.0 - Fail
- Dominant language
- JavaScript
- Stars
- 18.3k
- Forks
- 2k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 21
Getting set up
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.
More from plotly/plotly.js
-
chore P3 plotly-internal size: 3 task
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
chore P1 plotly-internal size: 1 task
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
chore P3 plotly-internal size: 1 task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
plotly/plotly.js#7648 · 3 comments ·
Maintainers usually reply within 1 day
-
bug infrastructure P2
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
All issues in plotly/plotly.js
Similar issues
-
factory-active factory-automatic harness/codex task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
vercel/ai#21582 · 3 comments ·
Maintainers usually reply within 1 day
-
ux
Difficulty 1/5 Under an hour Newbie friendliness 90/100
rr-djk/rr-djuikoo.com#53 ·
Maintainers usually reply within 1 day
-
new spec review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
w3c/browser-specs#2666 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
thim81/openapi-format#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
decentespresso/dye2#13 ·