Link to sectionLayout Pain Points
Similar to last year, Grid is the most frequently mentioned item when it comes to layout pain points. This is a reflection both of its increased usage (having now become the default CSS layout method for many developers), but also of its undeniable learning curve.
And while widespread Subgrid browser support is certainly welcome, that feature does add one more layer of complexity to an already-intricate layout system.
View:
Link to sectionShapes & Graphics Pain Points
CSS is getting better and better at letting us go beyond the rectangle and draw all kinds of fancy shapes without having to resort to Canvas or even SVG.
The issue now is browser support: until all browsers implement these features, it'll be hard to convince developers to start using them.
View:
Link to sectionColors Pain Points
In recent years, CSS has given us many innovative ways to define colors. The challenge now seems to be finding ways to actually use this new rainbow of possibilities without turning our stylesheets into a mess of color theory math formulas.
This is where Theming comes in, especially as we move away from the binary light/dark duality, towards a conception of themes that also takes proper contrast and accessibility into account.
View:
Link to sectionInteractions Pain Points
Just like with shapes and graphics, interactions and animations is another area where browser support is lagging a bit behind.
CSS Carousels also generated some feedback, especially centered around accessibility concerns.
View:
Link to sectionOther Features Pain Points
Besides being the top three most-mentioned features in this category, what Cascade Layers, CSS Nesting, and if() have in common is that they all have the potential to drastically change how we write CSS code.
Despite that, respondents were overall fairly enthusiatic about adopting them, mainly being held back by the lack of proper browser and tooling support.