Migrate to Bootstrap 5.3 and resolve modal/popover/tooltip lifecycle bug

[malberts]

Closes #38.
Fixes #68.

Summary

Upgrades BootstrapComponents from Bootstrap 4 to Bootstrap 5.3, at functional parity with the last released BS4-era BC (5.2.2) and additionally resolves the upstream "Modal/Popover/Tooltip stop working under MediaWiki 1.43+" bug.

This branch was informed by the earlier WIP exploration in #69 (now closed as superseded); it is a clean, self-contained set of nine commits.

What changed

Nine self-contained commits:

1. Migrate BootstrapComponents to Bootstrap 5.3 — the BS4 → 5.3 emission changes (data-toggle → data-bs-toggle family, .btn-default → .btn-secondary mapping for color="default", .close → .btn-close, .badge-pill → .rounded-pill, jumbotron utility-class reimplementation per the BS5 migration guide, vanilla-JS rewrites of carousel/popover/tooltip). Floor versions bumped to MW ≥ 1.43, PHP ≥ 8.1, mediawiki/bootstrap: ^6.0.
2. Run CI on more versions of MediaWiki and PHP — CI matrix updated to MW 1.43–1.45 + master, PHP 8.1–8.5.
3. Modernise namespaced class imports — use \Html etc. replaced with use MediaWiki\…\X across the codebase (required-ish at the MW 1.43 floor).
4. Update tests for Bootstrap 5 output — PHPUnit expectations updated to match the BS5 emitted markup.
5. Fix DOMContentLoading typo in tooltip JS initialiser — 'DOMContentLoading' (which is not an event) is now 'DOMContentLoaded'.
6. Resolve upstream Tooltip, Popover and Modal stop working after a cache purge on MW 1.43.3 #68 by emitting modal markup inline — the architectural fix; see below.
7. Emit Bootstrap 5 text-bg-<color> for badges — BS5 removed the .badge-<color> family; replaced with .text-bg-<color>. color="default" maps to text-bg-secondary for backward-compat (matches Button/Modal/Popover behaviour).
8. Update tests to match inline modal emission — ModalTest, ImageModalTest, ModalBuilderTest, OutputPageParserOutputTest contract changes.
9. docs: update component references for Bootstrap 5 — every external https://getbootstrap.com/docs/4.1/ link bumped to /docs/5.3/; jumbotron deprecation banner; color="default" mapping noted in the relevant component docs; known-issues.md updated with the Tooltip, Popover and Modal stop working after a cache purge on MW 1.43.3 #68 resolution note; release-notes 6.0 entry expanded.

Resolves upstream issue #68

PR #69 noted "Modal does not trigger" / "Popover does not trigger" as a TODO. Investigation showed it is the same bug as the open issue #68 ("Tooltip, Popover and Modal stop working after a cache purge on MW 1.43.3").

Root cause: BC's ModalBuilder::parse() stashed the modal markup via ParserOutputHelper::injectLater() → $parserOutput->setExtensionData(DEFERRED_CONTENT_KEY, …), and OutputPageParserOutput::process() retrieved it via the same key at render time. Diagnostic instrumentation under MW 1.43.8 showed the parse-time and render-time ParserOutput instances are different objects (spl_object_id differs); the deferred-content data set on the parse-time object never reaches the render-time hook. Effect: trigger renders, modal container does not, click does nothing.

The defensive design rationale for the deferred-injection pattern no longer applies under modern MediaWiki + Bootstrap 5 — MW 1.40+ uses RemexHtml which auto-closes the enclosing inline element rather than mangling block-in-inline, and BS5 modals use position: fixed plus an ID-resolving data-bs-target attribute so DOM placement is no longer significant.

Refactor: emit the modal markup inline as a sibling of its trigger button. Per-component JS init modules (the BS5 vanilla-JS replacements for the dropped jQuery plugins) are loaded via OutputPage::addModules() from the OutputPageParserOutput hook (which works reliably; OutputPage is the persistent object). A new ext.bootstrapComponents.modal.js module explicitly instantiates bootstrap.Modal on each .modal element, since BS5 dropped the BS4 jQuery-driven autoinit.

