What ELSE is in your CSS wishlist?

What else do we wish or want CSS to do? It’s like being out late at evening someplace you shouldn’t be and a stranger in a trenchcoat walks up and whispers in your ear.

“Psst. You wanna purchase some async @imports? I’ve acquired the specificity you need.”

you shouldn’t entertain the thought however you do it anyway. All your folks doing Cascade Layers. What are you, a sq.?

I hold considering of how wonderful it’s to write down CSS immediately. There was an electronic mail change simply this morning the place I used to be discussing a bunch of concepts for a persistent set of controls within the UI that will have sounded bonkers even one 12 months in the past if it wasn’t for brand spanking new options, like anchor positioning, scroll timelines, auto-height transitions, and popovers. We’re nonetheless within the early days of all these items — amongst many, many extra — and have but to see all of the superior prospects come to fruition. Thrilling instances!

Chris saved a CSS wishlist, going again so far as 2013 and following up on it in 2019. All of us have issues we’d wish to see CSS do and we at all times will regardless of what number of sparkly new options we get. Let’s revisit those from 2013:

✅ “I’d like to have the ability to choose a component based mostly on if it incorporates one other explicit selector.” Hey, :has()!

❌ “I’d like to have the ability to choose a component based mostly on the content material it incorporates.”

❌ “I’d like a number of pseudo-elements.”

✅ “I’d like to have the ability to animate/transition one thing to peak: auto;” Yep, we acquired that!

🟠 “I’d like issues from Sass, like @lengthen, @mixin, and nesting.” We acquired the nesting half down with some progress on mixins.

❌ “I’d like ::nth-letter, ::nth-word, and so on.”

✅ “I’d like all the key browsers to auto-update.” This one was already fulfilled.

So, a few rating of three.5 out of seven. It may very nicely be that a few of these issues fell out of favor sooner or later (haven’t heard any crying for a brand new pseudo-element for the reason that first wishlist). Chris re-articulated the listing this fashion:

Mother or father queries. As in, choosing a component any-which-way, then choosing the guardian of that component. We have now some proof it’s potential with :focus-within.

Container queries. Choose a specific component when the component itself is underneath sure circumstances.

Standardized styling of type components.

Has/Accommodates Selectors.

Transitions to auto dimensions.

Fastened up dealing with of viewport models.

And we’ve acquired the overwhelming majority of these underneath wraps! We have now methods to question dad and mom and containers. We’re exploring stylable selects and field-sizing. We learn about :has() and we’re nonetheless going gaga over transitions to intrinsic sizes. We’ve brazenly opined whether or not there’s an excessive amount of CSS (there isn’t).

However what else is in your CSS wishlist? Mockingly sufficient, Adam Argyle went via this train simply this morning and I really like the best way he’s damaged issues down right into a user-facing wishlist and a developer-facing wishlist. I imply, geez, a CSS carousel? Sure, please! I really like his listing and all lists prefer it.

We’ll spherical issues up and put a listing collectively — so tell us!

What ELSE is in your CSS wishlist? initially revealed on CSS-Methods, which is a part of the DigitalOcean household. You must get the publication.