New CSS Features You Can Use in Every Browser Now: The Late 2026 Guide

Every few months a handful of CSS features quietly cross an important line: they start working in all three major browser engines, Chrome, Safari and Firefox. That is the moment they stop being “cool demos” and become things you can actually ship on a client website.
This autumn was a good one. With Safari 27 and Firefox 155, several features that used to work only in Chrome are now supported everywhere, according to web.dev’s September roundup. Add a few that landed earlier in 2026 and you have a nice toolkit that replaces a lot of JavaScript and workaround code.
Here is what is new, what each feature is actually useful for, and code you can copy.
A quick word on “Baseline”
You will see the word Baseline a lot in this post. It is a label used by MDN, web.dev and browser makers. A feature is Baseline Newly available when it works in the latest versions of Chrome, Edge, Firefox and Safari. After about two and a half years it becomes Widely available, meaning almost every visitor’s browser supports it.
Everything below is Newly available. That means it is safe for most visitors, but people on older phones that have not updated may not see it. We will show you how to handle that at the end.
1. alpha(): change the transparency of any color
This one solves a problem almost every developer has hit. You have a brand color in a CSS variable, and you want a lighter, see-through version of it for a background or a border. Before, you had to store the color twice, once as hex and once as separate RGB numbers, or use color-mix().
Now you just write alpha():
:root {
--brand: #2563eb;
}
.badge {
color: var(--brand);
background: alpha(from var(--brand) / 12%);
border: 1px solid alpha(from var(--brand) / 40%);
}
The from keyword takes your original color, and the value after the slash sets the new opacity. Change --brand once and every tint updates with it. This is perfect for design systems, buttons, alerts and tags. It is documented on MDN’s alpha() page.
2. progress(): smooth scaling without a math headache
progress() tells you how far one value is between a start and an end, as a number from 0 to 1. That sounds abstract, so here is a real use: a heading that grows smoothly as the screen gets wider.
.hero-title {
/* 0 when the screen is 400px wide, 1 when it is 1200px or wider */
font-size: calc(1.75rem + progress(100vw, 400px, 1200px) * 1.75rem);
}
On a small phone the title is 1.75rem. On a large screen it is 3.5rem. In between, it scales smoothly. You may already do this with clamp(), and that still works fine. The advantage of progress() is that the result is a plain number, so you can reuse the same progress value for font size, spacing, opacity or anything else and keep them all in step.
One rule to remember: all three values must be the same kind of thing. Lengths with lengths, percentages with percentages, plain numbers with plain numbers.
3. light-dark() now works with images
Many sites already use light-dark() to pick a color for light mode and another for dark mode. Now Safari has joined Chrome and Firefox in letting you use it for images too. That means you can swap a logo or background for dark mode without any JavaScript or duplicate HTML:
:root {
color-scheme: light dark;
}
.site-logo {
background-image: light-dark(url("logo-dark-text.svg"), url("logo-light-text.svg"));
}
The first value is used in light mode, the second in dark mode. Do not forget the color-scheme line. Without it, light-dark() has nothing to react to.
4. Scroll anchoring finally works in Safari
You are reading an article on your phone, an image or ad loads above where you are, and the whole page jumps down. Annoying, right? Chrome and Firefox have prevented this for years with a feature called scroll anchoring. The browser keeps your reading position steady when content above it changes size. With Safari 27, it now works there too.
The good news is that scroll anchoring is on by default, so you get it for free. The CSS property overflow-anchor is for the rare case where you want to turn it off, for example on a chat window or live feed where new content should push things around:
.live-feed {
overflow-anchor: none;
}
This is especially helpful for blogs and news sites with ads. It is not a replacement for reserving space for images and ads, which still matters for Core Web Vitals, but it makes the experience much calmer for iPhone readers.
5. revert-rule: “pretend I never wrote this”
CSS already had revert, which goes back to the browser’s default style, and revert-layer, which skips a whole cascade layer. The new revert-rule is much more precise. It tells the browser to ignore only this one declaration and use whatever value would have applied without it.
.nav a {
color: white;
}
.nav a.current {
font-weight: 700;
color: revert-rule; /* keeps the white from .nav a */
}
In a tiny example like this you could simply leave the line out. Where revert-rule really shines is in shared or generated CSS, such as design system utilities and page builder output, where a rule sets a property and you need a clean way to say “not here”. Using revert in that spot would jump all the way back to the browser’s blue link, which is rarely what you want.
Earlier in 2026: three more you can use now
These reached all major browsers earlier this year and are worth knowing if you missed them.
Anchor positioning: tooltips and dropdowns without a library
For years, placing a tooltip or menu next to a button meant reaching for a JavaScript library like Popper or Floating UI. With Firefox 147 in January, CSS anchor positioning works across Chrome, Safari and Firefox, according to web.dev. Combined with the HTML popover attribute, you can build a working tooltip with zero JavaScript:
<button class="info-btn" popovertarget="tip">What is this?</button>
<div id="tip" class="tip" popover>Your changes are saved automatically.</div>
.info-btn {
anchor-name: --info;
}
.tip {
position-anchor: --info;
position-area: top;
inset: auto;
margin: 0 0 8px;
position-try-fallbacks: flip-block; /* flips below if there is no room above */
}
The button gets a name, the tooltip says “put me on top of that”, and the browser handles screen edges for you.
contrast-color(): readable text on any background
If users or clients can pick a background color, you can let the browser choose black or white text for it automatically:
.tag {
background: var(--tag-bg);
color: contrast-color(var(--tag-bg));
}
It is a simple black or white choice, so you still need to check contrast for mid-tone colors, but it removes a lot of manual work.
Container style queries: style a component by its settings
You probably know container size queries, which change a component based on how wide its container is. Style queries let you react to a custom property instead, which works nicely as a “variant” switch:
.card-wrap.featured {
--variant: featured;
}
@container style(--variant: featured) {
.card {
border: 2px solid gold;
box-shadow: 0 8px 24px alpha(from gold / 25%);
}
}
Small but handy: browser and DevTools updates
- Chrome DevTools (Chrome 155 and 156): a visual editor for
position-areawhen working with anchor positioning, inactive@starting-stylerules shown in the Styles panel, and a color picker that converts tooklch()andoklab()and suggests APCA contrast fixes. Details are in Chrome’s November DevTools post. - Firefox 160 (10 November): the old
::-webkit-input-placeholderselector now works as an alias of::placeholder, so older sites that only used the WebKit version will style placeholders correctly in Firefox. See the Firefox 160 notes.
How to use new CSS safely on real websites
“Works in the latest browsers” is not the same as “works for every visitor”. Some people do not update their phones for months. The fix is simple: write a basic version first, then upgrade it for browsers that understand the new feature.
.badge {
/* Works everywhere */
background: rgb(37 99 235 / 12%);
}
@supports (color: alpha(from red / 50%)) {
.badge {
/* Upgrade for newer browsers */
background: alpha(from var(--brand) / 12%);
}
}
Older browsers ignore what they do not understand, so they keep the first value and the page still looks fine. This approach is called progressive enhancement, and it is the reason you can use new CSS today without breaking anything.
A few more tips:
- Check support on MDN before using a feature. Each page shows a Baseline badge at the top.
- Look at your analytics to see which browsers your visitors actually use. If many are on older iPhones, keep good fallbacks.
- Use new features for “nice to have” polish first, not for things the page cannot work without.
Frequently asked questions
Do these new CSS features work in WordPress?
Yes. CSS runs in the visitor’s browser, so it does not matter whether the site is built with WordPress, Bricks, Elementor or plain HTML. Add the code to your theme stylesheet, the Additional CSS panel or your page builder’s custom CSS area.
Can CSS anchor positioning replace JavaScript tooltip libraries?
For most simple tooltips, dropdowns and popovers, yes. Complex cases with lots of custom logic may still need JavaScript, but you no longer need a library just to place a box next to a button.
What is the difference between alpha() and color-mix()?
color-mix() blends two colors together. alpha() only changes the transparency of one color and keeps everything else the same. For “a see-through version of my brand color”, alpha() is shorter and clearer.
Should I stop using clamp() now that progress() exists?
No. clamp() is still great and has much wider support. Use progress() when you want to reuse the same scaling value across several properties.
Final thoughts
CSS keeps taking over jobs that used to need JavaScript: tooltips, color tints, dark mode images and smooth scaling. That means less code to download, fewer libraries to update and faster pages. Pick one feature from this list, try it on your next project with a simple fallback, and you will be surprised how much code you can delete.
If you are newer to CSS layout, start with our guide to building a three column layout with Flexbox. And if you want to see how JavaScript fits alongside CSS, read JavaScript: the dynamic language powering web development or our take on whether jQuery is dead.
