-
Notifications
You must be signed in to change notification settings - Fork 715
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
Tooltip not reflecting x-axis on <BarStack />
components
#1876
Comments
I've managed to get to the root cause of this issue. It stems from the
So take the following
This works fine, because when you hover over "second" it corresponds to index
then "second" will reference index 1 in one data series, but return the "third" in the other as thats what index There is an obvious fix here to just fixup the data but I think that we could make the lib code a little bit more reliable by finding based on the I've updated my codesandbox with a little bit more context |
I've opened a PR for this issue, would be great to get some feedback on it |
Hi folks, would appreciate feedback on this PR as this issue is causing major frustration. Thanks |
Hi folks, following up on this, any update please? This is a major frustration for our customers so would be great to get it sorted ASAP |
Hi,
Seeing an issue with the tooltip in the
<XYChart />
and I'd love some help getting to the bottom of it. When hovering over a bar stack, it doesn't seem to be picking up the correctnearestDatum
meaning that whats displayed in the tooltip is not reflective of whats visible in the x-axis. There is also some strange behaviour arounddatumByKey
where by not all the data is listed, making it difficult to display accurate information in the tooltip. I've put together a codesandbox to recreate the issue outside of our application code.Thanks in advance for any help
Some examples:
Here I'm hovering over the 29th May, but
nearestDatum
is 5th June12th June partially showing showing 26th June's Data
Data missing from 26th June
More data missing from 10th July
The text was updated successfully, but these errors were encountered: