Animated popups can get stuck open if mouse enters then leaves very quickly

Open
#157 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
react, typescript
Domain
frontend

Research direction

No source file or test is named. First reproduce the provided Trigger example with the fade transition and rapid mouse movement, then trace the hover and leave behavior; done means the popup reliably closes after the pointer leaves, including during rapid entry and exit.

Written by the indexing model from the issue text.

Description

Pretty much what the title says. I'm on version 4.0.0-alpha.7. Given an element like this:

<Trigger
  action={["hover"]}
  popup={<span>Hello There</span>}
  popupTransitionName="fade"
  mouseLeaveDelay={0}
  popupAlign={{
    points: ["tc", "bc"],
    offset: [0, 3]
  }}
>
  <p>Test</p>
</Trigger>

And a style like the fade animation from rc-animate's examples. Or even something simple like this:

.rc-trigger-popup {
  display: inline-block;
  opacity: 1;
  transition: opacity 1s;
}

.rc-trigger-popup-hidden {
  display: none;
}

.fade-enter-active {
  opacity: 1 !important;
}

.fade-leave-active {
  opacity: 0;
}

For the most part the trigger/popup works normally. Hovering over the "Test" text creates the popup, which fades in, and then fades out when you stop hovering over the text. The issue comes up when you move your mouse quickly over the text. Sometimes it works normally, other times the popup gets stuck open even after the mouse has left. Increasing the mouseLeaveDelay seems to mitigate the problem, but that's not really a solution.

Dominant language
TypeScript
Stars
391
Forks
245
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react-component/trigger

All issues in react-component/trigger

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.