Skip to content

fix(viewer): stop engine-mismatch warning stretching full-height on load#20

Merged
dutifulbob merged 1 commit into
mainfrom
fix/viewer-load-layout
Jul 6, 2026
Merged

fix(viewer): stop engine-mismatch warning stretching full-height on load#20
dutifulbob merged 1 commit into
mainfrom
fix/viewer-load-layout

Conversation

@dutifulbob

Copy link
Copy Markdown
Member

Opened on behalf of Onur Solmaz (osolmaz).

Summary

On first load the engine-mismatch warning banner briefly filled the whole screen before the tables settled.
Cause: .app used grid-template-rows: auto 1fr, but the warning is a third grid child, so it landed in the 1fr row and grid's default align-items: stretch blew the yellow banner up to full viewport height until the tab content loaded.

What Changed

CSS-only, in internal/viewer/web/src/styles.css (+ rebuilt web/dist).

  • .app: display: grid; grid-template-rows: auto 1frdisplay: flex; flex-direction: column, so children keep their natural height and nothing stretches.
  • .tabs-root: flex: 1 so the content area still grows to fill the viewport (preserving the original 1fr intent) instead of the warning doing so.

Testing

Rebuilt web/dist, go build ./cmd/localperf passes, viewer relaunched and verified: engine warning stays a compact banner, tabs/content fill correctly, prior width-cap and heat-fill styling intact.

Risks

Low — CSS-only, no logic change.

…on load

The .app grid used 'grid-template-rows: auto 1fr', but the engine-mismatch
warning is a third grid child — it landed in the 1fr row and, with grid's
default align-items: stretch, the banner filled the whole viewport height
during initial load before the tab content settled. Switch .app to a flex
column and let .tabs-root grow (flex: 1) so the warning stays auto-height
and the content area fills the space instead. Rebuilt web/dist.
@dutifulbob dutifulbob merged commit b2cb7a8 into main Jul 6, 2026
2 checks passed
@dutifulbob dutifulbob deleted the fix/viewer-load-layout branch July 6, 2026 15: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.

2 participants