Skip to content

Fix: Lay the non-client view out from the browser view when the appbar changes width - #194

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

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

Conversation

@b-re-w

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

Copy link
Copy Markdown
Member

Whale's bar-folded still fails after #191 (.scratch\fold-whale-191). Whale has no recorded frame view layout, so #193's frame view parent is not available there. hooks::page_area::relayout now lays out the browser view's grandparent first: client view, then non-client view, through chromium::view::parent_of, which checks that the place is readable and the object's table lies in the module. Then it lays out the browser view as before. The bar-folded row is the test.

🤖 Generated with Claude Code

…r changes width

Whale records no frame view layout, so the non-client view above its browser view was never laid
out and the page stayed where it was after the appbar showed again. Rivet now finds it as the
browser view's grandparent and lays it out first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@b-re-w
b-re-w merged commit 2b28c97 into develop Nov 9, 2026
3 checks passed
@b-re-w
b-re-w deleted the feat/host-relayout branch November 9, 2026 20:58
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