-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
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
Expounding on "opt-in for performance reasons" #29378
Comments
Hi @jonathanhefner, there is a way to do that, you can use our |
Bumping @twbs/js-review on this—would we want to make this the default in v5? Is that a breaking change that we'd need to punt to v6? |
TBH we need some kind of benchmark before everything else. The reasons behind this choice may no longer apply to v5, but it can indeed be a breaking change. |
Follow up / tangential to this as a user of bootstrap:
|
I agree with @XhmikosR on needing to re-evaluate this. @twbs/js-review Can any of you review and make a suggestion for how to better handle tooltips and popovers here without requiring extra work? |
In the documentation for both Tooltips and Popovers is the caveat: "opt-in for performance reasons, so you must initialize them yourself." But I'm having trouble finding a detailed explanation of "performance reasons." The caveat is at least 6 years old, which makes me wonder if it's still true.
Also, many people miss this caveat when reading the documentation, for example #24985 and #15458. So it would be great if Tooltips and Popovers could actually be automatically initialized in a performant way. That might also pair nicely with using
MutationObserver
to automatically remove Tooltips in v5.The text was updated successfully, but these errors were encountered: