Published November 19, 2026

Chrome 157 Arrives on Googlebook With Vertical Tab Fixes and a Native Save Dialog

When Chrome 157 started appearing on Googlebooks on November 11, it looked like a maintenance release. Google had not published release notes, the version number moved quietly, and the reasonable assumption was a handful of security patches on the way to Chrome 158. Then the paperwork caught up.

The official changelog for 157.0.8103.38 turned out to contain a decent block of desktop polish, and for anyone shipping a Flutter web build to a Googlebook, three of the changes are worth reading before the next release.

Vertical tabs stopped fighting the user

Collapsed vertical tabs now expand on hover as an overlay. Rest the cursor on the rail, read the full tab titles, manage a group, move away, and the rail tucks back in. Teams that prefer the old behaviour can switch it off in Settings, Appearance, Tab position, or by right-clicking the rail.

The second half of that change is the one with layout consequences. Once auto-expand is off, the vertical tab bar can be resized manually, and Chrome remembers the width across restarts and new windows. Window width is no longer a fixed quantity on a Googlebook display, which matters for anything that renders to the viewport.

A Flutter web app that switches layout at a breakpoint should treat the published rail width as user state rather than a constant. If your app measures the window on first frame and caches the result, an expanded rail produces a narrower viewport that it will never notice.

The rest of the desktop list reads like a set of things that should have shipped at launch: settings subpages now have real URLs such as chrome://settings/appearance that can be bookmarked and walked back with the Back and Forward buttons, a persistent bar appears at the top of the window when a tab is shared in a call so sharing can be stopped or switched in one click, and the native system file picker is now the default for right-click Save As instead of a flag buried in chrome://flags.

That last one changes download behaviour for web apps. Saving a generated PDF from a Flutter web build now opens the operating system dialog by default, which is better for users and different enough from the old silent download that any in-app instructions need a refresh.

Twenty-four fixes, and one API worth planning for

The changelog lists two dozen targeted fixes, most of them aimed at small frictions that accumulated since Googlebook OS launched.

  • Right-click menus on the bookmarks bar respond again.
  • The bookmarks bar no longer vanishes when switching tabs in fullscreen with vertical tabs enabled.
  • Google Slides can pick an external monitor for presenter view.
  • Crashes tied to extension messaging and unregistered keyboard shortcuts are gone.
  • Ctrl + L highlights the full URL, and downloaded PDFs open in a new tab instead of an external viewer.

Google also confirmed three features in the pipeline. On-startup behaviour will let users choose between the homepage, restoring the previous session, or a fixed set of pages. An "ask where to save files" toggle is being wired into Settings, Downloads for ordinary left-click downloads. And the EyeDropper colour picker API is live in Chrome Beta by default, which lets web apps such as Figma and Canva sample colours from anywhere on screen.

EyeDropper is the one to watch if you build design tools in Flutter. It is reachable from Dart through JavaScript interop, and it removes the last common reason a colour workflow needs a native companion app. Testing it now, behind a capability check, costs an afternoon. Discovering it in a competitor's release notes costs more.

Googlebook OS is still a moving target, and each of these releases narrows the gap between a browser that happens to run on a laptop and a browser built for one. Flutter web teams get the benefit for free, provided they stop assuming the window is a fixed size and the download dialog is invisible.