test: Match GUI card walkthrough to responsive layout - #119
Draft
BenWestgate wants to merge 1 commit into
Draft
BenWestgate wants to merge 1 commit into
BenWestgate wants to merge 1 commit into
Conversation
The Tails field-test change in #77 lets card groups wrap according to available space, but the headless walkthrough and developer guide still required a fixed four-column layout. Verify reading order and actual wrapping at the clamped content width instead. Remove the resize assertion, which cannot reliably resize an already mapped window in this headless run. No GUI runtime behavior changes. Refs #72.
BenWestgate
added
area: gui
BenWestgate
commented
Oct 4, 2026
BenWestgate
left a comment
BenWestgate
left a comment
Owner
Author
There was a problem hiding this comment.
Codex current-head review at 892111a: no findings. The walkthrough now tests the responsive FlowBox invariant (reading order plus actual wrapping) instead of the obsolete fixed four-column layout, and the developer guide matches that behavior.
This was referenced Oct 4, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
PR #77 implemented issue #72: card groups remain in reading order and wrap when the available content width requires it. The Xvfb walkthrough and developer guide still asserted exactly four groups per row, so the current GUI stack reported two false layout failures. Update only those checks and the guide; no GUI runtime code changes.
The walkthrough now checks group order and actual wrapping within the 700px content clamp. It drops the headless window-resize assertion because resizing the mapped top-level window is not reliable in this Xvfb run. The Tails visual resize pass remains a separate human qualification.
Verification
Refs #72. Stack on #78. AI-assisted draft; human review and signed authorship are required before integration.