-
-
Notifications
You must be signed in to change notification settings - Fork 32.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] Fix popper.js re-instantiation #19304
Conversation
Details of bundle changes.Comparing: d30e6bb...647462d
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for working on a fix. Could you add a test illustrating the issue?
@eps1lon Would an assert on the popper.js instance be enough? (testing the visual issue might be challenging) |
Could be, sure. I would have to see the test though to see what you mean. |
@eps1lon Here we go, let me know. |
952087a
to
2ac08ad
Compare
Closes #19203
This PR avoid the creation of a new Proper.js instance at each render.