2026 is nearly upon us. I do know we’re all itching to see the clock strike midnight (cue The Last Countdown by Europe), however not with out recapping one of the best CSS-related issues that occurred during the last two weeks!
Conditional view transitions
Chris Coyier confirmed us methods 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 have to depend on JavaScript for that half for very lengthy. I’m maintaining my fingers crossed for 2026!
Annotating design system elements for accessibility
Geri Reid rigorously defined methods to annotate design system elements for accessibility, giving stable HTML-based examples. I particularly love the half about defining parts, ARIA, markup, keyboard navigation, zoom, and consumer preferences as accessibility tokens.
Firefox to grow to be a “trendy AI browser” to the delight of completely nobody
Firefox has been a little bit of a rollercoaster recently. It began with an interview on The Verge, the place new CEO Anthony Enzor-DeMeo mentioned 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 change.
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 methods 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 must study in…2025
That’s proper, 2025! Adam Argyle wrote in regards to the CSS options that you must study in 2025 originally of the 12 months. 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 really speak to individuals on there, there’s a big dev neighborhood on there, and naturally CSS-Methods is on Bluesky too, as is the CSS-Methods crew and lots of our authors.
So since browser updates sometimes ship originally of the month, listed below are some cool posts by the Bluesky CSS neighborhood as an alternative:
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 (most likely requires Chrome):
Stephen Margheim listed the assorted causes why you must 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 quite astonishing as nicely, 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 mentioned:
Writing CSS for my web site that makes use of trendy options solely obtainable in Chrome or Safari, however not each. Eventual consistency — finally it’ll look proper in a single browser… proper?
Really, sure! More than likely. For those who don’t know, the Interop Undertaking is a collaboration between Chrome, Firefox, and Safari the place they make sure options work persistently throughout their browsers. You’ll be able to even vote on the options! Eager to study extra? Learn what Chrome and WebKit have mentioned about Interop 2026.
Lastly, an enormous shout-out to our very personal Sunkanmi Fafowora for saying what we’re all considering:
Thanks to all who work very arduous to increase and push the boundaries of what we are able to 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-Methods crew needs you a really blissful new 12 months. Could your web sites be freed from bugs and work in all (secure) browsers!
See you in 2026!
