Download 132.0.6834.159 from the Chrome Stable for Windows 64-bit

Google Chrome 132.0.6834.159 is available here as part of the Windows 64-bit Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.

Stable release date: January 14th, 2025

Unless otherwise noted, the following changes apply to Chrome 132 stable channel release for Android, ChromeOS, Linux, macOS, and Windows.

HTML and DOM

Throw exception for popovers and dialogs in non-active documents

Previously calling showPopover() or showModal() on a popover or dialog that resides within an inactive document would silently fail. No exception would be thrown, but as the document is inactive, no popover or dialog would be shown. As of Chrome 132, these situations now throw InvalidStateError.

Related technical references: ChromeStatus.com entry · Spec

Dialog toggle events

It's useful to know when <dialog> elements open and close, and popover already has ToggleEvent which is dispatched when a popover opens or closes. Previously, to detect when a <dialog> opens you had to register a mutation observer to check for open, however, this is quite a lot of work where an event would be easier.

This change incorporates the same ToggleEvent that popovers dispatch, but for <dialog> elements: when showModal or show is called, <dialog> dispatches a ToggleEvent with newState=open. When a <dialog> is closed (using the form, button, or closewatcher) it should dispatch a ToggleEvent with newState=closed.

Related technical references: ChromeStatus.com entry · Spec

Fix selection isCollapsed in Shadow DOM

Selection isCollapsed should return true if and only if the anchor and focus are the same. This should be true whether the selection starts or ends inside a light or a shadow tree.

Related technical references: Demo · ChromeStatus.com entry · Spec

CSS

CSS Anchor Positioning: allow anchor-size() in inset and margin properties

Originally, anchor-size() was only allowed in sizing properties. The specification was changed to allow anchor-size() in insets and margins as well.

Related technical references: ChromeStatus.com entry · Spec

CSS sideways writing modes

Support of sideways-rl and sideways-lr keywords for the writing-mode CSS property. sideways-rl and sideways-lr are helpful to write non-CJK text vertically. They don't have behaviors favorable for CJK languages unlike vertical-rl and vertical-lr.

Related technical references: MDN writing-mode · ChromeStatus.com entry · Spec

Loading

Fetch: Request.bytes() and Response.bytes()

Add a bytes() method to the Request and Response interfaces, which returns a promise that resolves with a Uint8Array. While Request and Response have an arrayBuffer() method, you can't read directly from a buffer. You have to create a view such as a Uint8Array to read it. The bytes() method improves the ergonomics of getting the body of Request and Response.

Baseline Newly Available: This feature is now available in all three major browser engines.

Related technical references: ChromeStatus.com entry · Spec

Ignore Strict-Transport-Security for localhost

Strict-Transport-Security (STS) response headers can cause problems for localhost web servers because STS applies host-wide, across all ports. This causes compatibility problems for web developers testing locally. It also affects end-users who use software packages that commonly start localhost web servers for ephemeral reasons. For example, communication of an auth token from a web login to a local software package. If one local listener sets Strict-Transport-Security on a localhost response, it's applied to all subsequent localhost requests regardless of port.

Chrome 132 resolves this problem by ignoring Strict-Transport-Security headers on responses from localhost URLs.

Related technical references: ChromeStatus.com entry

Media

Capture all screens

Capture all the screens connected to the device using getAllScreensMedia().

Calling getDisplayMedia() multiple times requires multiple user gestures, burdens the user with choosing the next screen each time, and does not guarantee to the app that all the screens were selected. The getAllScreensMedia() method improves on all of these fronts.

This feature is shipping on Desktop only.

Related technical references: Design Doc · ChromeStatus.com entry · Spec

Element Capture

Given a video MediaStreamTrack obtained through pre-existing means to initiate tab-capture, Element Capture allows mutating the track to only capture a subtree of the DOM starting at a given Element.

The API bears some resemblance to the Region Capture API, but affords greater flexibility for applications, because occluding and occluded content are both excluded from the capture.

