State of CSS 2025 Suggestions

[SachaG]

No description provided.

[jsnkuhn]

I've noticed over the last few years that there are a fair number of folks who claim to be using the CSS image() function (https://www.w3.org/TR/css-images-4/#image-notation) even though this is not implemented in any browsers. What's the requirement for properties to get listed as features on the survey? Do they have to be implemented in at least one browser?

screenshot from 2023:

[SachaG]

@jsnkuhn good point! The reason we include features that haven't been implemented yet is so that we're able to track things like awareness or interest over their entire lifetime, from conception to implementation. Also, sometimes people might've used something via a polyfill or preprocessor. In this specific case though it might very well be people just mistaking this for another feature…

[SachaG]

• Alt text for generated content

[SachaG]

• field-sizing

[SachaG]

• @import

[SachaG]

-calc-size(auto) https://blog.webdevsimplified.com/2024-07/css-calc-size/

[jsnkuhn]

From some folks over in Kevin Powell's discord:

There were some newer folks who didn't recognize many of the properties on the survey and felt the "Well Done!" was not appropriate.

There were also some folks who did better but still got the "you are in the top 100%" message? Wondering if there was a bug that showed peeps as in the top 100% too often?

[SachaG]

Yes, the percentage calculation is (was?) buggy. I might remove it altogether, it's meant to be a fun datapoint, not something people actually care about – how many features you know or don't is pretty meaningless in the grand scheme of things…

[SachaG]

• sibling-index/sibling-count https://www.w3.org/TR/css-values-5/#tree-counting

[SachaG]

• Add pain points to each section
• Add new "CSS challenges" multiple-choice quiz section (with help from https://css-challenges.com/ ?)