Future CSS Features
Discussions revolve around CSS limitations, upcoming native features like nesting, :has pseudo-class, and @layer, vendor prefixes, and preprocessors like PostCSS as workarounds or precursors.
Activity Over Time
Top Contributors
Keywords
Sample Comments
I think I'd still CSS is badly broken, until this is available everywhere.
Guess the idea is future css releases. But well i most likely wont use it ether.
Would love to see something like this support CSS.
This is how things start. This could be the future of CSS that becomes part of browsers some day.
Next stop: CSS vendor prefixes.
This is an advance version of CSS. I would like to know you did it.
You'll have to wait for CSS4 for that...
It's interesting to consider the parallels between this and CSS vendor prefixes.
There's the experimental :has pseudo-class which appears to be doing what you want [1].Personally, I'm against adding any more complexity to CSS, though; and :has fundamentally changes the locality/algorithmics and complexity of CSS selector matching. I think if the goal of CSS was to bring good-enough styling to the masses, it has utterly failed to so, yet has left a legacy of overcomplicated and badly specified ad-hoc styling rules that don't compose to a reasonable whol
Years of expertise and competitive edge now destroyed by a new CSS feature. How cruel.