Chrome 159 entered beta on 12 November 2026 and is scheduled for stable on 8 December 2026. Its CSS changes are small, spec-alignment fixes rather than flashy new properties, but small fixes are exactly the kind that change how existing pages render. Two of them are genuinely useful: the AccentColor system colours now follow your own accent-color, and scroll snapping finally behaves inside containers that only scroll in one direction.
This guide walks through the four CSS changes in Chrome 159 with examples and a test plan. Source: the official Chrome 159 release notes on Chrome Platform Status and the Chrome 159 beta announcement.
1. AccentColor and AccentColorText follow accent-color
accent-color lets you tint native form controls such as checkboxes, radios, range sliders and progress bars. CSS also has two system colour keywords, AccentColor and AccentColorText. Until now, Chrome mapped those keywords only to the platform’s system accent colour.
From Chrome 159, AccentColor and AccentColorText reflect the element’s effective accent-color value. This matches the CSS Color Module Level 4 specification. In practice, you can now style custom UI to match your native controls without repeating the colour.
:root {
accent-color: #7c3aed; /* brand purple */
}
/* Native controls use the brand colour */
input[type="checkbox"],
input[type="range"],
progress {
/* nothing needed, accent-color is inherited */
}
/* Custom UI matches the native controls automatically */
.toggle[aria-pressed="true"] {
background: AccentColor;
color: AccentColorText;
}
.selected-row {
outline: 2px solid AccentColor;
}
<label><input type="checkbox" checked> Email alerts</label>
<button class="toggle" aria-pressed="true">Dark mode</button>
Change accent-color in one place, for example inside a theme class, and both native and custom pieces update:
.theme-ocean { accent-color: #0284c7; }
What to test: if you already use AccentColor expecting the operating system’s colour, your UI will now pick up your accent-color instead. Search your CSS:
grep -rniE "AccentColor(Text)?" src/ --include=*.css --include=*.scss
2. Scroll snap in single-axis scroll containers
This is the most practical change. Consider a horizontal carousel with overflow-x: auto and overflow-y: clip. It scrolls only horizontally. Before Chrome 159, such a container still captured snap areas on both axes, including the one it cannot scroll. A snap area that asked for alignment on both axes could then not align on the vertical axis at all, and an outer vertical scroller ignored it.
From Chrome 159, a single-axis scroll container handles snap propagation and alignment separately per axis. It handles only the axis it scrolls. The other axis is passed up to the nearest ancestor scroll container that scrolls in that direction.
Example: a carousel of cards inside a snapping page
/* The page snaps vertically to sections */
html {
scroll-snap-type: y mandatory;
}
section {
scroll-snap-align: start;
min-height: 100vh;
}
/* A horizontal carousel inside a section */
.carousel {
display: flex;
gap: 1rem;
overflow-x: auto;
overflow-y: clip; /* single-axis scroll container */
scroll-snap-type: x mandatory;
}
.card {
flex: 0 0 80%;
scroll-snap-align: center start; /* block: center, inline: start */
}
<section>
<h2>Featured</h2>
<div class="carousel">
<article class="card">One</article>
<article class="card">Two</article>
<article class="card">Three</article>
</div>
</section>
scroll-snap-align takes the block axis first, then the inline axis. With Chrome 159’s behaviour, the carousel snaps cards on the horizontal axis, and the vertical alignment request is handed to the page scroller instead of being swallowed.
What to test: pages that combine an outer vertical snap with inner horizontal scrollers (carousels, tab strips, image galleries). Snapping that previously “did nothing” on one axis may now take effect, so check that it is what you want. If not, use scroll-snap-align: none start to request alignment on only one axis.
3. background-* lists keep their length in computed values
When you write several comma-separated background layers, the coordinating properties like background-position or background-size can have a different number of values than background-image. Browsers repeat or truncate the lists to match when painting. That is “used value” behaviour.
Before Chrome 159, Chrome also repeated or truncated the computed value. Now the computed value keeps exactly the number of values the author wrote, as the CSS Values spec says. Rendering does not change, but JavaScript that reads computed styles can.
<div id="hero" style="
background-image: url(a.png), url(b.png), url(c.png);
background-repeat: no-repeat;
background-position: left top, right bottom;
"></div>
<script>
const cs = getComputedStyle(document.getElementById('hero'));
console.log(cs.backgroundPosition);
// Chrome 159: the two positions you wrote
// Before: three values, with the list repeated to match the images
console.log(cs.backgroundRepeat);
// Chrome 159: a single "no-repeat"
</script>
What to test: code that splits computed background values on commas and expects one entry per image, for example animation libraries, style-copying tools or design-system tests. Pad the list yourself using the image count if you need a one-to-one mapping.
4. CSSImportRule.styleSheet can be null
@import can carry a supports() condition. When the condition is false, or no stylesheet is otherwise associated with the rule, CSSImportRule.styleSheet now returns null, as the spec requires. That lets you check before reading properties.
/* main.css */
@import url("grid-fallback.css") supports(not (display: grid));
for (const sheet of document.styleSheets) {
for (const rule of sheet.cssRules) {
if (rule instanceof CSSImportRule) {
if (rule.styleSheet === null) {
console.log('Not loaded:', rule.href);
continue;
}
console.log(rule.href, rule.styleSheet.cssRules.length, 'rules');
}
}
}
What to test: tooling that walks document.styleSheets (critical-CSS extractors, theme switchers, CSS-in-JS debuggers). Add a null check before accessing rule.styleSheet.cssRules, otherwise you may hit a TypeError.
How to test before 8 December
- Install Chrome Beta next to stable Chrome.
- Open pages with carousels, nested scrollers and snap points; check both axes.
- Check custom controls that use
AccentColoragainst native form controls. - Run your visual-regression and unit tests in Chrome Beta, especially anything that reads
getComputedStyle()background values or walks stylesheet rules. - Keep other browsers in your test run, because they may ship these spec behaviours at different times.
Takeaway
Chrome 159’s CSS changes are quiet spec fixes, but they matter. AccentColor now follows your accent-color, single-axis scrollers stop swallowing snap alignment on the axis they cannot scroll, computed background lists keep their author-written length, and CSSImportRule.styleSheet can be null. Test carousels, theming and style-reading scripts in Chrome Beta before 8 December.
