Skip to content

Fix: Lay the page area out again when the appbar folds or shows - #190

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

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

Conversation

@b-re-w

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

Copy link
Copy Markdown
Member

After #189, release bar-folded passes on Chrome, Edge and Samsung but still fails on Brave and Whale (.scratch\bar-rows-after2). The capture after showing the appbar again shows the page still full width under the appbar, with the top bar over it. The trace has no "address bar: layout page" after "appbar: hidden false" on Brave. On folding, the browser view laid out only after the next click.

frame::relayout ran the frame view's LayoutImmediately. The frame view lays its client view out only when its bounds change, and the appbar's width does not change them. relayout now also calls hooks::page_area::relayout, the browser view's LayoutImmediately that the split relayout message already uses. That reaches toggling, width drags and attach retries alike. The bar-folded row is the test.

🤖 Generated with Claude Code

On Brave and Whale the frame view's layout left the browser view as it was when the appbar
showed again, so the page stayed under the appbar and the top bar with it until the next input.
Rivet's relayout now also lays the browser view's page area out.

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