섹션 링크 공유Testing Environments
While testing environments don't show much change year over year, it's encouraging to see a small increase in respondents testing with keyboard-only and screen readers.
It's also interesting to note that when comparing with company size, larger companies tend to test using screen readers at a higher rate.
섹션 링크 공유CSS Usage
While CSS started its life as a document layout system, it's now clear that interactive apps represent its primary use case–a fact that has been no doubt driving the language's recent evolution.
My 2025 Pick: Combining features
My pick not as much a single feature that changes things, as it is the way multiple features can be used together.
For example, subgrid + the new corner-shape (or the shape() clip-path function) to get content-dependant shapes with concave roundings that aren't necessarily circular.
섹션 링크 공유직종
Many of us are building tools destined to be used internally within the developer community, which makes it much easier to adopt new features without worrying as much about browser compatibility.
섹션 링크 공유Browser Incompatibilities
Not only did Anchor Positioning keep its number one spot, but the percentage of respondents citing it almost doubled.
The View Transition API also climbed to number 3, while Container style queries gained a whopping 11 spots in the rankings.
On the other hand, CSS Nesting and :has() both lost ground, which makes sense since these features are now supported in all major browsers.
My 2025 Pick: CSS Math Functions
Math is the language of the universe, of life itself, and without it, we wouldn’t be able to describe, measure, or build anything with clarity.
So the fact that we can now use these functions natively in CSS only strengthens our capabilities and opens up a whole world of new possibilities.
Amit Sheen
섹션 링크 공유Missing Features
Mixins are still the feature developers wish for the most, closely followed by Masonry Layout. Both have long been possible using workarounds such as pre-processors or JavaScript, but it would be nice to see them natively supported in CSS!
섹션 링크 공유Other CSS Pain Points
Browser Support may still be the dominant CSS pain point in 2025, but the fact that only a relatively small 10% of question respondents mentioned it is a testament to recent improvements in this domain.
섹션 링크 공유Favorite New Feature
While :has() is still number one, it did lose a bit of ground, as the View Transition API and especially Anchor Positioning (which gained 8 spots) start seeing wider adoption.
My 2025 Pick: Picalilli
Saron Yitbarek
섹션 링크 공유Game-changing Feature
Every new CSS feature has its use, but only a few of them are real game-changers. It turns out Grid, :has(), and CSS Nesting are the features that most changed how we write CSS in recent years.
섹션 링크 공유Baseline Awareness
We wanted to see how familiar respondents are with the Baseline browser compatibility indicator (which you can see in use throughout these very survey results!).
Despite our clever traps in the form of fake answers, the vast majority of you successfuly negotiated the question! Younger respondents in particular showed higher awareness of Baseline, no doubt due to the recent Baseline integration in Fortnite (…just kidding).
섹션 링크 공유Pace of Change
Adopting a new feature is usually a multi-stage process: first, you hear about it a few times over the course of months or years, until you form a solid idea of what it does. Then, you might try it out on an experimental side project, before finally adopting it in production.
This chart shows that most of us are squarely in the middle of this journey, having learned about and tried out only part of the feature set presented in this survevy.
My 2025 Pick: The light-dark() Function
color-scheme in CSS, using light-dark() to declare colors based upon whether light or dark mode is currently in use feels like a no-brainer. I'm currently enjoying following this discussion thread about what further logic we may use in the future, to query color-scheme and change CSS conditionally.섹션 링크 공유Web Technologies Happiness
Happiness with the web has been fairly stable over the past years, neither going up or down.
섹션 링크 공유State of CSS
On the other hand, happiness with CSS specifically shows a clear upwards trend in recent years, which happens to align nicely with the language's own rapid pace of improvement.
섹션 링크 공유추천하는 리소스
Getting Started with CSS, v2