The same patch was applied workspace-only against BC 5.2.2 to confirm: with this commit, modal markup renders on MW 1.43+ even without the BS5 migration. So the fix would also help users still on BC 5.2.x if backported.

Verification

• 4-stack harness (Chameleon-BS4 / Chameleon-BS5 / Medik-BS4 / Medik-BS5 on MW 1.43.8): every parser function renders correctly on every stack; HTTP 200; no PHP errors; zero unparsed parser-function tokens.
• Comprehensive per-attribute matrix (~75 attribute permutations: 8 colors × every component, all sizes, all placements/triggers for popover/tooltip, outline/pill/active/disabled variants, custom-class/style passthrough): no functional regressions on any stack.
• Functional triggering verified via Playwright on the BS5 candidate stacks: modal data-bs-toggle click opens the modal (with backdrop, .modal.fade.show); popover and tooltip JS instances attach; dismissible alert .btn-close closes the alert.
• PHPUnit: 96 of BC's Unit/ tests pass (everything except LuaLibrary*Test.php which require Scribunto in the test environment).

Component deprecations (BS5)

• bootstrap_jumbotron — BS5 removed the .jumbotron class (migration guide entry). The parser function is retained and now emits the BS5 utility-class approximation per the migration guide (p-5 mb-4 bg-body-tertiary rounded-3). The deprecation is called out in docs/components/jumbotron.md and docs/components.md; the parser function may be removed in a future major release.

Notes for users

• mediawiki/bootstrap constraint pins to ^6.0 (the released BS5.3-bearing major). Anyone on the previous ^5.0 is on a BS4 stack and should stay on BC 5.x until ready to upgrade their wiki to MW 1.43+ + the new Bootstrap extension major.
• Most existing wiki markup using BC parser functions / tag extensions continues to work without changes. color="default" automatically maps to btn-secondary (button/modal/popover/badge).

Out of scope

• Adding new BS5-only components (bootstrap_offcanvas, bootstrap_spinner, bootstrap_toast) — separate enhancement.
• Audit of BC's *.vector-fix.css modules for continued necessity under BS5 — separate follow-up.
• Migrating MWException to typed exceptions — latent debt, separate follow-up.

🤖 Generated with Claude Code

[malberts]

Visual evidence

Captured on the 4-stack visual-regression harness (MediaWiki 1.43.8). Wikitext source for both pages is in the PR's findings / available on request.

1. Modal click actually opens on the BS5 candidate (closes #68)

<bootstrap_modal text="Open the modal" header="Modal Title" footer="Footer text">…</bootstrap_modal> on :8432 (Chameleon + BS5 candidate). Click on the trigger; modal renders with backdrop, dialog, header/body/footer; .modal.fade.show + .modal-backdrop both present in DOM.

2. Comprehensive per-attribute matrix — Chameleon BS4 baseline vs BS5 candidate

BCTestMatrix page (~75 attribute permutations: 8 colours × every component, all sizes, all popover/tooltip placements & triggers, outline/pill/active/disabled variants, custom-class/style passthrough). Full-page screenshots, same wikitext on both stacks.

Chameleon BS4 baseline (:8431):

Chameleon BS5 candidate (:8432):

Visible differences are exactly the accepted BS5 style-trend evolution (brighter primary blue / cyan, slightly larger border-radius, lighter bg-body-tertiary jumbotron, BS5 SVG-style × close buttons). The color="default" button + modal trigger render as a properly-styled btn-secondary on BS5 where they were unstyled plain text on BS4 (BS4 4.6+ has no .btn-default).

3. Cross-skin parity — Medik BS5 candidate

Same BCTestMatrix on :8434 (Medik master, BS5 lib 5.3.8). BC renders identically to the Chameleon-BS5 stack — confirms BC isn't skin-coupled and the migration works for every BS5-aware skin.