From efbba44749ac46d6ea6b2ea5ae136b284ae5b8cd Mon Sep 17 00:00:00 2001 From: BREW <81044362+b-re-w@users.noreply.github.com> Date: Tue, 10 Nov 2026 05:31:06 +0900 Subject: [PATCH] Fix: Lay the page area out again when the appbar folds or shows 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 --- rivet/runtime/windows/src/frame.rs | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/rivet/runtime/windows/src/frame.rs b/rivet/runtime/windows/src/frame.rs index 22c6e35..e638ddf 100644 --- a/rivet/runtime/windows/src/frame.rs +++ b/rivet/runtime/windows/src/frame.rs @@ -2029,6 +2029,11 @@ unsafe fn relayout(window: HWND) { // The frame view lays out again on request, which also works for a maximized window. crate::features::vertical_tabs::invalidate_strip(window); if frame_layout::relayout(window) { + // The frame view lays its client view out again only when the client view's bounds + // change, and a new appbar width can leave them as they were while the page area must + // move. The browser view lays its page area out again here, as on Brave and Whale it + // otherwise waits for the next input. + crate::hooks::page_area::relayout(window); if is_waiting(window) { crate::trace::trace("attach: asked the frame view to lay out again"); }