twbs/bootstrap

Expounding on "opt-in for performance reasons"

Open

#29.378 aberto em 6 de set. de 2019

Ver no GitHub
 (7 comments) (10 reactions) (0 assignees)MDX (174.240 stars) (78.904 forks)batch import
docshelp wantedjsv5v6

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.

Guia do colaborador

Pilha de tecnologia
htmlcssjavascript
Domain
documentationperformance
Tipo Issue
documentation
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 hours
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
stale
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
clear
Prerequisites
Basic understanding of BootstrapKnowledge of JavaScript initialization
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
75
Direção de pesquisa
Examine the linked blame (https://github.com/twbs/bootstrap/blame/c6aae570b1bc608f5ca4b9ce9085ba9929edeb13/docs/javascript/tooltips.md#L37 L38) to understand the original performance context. Review issues #24985, #15458, and #28964 to see common user confusion and relevant discussions. Propose updated documentation that explains the performance trade offs clearly and possibly suggest automatic initialization using MutationObserver as discussed in #28964.