Skip to content

test(web): witness the composer's bottom space and its clear top edge - #165

Merged
fxck merged 1 commit into
mainfrom
test/owner-layout-witnesses
Oct 10, 2026
Merged

fxck merged 1 commit into
mainfrom
test/owner-layout-witnesses

Conversation

@fxck

@fxck fxck commented Oct 10, 2026

Copy link
Copy Markdown
Member

Two geometry witnesses in the owner-reported layout regressions suite for the owner's 2026-10-09 composer reports (1786 x 1000, 435 px menu):

  • the conversation runs to the window's bottom and a recovery result arriving moves neither the composer nor the conversation: the docked footer ends at the window's bottom, the card sits one gutter above it, and the "accepted" then "Start failed." recovery toasts leave the card and conversation boxes unchanged (Show shell recovery results as toasts, not a strip in the page #152).
  • the conversation shows right up to the composer card's top edge: the two pixel rows above the card change when the conversation is hidden (The conversation runs right up to the docked composer #154/ci: make main's CI green and steady #161). This is a paint check because the footer is pointer-events-none, so elementFromPoint would skip the old opaque band too. The area below the card stays covered by "history does not paint through the composer footer".

Failed before: restoring the old strip, the footer ended at 960 instead of 1000, and a result arriving moved the card 4 px. Restoring the old bg-background footer, the strip above the card never changed. On main the suite file passes 3 of 3 runs, and gate-changed is green.

🤖 Generated with Claude Code

Two owner reports from 2026-10-09 get geometry witnesses in the
owner-reported layout regressions suite, at 1786 x 1000 with the 435 px menu:

- "the conversation runs to the window's bottom and a recovery result
  arriving moves neither the composer nor the conversation" (fixed by #152:
  recovery results became toasts instead of a strip under the main column).
  With nothing to report the docked footer ends at the window's bottom and the
  card sits one gutter above it; an "accepted" then a "Start failed." result
  leave the card and the conversation boxes unchanged.
- "the conversation shows right up to the composer card's top edge" (fixed by
  #154/#161: the dock is opaque only from the card's top edge down). Paint,
  not elementFromPoint: the footer is pointer-events-none, so hit-testing
  skips the old opaque band too. The two pixel rows above the card change when
  the conversation is hidden, stepping 5 px at a time until text passes.
  Nothing painting below the card stays with "history does not paint through
  the composer footer".

Failed before: with the old always-present "Recovery results" strip restored,
the footer ended at 960 instead of 1000, and with the quiet checks skipped a
result arriving moved the card 4 px (top 733 -> 729). With the old
`bg-background pt-1.5 sm:pt-2` footer, the strip above the card never changed
over 12 steps. On main both pass, 3 of 3 runs of the suite file (13 tests).
@fxck
fxck merged commit d27f8b6 into main Oct 10, 2026
20 checks passed
fxck added a commit that referenced this pull request Oct 10, 2026
- #165 test(web): witness the composer's bottom space and its clear top edge
- #163 Run-card oracle for the Mate engine, and the card defects it found
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