-
Notifications
You must be signed in to change notification settings - Fork 208
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
Feature request: disabled property #49
Comments
HI @raRaRa , Good remark. |
Great to hear! And excellent job, this is the only tooltip library that behaves and works like it should 🥇 I have a problem when I try to
|
let's me check |
Try to remove those deps from
Then excute this commande |
Still same issue :( I also tried removing yarn.lock among the steps you mentioned. |
Just got it.
|
Thanks, that did the trick. I have implemented the first version of the I also created a story for it. |
cool 👍 ,
Open a PR I will review it ASAP. |
Ah, will do! Are there any tests in the project where I can write a test case for it? |
Yeah of Course: https://github.com/yjose/reactjs-popup/blob/master/__test__/index.test.js you will notice that the build from your new PR was failed, it's related to Docs App just ignore it, I am migrating to gatsbyjs over react-static. |
Hi, please review my PR here: #50 |
Hey @yjose - any update on this? Thanks! |
Hi, this PR is in My Radar Now, I will merge it ASAP. |
Hi.
I want to suggest a new property for
<Popup />
which isdisabled
. I've run into an issue where I have a tooltip displayed when the mouse is hovering over a button, and when I click on the button I change the opacity of the button to0
. But unfortunately the tooltip will still show up, which is the expected behavior.That's why I want to suggest the new prop:
disabled
.When
disabled
is set as a prop for<Popup />
, then the tooltip will be removed if it's already displayed, and it won't show up when hovering over a disabled<Popup />
.I hope this gets implemented, and I could probably help out if there's interest.
Thanks!
The text was updated successfully, but these errors were encountered: