fix(ui): a cut status line shows its whole text on hover

[Shman4ik]

What and why

Release-checklist finding 3 for 1.0.1. In a narrow window, a failed safe-mode commit showed only "Commit failed…", and the reason could not be read.

Cause, confirmed: the main status text has had ToolTip.Tip bound to the full message since the status bar was built, but the tooltip never opened. A TextBlock with no Background is not hit-testable in Avalonia. A headless scan found 0 of 4,536 points over the status text reaching the TextBlock; every one reached the statusBar border behind it.

Reproducing it live in the AOT build turned up a second cause: the server's error carries DETAIL: after a newline, so the status grew to two lines, each cut on its own ("Commit failed — no staged…", "DETAIL: Detail redacted…").

The same hit-test defect affected two more places:

• The bar's segment tooltips (why results are read-only, what "In transaction" means, what is staged) opened only when the pointer was exactly over an icon.
• The Activity, Database Overview and Security windows' status lines had no tooltip and no ellipsis at all.

Fix, one mechanism, no new control (UI rule 1): TextBlock.statusMessage in Styles/Theme.axaml. It is a single line (MaxLines=1), cut with an ellipsis, with a transparent background so it can be hovered. Its tooltip shows the whole text, every line of it, only while something is cut or left out: Converters/CutTextTip checks the block's TextLayout. The style is used by:

• the main status message and the cap warning;
• the Activity, Database Overview and Security windows' status lines.

Border.statusBar StackPanel also gets a transparent background, so the segment tooltips open over their text.

The Slow Queries status line keeps its wrapping: it is a paragraph of caveats (hidden statements, evictions) meant to be read, not a one-line status.

Visible to users (release notes)

A status line stays one line, and hovering it shows the whole message, including a server error's DETAIL. This applies to the main window and the Activity, Database Overview and Security windows. The tooltips on the status bar's "read-only", "In transaction" and staged-changes segments now open over their text.

Verified

• dotnet build: 0 warnings, 0 errors.

• Core tests against a live Postgres 17: 2039 total, 0 failed, 17 skipped. App tests: 736 total, 0 failed (the 14 tests gated on PGNIMBUS_TEST_CONN skipped in this final run; the live run before the one-line change passed 735 of 735).

• StatusLineTests moves the real pointer over each status line and segment. All 5 tests failed before the fix and pass now:

  • a cut message shows its text on hover;
  • a two-line message stays one line and shows both lines on hover;
  • a message that fits has no tooltip;
  • every status-bar segment that has a tooltip receives the pointer over its text;
  • the three windows' status lines are cut and show their text on hover.

  The only shortcut: the tooltip's 400 ms show delay is a dispatcher timer that the headless clock never advances, so the test sets the delay to 0. The hit test, pointer-over state and tooltip service are the real path, and the failures before the fix came from the hit test, not the delay.

• Live, in a NativeAOT win-x64 build (all four 1.0.1 fixes merged locally) against a local Postgres: a unique-violation commit failure in safe mode, narrow window, hover. The tooltip shows the whole message including DETAIL. (That run predates MaxLines=1; the one-line folding is covered by the headless test.)

• Screenshots: the transparent background draws nothing, and the scenarios' status lines fit, so no published image changes. update-published.sh was not run.

Checklist

• CLAUDE.md updated (UI rule 6), including the landmine: a background-less TextBlock or panel is not hit-testable.
• Anything general enough for kubeNimbus went into shared/nimbusUi: not done, on purpose, for a patch release. statusMessage and CutTextTip describe no Postgres concept, so they are candidates for nimbusUi. kubeNimbus's status bar probably has the same dead tooltip. Moving them means a subtree push and a paired kubeNimbus PR, so that is left as a follow-up.
• PgNimbus.Core untouched.

Follow-up spotted, not fixed here: about 25 more tooltip-bearing TextBlocks and panels have no background (history rows, schema tree details, the staged-conflict dialog, the Slow Queries headers). They are probably dead the same way.

🤖 Generated with Claude Code