Skip to content
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] Tooltip shows briefly when using delayShow and moving to directly adjacent element #1162

Closed
viveleroi opened this issue Jan 26, 2024 · 3 comments · Fixed by #1168
Closed
Labels

Comments

@viveleroi
Copy link

It seems that when using delayShow and moving from one tooltip element to another that's immediately next to it, the "new" tooltip for the element you just moved to flashes for a second, hides, and then shows again after the time delay. Removing your mouse entirely and trying again works fine.

So it seems to be related to moving from one tooltip element to another.

    <Tooltip
      className={styles.tooltip}
      delayShow={1000}
      id='default'
      noArrow
      place='top-start'
    />
    
<span
  data-tooltip-content='This is a tooltip'
  data-tooltip-id='default'
  data-tooltip-variant='info'>test</span>
<span
  data-tooltip-content='This is a tooltip'
  data-tooltip-id='default'
  data-tooltip-variant='info'>test</span>
@viveleroi viveleroi added the Bug label Jan 26, 2024
@Carnageous
Copy link

Carnageous commented Feb 2, 2024

I was able to reproduce that issue while trying to debug another issue I am having with delay-show / delay-hide:

When you define a different show / hide delay on two elements and alternate hovering between them, the "show" delay from the previous element is applied, not the one from the currently hovering one.
https://stackblitz.com/edit/stackblitz-starters-dfebpx?file=src%2FApp.tsx

I`ll try to find the cause for this, but I would like to know if this is expected. Its not documented as far as I can see.

// Edit: Also, looks like this issue has been present since version 5.0.

@gabrieljablonski
Copy link
Member

[email protected] (from #1168) seems to fix both these issues.

Feel free to test it out until we are ready to release an official version.

@gabrieljablonski
Copy link
Member

Fixed on official release [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants