You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] imperativeModeOnly not working as expected #1226
Originally posted by GabrielMAraujo September 6, 2024
Hi,
I've been trying to do a custom implementation of the tooltip that requires me to open and close the tooltip programmatically, and it also must not close the tooltip when the mouse hovers out the anchor div.
I read in the docs that the imperativeModeOnly prop should suffice in this case, but I tried to use it and it seems like it's not working.
I ran into a similar problem but I also have clickable=true because of the inclusion of buttons in the tooltip content. A workaround for me was settting an openEvents prop to true to prevent the tip from automatically dismissing on a mouseleave event.
openEvents={{
dblclick: true,
}}
I believe the problem could be attributed to this code here:
I ran into a similar problem but I also have clickable=true because of the inclusion of buttons in the tooltip content. A workaround for me was settting an openEvents prop to true to prevent the tip from automatically dismissing on a mouseleave event.
openEvents={{
dblclick: true,
}}
I believe the problem could be attributed to this code here:
Activity
alsoknownasfoo commentedon Nov 1, 2024
I ran into a similar problem but I also have clickable=true because of the inclusion of buttons in the tooltip content. A workaround for me was settting an openEvents prop to true to prevent the tip from automatically dismissing on a mouseleave event.
I believe the problem could be attributed to this code here:
react-tooltip/src/components/Tooltip/Tooltip.tsx
Lines 584 to 589 in 08bfc6f
Does the line need to consider imperative mode as well?
MadWagon commentedon Dec 24, 2024
Thanks for the clever workaround !
github-actions commentedon Mar 25, 2025
This issue is stale because it has not seen activity in 30 days. Remove the
stalelabel or comment within 14 days, or it will be closed.gabrieljablonski commentedon Apr 8, 2025
Sorry for the long delay.
This has been fixed in v5.28.1