twbs/bootstrap

Expounding on "opt-in for performance reasons"

Open

#29,378 opened on Sep 6, 2019

View on GitHub
 (7 comments) (10 reactions) (0 assignees)MDX (78,904 forks)batch import
docshelp wantedjsv5v6

Repository metrics

Stars
 (174,240 stars)
PR merge metrics
 (Avg merge 6d 11h) (47 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate the performance trade offs of initializing Tooltips and Popovers automatically vs. opt in. Review the historical context from the 6 year old caveat and linked issues (#24985, #15458, #28964). Consider implementing a solution using MutationObserver for automatic initialization and removal.
Tech stack
javascriptcsshtml
Domain
frontend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65