Chrome 156 just reached Googlebook through the Play Store, about a week later than Google’s usual two-week cadence. It doesn’t carry a single headline feature like Chrome 155’s website-as-app install, but it fixes a handful of things that have been quietly annoying since launch, starting with where your downloads actually go.
What’s actually new in Chrome 156
The biggest practical change is a proper “Save As” dialog. Instead of every download landing wherever Chrome last decided, you can now pick a destination folder and rename the file before it saves. Google is rolling it out gradually, but you can force it on right now through chrome://flags#enable-download-save-as-system-file-dialog. The update also quietly fixes a bug where repeat downloads of the same filename got a duplicate number stuck after the file extension instead of before it.
Google Docs gets a real fix too. Copying a big table, a large image, or a chunk of rich text used to throw a clipboard error on Googlebook. Chrome 156 offloads large clipboard payloads instead of choking on them, so that error should be gone.
A few crashes are patched: the 1Password extension no longer crashes when paired with a third-party autofill service in Chrome 156.0.8078.47, uninstalling Teleparty won’t take Chrome down with it, and a specific tab-dragging window management case is fixed. Keyboard behavior got two small but welcome tweaks worth adding to your shortcut list: Alt+Tab now switches windows even in fullscreen keyboard-lock mode, unless the site you’re on specifically requests system modifier capture, and Alt+Shift+Enter opens a link in a background tab. The address bar also stopped showing its autocomplete dropdown over multi-line input, so arrow keys move your cursor between lines like they should.
The rest is cleanup: a working close button on “Sign in with…” prompts from sites like Reddit, Canva, Pinterest, and the New York Times, smoother Facebook Live buffering, working right-click menus on the Incognito new tab page, favicons that reappear properly after you clear the address bar with Esc, and some polish on the AI Mode menu.
Why this one showed up late, and what’s still missing
Chrome moved to a two-week release cycle back in September, so a one-week delay is worth noting even if it’s minor. It’s also a reminder that Googlebook runs its own Chrome build, separate from classic ChromeOS devices, so an update like this doesn’t automatically mean anything for a Chromebook sitting next to it.
Google has flagged three bigger gaps it’s still working on: multiple Chrome profiles, which has been the most requested feature from longtime Chrome users; tab group syncing across windows and devices; and automatic Cast device discovery in Chrome’s Cast menu, which currently requires a manual workaround. None of the three shipped in 156, but Google says fixes for all of them are in development for upcoming bi-weekly releases.
What Googlebook owners should do
Check the Play Store for the Chrome 156 update if you haven’t gotten it yet. If you’re tired of downloads landing in the wrong place, flip on the Save As flag now rather than waiting for the gradual rollout to reach you. And if Casting has been refusing to find your TV or speaker, go to Settings, then Apps, then Chrome, then Permissions, and grant access to Nearby devices or Local Network. That’s the workaround until automatic discovery actually ships.
None of this changes anything for a regular Chromebook running classic ChromeOS. If you’re still deciding whether a Googlebook upgrade is even worth it, that’s a separate question with its own answer.
