2026 is nearly upon us. I do know we’re all itching to see the clock strike midnight (cue The Remaining Countdown by Europe), however not with out recapping the most effective CSS-related issues that occurred during the last two weeks!
Conditional view transitions
Chris Coyier confirmed us learn how to set off totally different view transitions primarily based on the URL (or any conditional JavaScript logic, actually). Nevertheless, Bramus talked about within the feedback that navigation matching is coming to CSS, so we’d not must depend on JavaScript for that half for very lengthy. I’m maintaining my fingers crossed for 2026!
Annotating design system parts for accessibility
Geri Reid fastidiously defined learn how to annotate design system parts for accessibility, giving stable HTML-based examples. I particularly love the half about defining components, ARIA, markup, keyboard navigation, zoom, and person preferences as accessibility tokens.
Firefox to turn out to be a “fashionable AI browser” to the delight of completely nobody
Firefox has been a little bit of a rollercoaster these days. It began with an interview on The Verge, the place new CEO Anthony Enzor-DeMeo stated that Firefox “will evolve into a contemporary AI browser.” With solely 2.3% of the browser market share, I suppose it was inevitable that Firefox would attempt to shake issues up, however customers don’t seem to need this in any respect. To stem the bleeding although, they’ve introduced an AI kill swap.
And that’s how I met your Mo- …Waterfox, which is a no-AI fork of Firefox.
Creating ‘toon textual content with CSS and SVG
Andy Clarke demonstrated learn how to create the textual content results of traditional ‘toons utilizing CSS and SVG. I hadn’t heard of the paint-order CSS property earlier than this, in order that half is fairly darn cool.
6 CSS options that you need to study in…2025
That’s proper, 2025! Adam Argyle wrote concerning the CSS options that you need to study in 2025 at first of the yr. Properly, it’s virtually 2026 now, so how did you do? I’ll be sincere — I barely even touched the floor of @property.
Nice CSS posts on Bluesky
Let’s be sincere, social media isn’t a enjoyable place to hang around anymore, however I’ll make the exception for Bluesky. I not often see stuff that’s not related to my pursuits, I truly discuss to folks on there, there’s a big dev neighborhood on there, and naturally CSS-Tips is on Bluesky too, as is the CSS-Tips workforce and lots of our authors.
So since browser updates usually ship at first of the month, listed below are some cool posts by the Bluesky CSS neighborhood as a substitute:
Temani Afif demonstrated a really attention-grabbing mixture of anchor positioning, attr(), container queries, and form(), which you’ll be able to mess around with (in all probability requires Chrome):
Stephen Margheim listed the assorted causes why you need to namespace your semantic courses (e.g., rename .btn to .ui-button):
Just like Andy Clarke’s ‘toon textual content explorations, Ana Tudor’s displacement map textual content results are relatively astonishing as effectively, though you’ll most certainly want Chrome for cutting-edge stuff like this:
There are extra displacement map textual content results in Ana’s feed.
George Black stated:
Writing CSS for my web site that makes use of fashionable options solely obtainable in Chrome or Safari, however not each. Eventual consistency — ultimately it’ll look proper in a single browser… proper?
Truly, sure! More than likely. For people who don’t know, the Interop Mission is a collaboration between Chrome, Firefox, and Safari the place they make sure options work persistently throughout their browsers. You may even vote on the options! Eager to study extra? Learn what Chrome and WebKit have stated about Interop 2026.
Lastly, a large shout-out to our very personal Sunkanmi Fafowora for saying what we’re all pondering:
Thanks to all who work very exhausting to broaden and push the boundaries of what we will do with CSS. You’ve made my work and the work of hundreds of thousands of others a lot simpler. You’re not unnoticed, and I do hope you’re having a tremendous day.
On that notice, the CSS-Tips workforce needs you a really glad new yr. Could your web sites be freed from bugs and work in all (secure) browsers!
See you in 2026!
