fix(tooltip): behavior of tooltip trigger with delay #1278
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 9596e14 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@tianenpang is attempting to deploy a commit to the NextUI Team on Vercel. A member of the Team first needs to authorize it. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1168
📝 Description
The tooltip should not open again after the delay is not reached and the cursor moves out.
⛳️ Current behavior (updates)
Fix the trigger behavior to prevent it from opening again after the delay is not reached and the cursor moves out.
🚀 New behavior
Use
triggerPropsinstead of custom on-pointer events, it already includes the correct pointer behavior.💣 Is this a breaking change (Yes/No):
No.
📝 Additional Information
Before
before.webm
After
after.webm