Well spotted, the article states:

The :heading pseudo-class is currently available in nightly builds only. You can test it now in:

• Firefox Nightly (behind a flag)
• Safari Technology Preview

yep

I love this so much.

Isn't :heading literally not supported anywhere?

div.mydiv {
  template <Variable mycolor> 
  requires std::is_named_color<mycolor> || is_function_color<mycolor> || is_hexa<mycolor>
  mydiv& background-color: mycolor 
  noexcept( noexcept( background-color: mycolor) || !std::is_IE6 )
  --> decltype (css_declaration<property>)
  ;
}

To what end? What would you expect version numbers to do? How would you specify or use them, which what consequences?

Grouping changes into releases with explicit numbering instead of a living standard with generic @supports checks?

I guess it would make some things easier and more obvious.

Please make them incompatible so that I have to upgrade.

thanks, this is the stuff I keep my programming.dev account for

Yeh, we need c++ss

Each snippet clearly states which browsers+version supports it (as well as a general year if all major browsers support it). At a quick glance, with the exception of trying to find an unsupported on Firefox snippet, everything seemed supported by all major browsers.

Since CSS has changed so much that there are old and new ways of doing things, maybe they should have changed version numbers.

Do I wanna bet how many of these “““modern””” snippets are Chrome-exclusive?

It’s brand new and has incomplete browser support as of this writing (come on, Firefox!),

So, basically useless, better to go back to the old trick?

We shouldn't be promoting things that only (or mostly) work in Chrome.

Oh yeah I do. Was just exagerating a little (note: a little). Bottom <hr>: you can't really call something "modern CSS" (or "good CSS") if it only works in Chrome.

Those will be cool once they’re baseline available.

jorunalism

Sir, this is a codepen. Do you know what CSS Tricks is?

Really? Wow, it's incredible what passes for jorunalism these days.

It doesn't even render the hexagons in Waterfox lmao

Support is limited to Chrome only

Into the trash bin it goes.

If you can scope 3rd-party CSS, because the client HAS to use that particular chat vendor, then maybe this can keep their chocolate out of my peanut butter?

Yeah, but seriously … I can’t come up with a use case. Maybe I don’t understand it correctly, but I don’t see how @scope could help me when I already use nesting.

My gut says... it's CSS, always has been

So it’s basically nesting but with extra steps?

I am happy to share that we (the @GoogleAIStudio team) are now a sponsor of the @tailwindcss project! Honored to support and find ways to do more together to help the ecosystem of builders.

by Logan Kilpatrick - user profile desc: Lead product for @GoogleAIStudio & Gemini API. My views!

Layoffs are a failure of leadership and so is this.