A reminder that #CSSnesting is still a working draft in the #W3C under the #CSSWG. Please mind #webcompat when using this relatively new feature. IOW, don't make your #CSS break because you assumed everyone right now is using the latest version of #Chrome / #Chromium, #Firefox, #Safari, or #Edge. They might not even be using a mainstream #browser to visit your website (I am using #PaleMoon for example)... :seija_coffee:
Question aux développeurs web front et/ou intégrateurs, j'ai l'impression que le #nesting#css est une petite révolution en soi, mais qu'il reste une marge de progression par rapport à ce qu'offrent les préprocesseurs. Est ce que ça change quelque chose au final dans vos habitudes de développement ? #nestingCss#cssNesting
I think we're going to regret #CSSNesting, at least the way it’s defined in the spec.
#CSS has been going in a very strong direction for the past five years. There just aren’t any more “gotchas” or confusing/misleading parts of modern CSS, because the W3C has worked their asses off essentially refactoring them all away... except nesting.
Many things I love about #CSS. One is reading of features I've never/barely heard of, such as in @5t3ph's talk/mega-tutorial– https://front-end.social/@5t3ph/110514087802458725 – knowing they don't need me to first install something on a server, or persuade a client to adopt or upgrade a particular language or framework and assess if it might become obsolete. They're just arriving, in every browser, sooner or later (eyes glued to #Firefox with #CSSNestinghttps://caniuse.com/css-nesting).