-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Allow onMouseMove and onMouseLeave Events For Line Charts when Slice Tooltip is Enabled #1401
Comments
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
bump |
1 similar comment
bump |
bump |
1 similar comment
bump |
Is your feature request related to a problem? Please describe.
I'm synchronizing multiple charts on the same page using the technique described here: https://nivo.rocks/storybook/?path=/story/scatterplot--synchronizing-charts However, adding custom onMouseMove and onMouseLeave handles precludes using the out of the box slice tooltip. Each chart has two series, one for current values and one for target values. It would be nice to see both values in the tooltip, as it behaves when
enableSlices = 'x'
This scenario is similar requested in this comment, #47 (comment), but I felt it deserved it's own feature request given the number of upvotes that comment has.
Describe the solution you'd like
I would like to be able to supply
onMouseMove
andonMouseLeave
handlers whenenableSlices="x"
Describe alternatives you've considered
I'm exploring adding a custom tooltip but it is messier than the default x slice tooltip.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: