-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: Malfunction inside Links #5030
Comments
Cannot open the codesandbox demo. Could you update the link? |
Well, could you try this share link then, please? |
Do we have an update here? |
Thanks a lot, @vaibs30! We'll check before the next version release. Sorry for the delayed response! Best Regards, |
Hey I noticed this was supposed to be released in 3.47.0 recently but I'm not seeing it as fixed nor the changes in the published sources. Here's an updated sandbox link to
(notice there is no reference to the added See in browser via https://www.runpkg.com/[email protected]/utils/utils.js#368 |
Sorry for the confusion :/ There was confusion while merging from a different branch to master. I fixed it now. #5146 We will release the new version today. Thanks a lot for your report! |
No worries! Can confirm I'm seeing the fix in |
Describe the bug
There is a serious bug with Tooltip when it's used inside Links. When so, it causes the infinite recursion when trying to bind listeners using Tooltip's
bindScrollListener()
method resulting withUncaught RangeError: Maximum call stack size exceeded
. The problem lies inDomHandler.getScrollableParents()
utility that cannot properly read parent nodes. That's because in described case the condition checking parent for null in DomHandler's code below does not work (parent is undefined instead).Reproducer
https://codesandbox.io/p/sandbox/hungry-gagarin-nm9xwy
PrimeVue version
3.45.0
Vue version
3.x
Language
ALL
Build / Runtime
Vue CLI App
Browser(s)
No response
Steps to reproduce the behavior
Try the code in Sandbox and see the console.
Expected behavior
Tooltip should work w/o errors.
The text was updated successfully, but these errors were encountered: