-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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
Bug: Passing Line Chart null value(s) hides entire 'label' tooltip #2875
Comments
@adamtLICOR I do not think this is intended behaviour. In my mind we should either eliminate the row represented by the |
@etimberg: Well, in my particular use-case, removing the row is desirable. This chart has four datasets -- when all four are present, the tooltip displays as normal. If a dataset has a null value, it just doesn't show it in the tooltip (or technically 'select' it from the hover state, but that's a moot point since it's invisible) If this is sufficient, I'll make another PR when I get the chance. My fix only works for |
I support removing the row. I think in most (>90%) of cases this is what users will expect. Please PR these changes 😄 |
How's the progress on this issue? |
There's a PR open for it right now, actually. Not sure what else (if anything) needs to be done |
@adamtLICOR @Regaddi merged the PR |
Is this one only solves line chart? I have same issue for bar chart with v2.3.0 |
In 1.0, if you passed multiple data-points to a Line Chart but included a null value, a
label
tooltip would still display if any other numeric data-point was hovered (simply removing the null data-point from the multi-tooltip).In 2.0, one or more null values hides the entire
label
tooltip, even if there are one or more numeric values and one of those data-points is hovered.I already have a fix for this on my local project (checking the meta data for the skip flag before adding an element to the returned
getElementsAtEvent()
array), but wanted to make sure this wasn't intended functionality before I made a PR.Thanks!
The text was updated successfully, but these errors were encountered: