thanks, this is the stuff I keep my programming.dev account for
this post was submitted on 15 Feb 2026
27 points (96.6% liked)
CSS
779 readers
8 users here now
founded 2 years ago
MODERATORS
Since CSS has changed so much that there are old and new ways of doing things, maybe they should have changed version numbers.
Yeh, we need c++ss
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>)
;
}
Please make them incompatible so that I have to upgrade.
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.
Do I wanna bet how many of these “““modern””” snippets are Chrome-exclusive?
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.