twbs/bootstrap

Expounding on "opt-in for performance reasons"

Open

#29,378 opened on 2019年9月6日

GitHub で見る
 (7 comments) (10 reactions) (0 assignees)MDX (174,240 stars) (78,904 forks)batch import
docshelp wantedjsv5v6

説明

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.

コントリビューターガイド

技術スタック
htmlcssjavascript
領域
documentationperformance
Issue 種別
documentation
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Basic understanding of BootstrapKnowledge of JavaScript initialization
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
75
調査方針
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.
Expounding on "opt-in for performance reasons" · twbs/bootstrap#29378 | Good First Issue