Skip to content

Fix: Lay the page area out again whether or not the frame view's layout is recorded - #191

Merged
b-re-w merged 1 commit into
developfrom
feat/relayout-all
Nov 9, 2026
Merged

b-re-w merged 1 commit into
developfrom
feat/relayout-all

Conversation

@b-re-w

@b-re-w b-re-w commented Nov 9, 2026

Copy link
Copy Markdown
Member

After #190, bar-folded passes on Chrome and Edge (.scratch\bar-rows-after3), and appbar-width, appbar-peek, split and sidebar pass on Chrome, Edge and Whale. Whale's bar-folded still fails. Its trace says "caption_layout: not in this build (frame view layout is not recorded for this build)", so frame_layout::relayout returns false and relayout takes the SWP_FRAMECHANGED path, which #190 did not touch. The page area relayout now runs first on every path. The bar-folded row is the test.

🤖 Generated with Claude Code

…ut is recorded

Whale records no frame view layout, so Rivet's relayout took the frame change path and the page
area stayed where it was after the appbar showed again. The browser view's page area is now laid
out first on every path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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