The features that used to have an asterisk
For a few years now, every "exciting new CSS feature" write-up came with the same quiet caveat: great feature, limited browser support, check back later. In 2026, "later" has arrived for a genuinely useful cluster of them, largely thanks to this year's Interop initiative — a coordinated push across Blink, WebKit, and Mozilla to bring consistent support to the features developers have been asking for the longest.
Container queries are the clearest case. They shipped in all major browsers back in late 2023, but production adoption lagged behind availability for years, the way it usually does. In 2026, they've finally crossed into "just use them" territory, with the fact that browser support is essentially universal removing the last excuse to keep hand-rolling JS that measures a parent's width and toggles classes based on the result.
The feature everyone's been waiting for
Anchor positioning is the one generating the most genuine excitement, and for good reason: it lets you tether one element to another — a tooltip to its trigger, a dropdown to its button — using pure CSS, no JavaScript positioning library required. It's the native replacement for Popper.js, Floating UI, and every custom tooltip-positioning hack you've ever had to debug at 11pm because it broke near a viewport edge.
It's also, per this year's State of CSS survey, the single feature with the largest year-over-year increase in actual usage, which tells you developers aren't just curious about it — they're shipping it. The honest caveat: support is still uneven enough across browsers that you need a sensible fallback if your audience includes anyone on an older Safari release. It's not yet at the "universally safe" level of :has() or container queries, but it's close enough to be worth adopting with a fallback in place today.
CSS quietly absorbing JavaScript's job
The broader theme across this year's CSS additions is components getting more context-aware without reaching for JavaScript at all. Scroll-driven animations replace scroll event listeners that used to run on every frame and jank on exactly the low-end devices you most needed to support. The Popover API gives you native modal behavior without a UI library. @starting-style handles clean enter transitions without the flash-of-unstyled-content workarounds that used to require careful class-toggling choreography.
None of these individually are revolutionary. Together, they represent a real shift: patterns that were universally handled in JavaScript a few years ago now have native, more performant, more accessible CSS equivalents.
What's worth adopting now versus waiting on
Safe to ship today across evergreen browsers: container queries, the Popover API, scroll-driven animations with a prefers-reduced-motion branch, and @starting-style transitions. Worth adopting with a fallback: anchor positioning, where the payoff is high but Safari support still lags. Worth watching but not betting production code on yet: newer proposals like if() and gap decorations, which remain gated by limited browser availability.
The practical migration path isn't "rewrite everything in CSS overnight." It's auditing your JS bundle for the handful of libraries solving problems the browser now solves natively, and removing them one at a time as your support matrix allows.