My top 10 anticipated CSS features 🔮

Heya!

I just published a brand-new blog post about the current set of proposals being considered by browser vendors for Interop 2027. There’s some incredibly exciting stuff in here.

But first, two quick announcements:

• 1. I’ll be having a Black Friday sale again this year! The sale will start on November 23rd and run for about a week. You’ll be able to save ~40% on each course individually, with even bigger discounts on bundles. ✨
• 2. I’ve spent the past couple of weeks working on a top-secret project all about sound effects on the web. I’ll be releasing it for free during the Black Friday sale, and wanted to share a lil’ sneak peek:

Honestly, I put way too much work into this 😂. But I’m very happy with how it’s coming along, and I can’t wait for you to check it out!

Alright, onto the new blog post.

Ranking my top Interop 2027 choices

For the past 6 years, all of the major browser vendors (Google/Microsoft/Apple/Mozilla) have been working together on a project known as Interop. The goal of the project is to synchronize efforts so that HTML/CSS/JS features are interoperable across browsers, so that when a new feature comes along, we don’t have to wait many years to be able to start using it in our work. ✨

This project has been remarkably successful, and the team is currently choosing their focus areas for 2027. The Mozilla team has created an Interop 2027 voting system that allows us developers to rank our top choices, as a way to signal which features are important to us.

There’s some really good stuff in here, so I decided to write a blog post about my 10 top choices.

Many of these features are already implemented in some browsers and can be used today. I’ve also included a couple little bonuses, like fallback techniques you can use today to accomplish the same goals. So, even if you have no interest in hypothetical future CSS, I think there’s a bunch of stuff in here that you can immediately benefit from. ✨

You might be feeling like we don’t really need to know about this stuff anymore, in a world where so much code is AI-generated. Personally, I think it’s more important than ever. We can’t expect LLMs to automatically use modern CSS features when so much of their training data is years old. So, whether you still write CSS by hand or not, I think there’s a ton of value in knowing the state-of-the-art.

You can read the new post here:

• → The Future of CSS ✨

That’s it for me! Hope you’re having a good week. ❤️

PS. Speaking of future web APIs, the State of HTML 2026 survey just opened. Every year, I’m surprised by just how much new stuff there is when it comes to HTML (and related DOM APIs).