Chrome 159 beta landed on November 12, 2026, and it gives web developers about four weeks to test before the stable release. This update is not about one flashy API. Instead, it brings a set of CSS fixes, big WebTransport upgrades and a new way to prerender pages that contain cross-origin iframes.
In this guide, we cover what changed, which features matter for everyday sites, and how to test your project before the release reaches all users. As a result, you can spot problems early instead of fixing them in a hurry.

What Is Chrome 159 Beta?
Google promoted Chrome 159 to the Beta channel for Windows, Mac and Linux on November 12, 2026, as version 159.0.8154.6. The Android and iOS beta builds shipped on the same day. According to the Chrome 159 release notes on Chrome Platform Status, the stable release is scheduled for December 8, 2026.
The beta channel exists so that developers can try upcoming changes on real sites. In other words, anything you see in the Chrome 159 beta is likely to reach your visitors in December. However, Google can still adjust or delay individual features, so treat the list below as a preview rather than a promise.
If you followed our earlier coverage, this release continues the steady pace we saw with the Web Install API in Chrome 158 and HTML in Canvas in Chrome 157.
New CSS Features in Chrome 159 Beta
The CSS changes in this release are small, but they fix long-standing gaps between Chrome and the specifications. Most CSS changes in the Chrome 159 beta make Chrome behave the way the standards already describe.
AccentColor and AccentColorText Follow accent-color
The accent-color property lets you tint form controls such as checkboxes and radio buttons. Until now, the AccentColor and AccentColorText system colors only reflected the platform’s own accent color. In Chrome 159, they reflect the element’s effective accent-color value instead.
This means you can reuse your brand accent across custom components without repeating the hex value. For example:
:root {
accent-color: #f15a24;
}
.badge {
background: AccentColor;
color: AccentColorText;
}
As a result, your custom badges and buttons stay in sync with native form controls. This change aligns Chrome with the CSS Color Module Level 4 specification.
Background Layer Count and Other CSS Fixes
- Background layer count independence: the computed value of
background-*longhands now keeps the number of comma-separated values you wrote. Previously, Chrome repeated or trimmed them to match the number of background images. - CSSImportRule.styleSheet: this now returns
nullwhen an@importrule has no stylesheet, for example when itssupports()condition is false. Therefore, you can check for a stylesheet before reading its properties. - Scroll snap for single-axis containers: a container that scrolls in only one direction now handles snapping on that axis alone. The other axis passes to the nearest ancestor that scrolls in that direction.
For most sites, these fixes will not break anything. Still, if your scripts read computed background values, it is worth a quick check.
Prerendering Pages With Cross-Origin Iframes
This is one of the most practical changes for performance work. Chrome can already prerender pages through the Speculation Rules API. However, cross-origin iframes inside those pages were not prerendered, so embeds like videos, maps or payment widgets still loaded late.
With the Chrome 159 beta, a page can opt in to prerendering all of its cross-origin frames. To do so, the top-level document’s HTTP response must include this header:
Supports-Loading-Mode: prerender-cross-origin-frames
For WordPress sites, you could add this header through your server config or a small plugin. Before you enable it, though, check that your embeds do not run analytics or ads on load, because prerendered frames may load before a visitor actually arrives.
WebTransport Upgrades in Chrome 159 Beta
WebTransport is a modern API for low-latency, two-way communication over HTTP/3. It is useful for games, live video and real-time dashboards. The Chrome 159 beta adds several features from the WebTransport specification, so it is the biggest area of change.
- Congestion control option: you can request
"default","throughput"or"low-latency"behaviour per session. - Datagram readable byte streams: setting
datagramsReadableType: "bytes"enables BYOB (bring your own buffer) reading. - Datagram writable streams:
createWritable()returns independent writables withsendGroupandsendOrderfor prioritisation. - Send groups for streams: outgoing streams can join send groups and use
sendOrderto set priority, with sending statistics. - Receive stream stats: the new
WebTransportReceiveStreamhas agetStats()method with byte counters. - Keying material export:
exportKeyingMaterial()derives keys bound to the session. - Error alignment:
WebTransportErrornow matches the spec and can be structured-cloned.
Here is a short example that combines the new options:
const wt = new WebTransport("https://example.com:4433/live", {
congestionControl: "low-latency",
datagramsReadableType: "bytes"
});
await wt.ready;
console.log(wt.congestionControl);
const datagramWriter = wt.datagrams.createWritable().getWriter();
await datagramWriter.write(new Uint8Array([1, 2, 3]));
Note that WebTransport needs a server that supports HTTP/3. Therefore, test these options against a staging server first.
Other Notable Changes
- Sanitizer API: a new
javascriptURLsoption lets developers choose howjavascript:URLs are handled. Behaviour stays the same when you do not set it. - Speech recognition timestamps:
SpeechRecognitionResultgainsspeechStartTimeandspeechEndTime, which helps when you build synced captions. - MediaSession promises:
setMicrophoneActive()andsetCameraActive()now return a Promise. - Service worker errors: cancelled race-network-and-fetch-handler requests now reject with a distinct
TypeErrormessage. - Passkey Passive Mode origin trial: sites can test a sign-in suggestion that does not need a login form on the page.
How to Test Chrome 159 Beta on Your Site
Testing the Chrome 159 beta early takes less than an hour for most sites. First, follow these steps:
- Install Chrome Beta for your platform. It runs side by side with stable Chrome, so you do not lose your normal browser.
- Open
chrome://versionand confirm you are on version 159. - Load your key pages, such as the home page, checkout, sign-in and any page with custom form controls.
- Open DevTools and check the Console for new errors, especially around
@importrules and service workers. - If you use WebTransport or prerendering, test those flows on a staging server.
Next, compare the results with stable Chrome. If something breaks only in the beta, you have a few weeks to fix it before December 8. In addition, you can report real browser bugs through the Chromium issue tracker.
FAQ
When will Chrome 159 be released to stable?
Chrome Platform Status lists December 8, 2026 as the scheduled stable date. Google can still change this, so check the release notes before you plan around it.
Will Chrome 159 beta break my WordPress site?
Probably not. Most changes in the Chrome 159 beta align Chrome with existing standards. However, sites that read computed background values or depend on @import behaviour should run a quick test.
Do I need to change anything for AccentColor?
No. Existing code keeps working. The change simply lets you reuse your accent-color value through the AccentColor keyword.
Is the cross-origin iframe prerendering on by default?
No. It only works when the top-level page sends the Supports-Loading-Mode: prerender-cross-origin-frames response header.
Conclusion
Chrome 159 beta is a quiet but useful release. The CSS fixes make Chrome match the specs, the new prerendering header can speed up pages with embeds, and WebTransport gets a much fuller toolset. Meanwhile, the stable release is only a few weeks away.
So install the Chrome 159 beta today, test your most important pages, and fix any issues before December. If you also want to try fresh CSS ideas, our guide to the CSS random() function is a good next read.
Sources
Need Help With Your Website or Web App?
Swrice builds and customises WordPress sites, plugins and web apps. Whether you need an upgrade, a custom feature or a fix, our team can handle it for you.


Leave a Reply