Related technical references: Demo · ChromeStatus.com entry · Spec

Web APIs

PushMessageData::bytes()

The PushMessageData interface mimics the Body interface, which was amended earlier this year with a new bytes() method, following the principle that APIs should generally vend byte buffers as Uint8Arrays. Chrome 132 realigns with the Body interface by providing the bytes() accessor on the PushMessageData interface as well.

Baseline Newly Available: This feature is now available in all three major browser engines.

Related technical references: MDN PushMessageData: bytes() method · ChromeStatus.com entry · Spec

Keyboard focusable scroll containers

The rollout of this feature (from Chrome 130) was stopped due to an accessibility regression. This is fixed and the feature continues to roll out with Chrome 132.

Related technical references: Keyboard focusable scrollers · ChromeStatus.com entry · Spec

Device Posture API

This API helps developers to detect the current posture of a foldable device. The device posture is the physical position in which a device holds which may be derived from sensors in addition to the angle.

From enhancing the usability of a website by avoiding the area of a fold, to enabling innovative use cases for the web, knowing the posture of a device can help developers tailor their content to different devices.

Content can be consumed and browsed even when the device is not flat, in which case the developer might want to provide a different layout for it depending on the posture state in which the device is being used.

Related technical references: Git Repo · ChromeStatus.com entry · Spec

Saved queries in sharedStorage.selectURL

sharedStorage.selectURL() now allows queries to be saved and reused on a per-page basis, where the two per-page-load budgets are charged the first time a saved query is run but not for subsequent runs of the saved query during the same page-load. This is accomplished with a savedQuery parameter in the options for selectURL() that names the query.

Related technical references: ChromeStatus.com entry · Spec

Private State Token API Permissions Policy default allowlist wildcard

Access to the Private State Token API is gated by Permissions Policy features. Chrome 132 updates the default allowlist for both private-state-token-issuance and private-state-token-redemption features from self to * (wildcard).

Related technical references: ChromeStatus.com entry · Spec

FedCM Mode API and Use Other Account API

Two new extensions for FedCM:

• Mode: The active mode allows websites to call FedCM inside a button click (for example, clicking on a Sign-in to IdP button), which requires FedCM to guarantee it will always respond with a visible user interface. Calling the FedCM API in active mode takes users to login to the Identity Provider (IdP) when users are logged-out. Also, because the active mode is called within an explicit user gesture, the UI is also more prominent (for example, centered and modal) compared to the UI from the passive mode (which doesn't require a user gesture requirement and can be called on page load).
• Use Other Account: With this extension, an IdP can allow users to sign into other accounts.

Related technical references: Demo · ChromeStatus.com entry · Spec

File System Access for Android and WebView

This API enables developers to build powerful apps that interact with other (non-Web) apps on the user's device using the device's file system. After a user grants a web app access, this API allows the app to read or save changes directly to files and folders selected by the user. Beyond reading and writing files, this API provides the ability to open a directory and enumerate its contents, as well as store file and directory handles in IndexedDB to later regain access to the same content.

File System access shipped on Desktop in Chrome 86, with Chrome 132 it's available on Android and WebView.

Related technical references: The File System Access API · ChromeStatus.com entry · Spec

WebAuthn Signal API

Allows WebAuthn relying parties to signal information about existing credentials back to credential storage providers, so that incorrect or revoked credentials can be updated or removed from provider and system UI.

This page highlights the release changes most relevant to users. The official source below contains the full technical detail.

Official source: Chrome 132 Release Notes

Installation notes

After downloading the package, confirm that the branch and platform match your device before launching the installer or extracting the archive. If you only need a standard everyday browser, Stable is usually the safest choice. If you are testing new behavior, Beta, Dev, and Canary are better fits.

Related release pages

For newer or older builds in the same branch, open the category archive linked above. For different platforms, use the related desktop archives in the sidebar.