2025.stateofcss.com
CSS Usage - State of CSS 2025
Excerpt
### Link to sectionBrowser 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. … ### Link to sectionMissing 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! ### Link to sectionOther 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. … ### 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.
Source URL
https://2025.stateofcss.com/en-US/usage/Related Pain Points
Safari browser lags in CSS feature support
6Safari's CSS feature support lags behind other major browsers, creating platform-specific compatibility issues and forcing developers to write Safari-specific workarounds.
Cross-Browser Compatibility and Testing Challenges
6Making designs and experiences work consistently across different browsers remains a significant challenge (26% of developers in Q1 2021). Browser testing is time-consuming, polyfill management is complex, and developers struggle to identify reliable, high-quality polyfills.
Missing native CSS mixins and functions
5Developers still rely on preprocessors like Sass, Less, and PostCSS for mixins and advanced functionality, despite repeated requests for native CSS support. This perpetuates tool dependencies and learning curves.
Speed of CSS language evolution outpaces developer adoption
3CSS is evolving rapidly with new features introduced constantly, making it difficult for developers to keep up with learning curve and adoption timelines.
Hard-to-remember CSS syntax
2CSS has many features with complex or counter-intuitive syntax that developers struggle to remember, increasing cognitive load and requiring frequent reference checks.