Skip to content

fix: keep readiness finding verbs inside the pane - #2127

Merged
AnsoCode merged 2 commits into
mainfrom
fix/readiness-findings-verbs
Oct 16, 2026
Merged

AnsoCode merged 2 commits into
mainfrom
fix/readiness-findings-verbs

Conversation

@AnsoCode

@AnsoCode AnsoCode commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • On a 1280-wide window the Fleet Readiness findings table was wider than its pane, so the resolving verb (Capture recovery point, Start stack, and the rest) sat past a horizontal scroll.
  • Until the window is wide enough for every column, Stack and Domain are named on the finding, and Node, State, and Action take a share of the pane so the verb and Dismiss stay visible.
  • On a wide window, Stack and Domain return as their own columns.

Test plan

  • Open Fleet, then Readiness, at 1280. Confirm the verb and Dismiss are on screen with no horizontal scroll.
  • Widen the window until Stack and Domain reappear, and confirm the verbs still fit.
  • Narrow the desktop pane with the sidebar open and confirm the verbs stay in the pane.
  • Frontend typecheck is clean, and the readiness findings tests pass (66).

The findings table was wider than the fleet pane, so the resolving verb sat past a horizontal scroll. Size the columns as a share of the pane until there is room for stack and domain.
Brings the image gate fix (the source-built Compose plugin no longer
links a vulnerable containerd) so this branch's image build and preview
publish can pass.
@AnsoCode
AnsoCode merged commit 6da06ce into main Oct 16, 2026
20 checks passed
@AnsoCode
AnsoCode deleted the fix/readiness-findings-verbs branch October 16, 2026 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant