-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Tooltip: disable autoHide doesn't with positionLeft property #14714
Comments
Hi, A word from PrimeNG team here is necessary IMO as autoHide:false only prevent tooltip deactivation when the cursor immediately leave the bound field or element to the tooltip container (since by default the arrow/tooltip is stuck to the bound element). Is it okay for this feature to still work even if there is a 100px gap between the two ? |
good point. But what about tooltip with some action btns? For example I am going to add a button to the tooltip |
If you need to put some dynamic content like component, either stick your tooltip to your target or maybe OverlayPanel is more what you need rather than Tooltip. Also not sure if a button inside a tooltip is a good pattern/user experience (but who am i to judge) |
Hi, So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap? Thanks a lot for your understanding! |
Describe the bug
Tooltip: disable autoHide doesn't work with positionLeft property
https://stackblitz.com/edit/wszuks?file=src%2Fapp%2Fdemo%2Ftooltip-auto-hide-demo.html
Environment
Angular project
Reproducer
https://stackblitz.com/edit/wszuks?file=src%2Fapp%2Fdemo%2Ftooltip-auto-hide-demo.html
Angular version
16
PrimeNG version
16.9.1
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18.18
Browser(s)
Chrome
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: