Post

End of the year is approaching. I should probably start planning the next CSS Selection and not yolo it like I did this year. Does anyone have requests for what we should analyze?

23/9/26, 7:11 am4 reposts5 likes

Vale

@vale.rocks

I'll go buy a red pen or two...

That'd be super rad!

Since you now have last year‘s data, you can start comparing things. A “rising stars” section for example, which you then try to map with the feature becoming Baseline {Newly|Widely} Available.

Bart Veneman

@veneman.dev

Oh, that's nice, thanks!

Bramus

@bram.us

I think you can also map properties through BCD (github.com/mdn/browser-...) to web-features (github.com/web-platform...), in order to get some sort of grouping (e.g. “Anchor Positioning” to cover all anchoring-related properties) which you could then rank by popularity.

Jakob E

@jakob-e.bsky.social

All three are great for a combined mapping (including sub-features). I made a little prototype tool to test features against browser targets css.franklyone.com/support/

css.franklyone.comCSS Feature Support