[feat] Expanded tooltips: nested keyword inspection system

[ScottyVenable]

Summary

Track a follow-up feature for expanded tooltips: a nested keyword inspection system inspired by Paradox / Victoria III-style tooltip locking.

Desired behavior

• Hover keywords in UI text to show a contextual tooltip.
• Keep a tooltip lockable when the pointer moves into it, so the player can inspect it instead of losing it immediately.
• Allow keywords inside a tooltip to open secondary tooltip panels in a readable stack.
• Support keyboard focus for opening, pinning, moving between, and closing tooltip panels.
• Support mobile through long-press or tap-to-pin behavior, with clear dismissal.

Data model ideas

• Keyword registry keyed by stable ids for goods, factions, crew traits, ship modules, market modifiers, and glossary concepts.
• Rich text tokens that render plain text plus keyword spans without unsafe HTML injection.
• Tooltip panel stack that tracks origin element, parent panel, pinned state, and focus target.
• Glossary entries for authored descriptions and generated stat summaries.

Accessibility needs

• Focus trap for pinned tooltip panels when they behave like temporary dialogs.
• Esc closes the active pinned panel, then unwinds the panel stack.
• Use aria-describedby for simple hover/focus tooltips and dialog roles where panels become interactive.
• Preserve readable contrast, keyboard order, and touch targets at mobile widths.

Future usage examples

• Goods: legality, bulk, supply, demand, and average price context.
• Factions and civilisations: reputation, region, and station ownership context.
• Crew traits: stat effects, stress interactions, and hiring risk.
• Ship modules: installation effects, slot pressure, and maintenance hooks.
• Market modifiers: news events, station kind effects, and route risk.

Related follow-up ideas

• Helm map improvements can ride beside this work as linked UX follow-ups: click-drag panning, route particles, animated routes, and destination hover previews.

Scope note

This is not part of PR #101. It is tracked as a follow-up backlog feature.

Related to #101.

[ScottyVenable]

Example of extended tooltips in Victoria III from the image above.

---

I like the idea of setting keywords in a dictionary (perhaps), and color coating based on the type.

Things to Make Sure

• Tooltips shouldn't clip off screen.
• System might be different for mobile (due to layout constraints)
• Hovering over a keyword or component which allows the Expanded Tooltips
• We need to make sure we are implementing this right.
• The UI of other modules/themes should be used, it shouldn't look like a whole different UI.
• Clicking outside of the tooltip closes all tooltips opened that way
• Hovering over a keyword should be set in a number of seconds (2 seconds default?)
• A radial progress bar should appear at the top righthand corner of the tooltip opened by another tooltip to lock it in place. A lock icon (in the theme and style of the UI) should appear in it's place to show it is locked.
• When hovering out of an extended tooltip that was opened from another tooltip, if the mouse lands back at the first tooltip, the second one should close but the first one should remain open.
• To allow the mouse to move from the trigger to the tooltip without it disappearing, use a small leaveDelay (e.g., 300ms) or ensure the tooltip container is physically adjacent to the trigger in the DOM so the onMouseLeave doesn't fire immediately.
• The tooltip should "spawn" on the mouse, ancored to the top left of the tooltip. So when it spawns, the mouse is right ontop of the top left corner of the tooltip.

Google says the following about them:

"Extended tooltips in Victoria 3 are a foundational part of the user experience, designed to provide deep, nested information about mechanics, goods, and pop statistics without cluttering the screen."