A historical day for CSS 😀🎉 We (the CSS WG) resolved to add an inline if() function, allowing CSS authors to conditionally branch values based on custom properties, media queries, or supports conditions. It was very hard to get consensus on it, but I’m so glad we got there. So many use cases and author pain points addressed in one go! Edited to add: I wrote up some background and an FAQ: https://lnkd.in/dkM8kMWu GitHub issue for more details:
Daniel Glazman
5mo
I hope the WG understands well that this is a death knell for the wysiwyg editability of arbitrary web pages ( like I did in BlueGriffon long ago).
Maja Jaakson
5mo
WHOA 🤩 This is epic!!
Faruk Ateş
5mo
Aw, feels like a great evolution from where it started 15 years ago (also, omg it’s been that long!) 🙂
Aaron Mendez
5mo
Thank you, Lea Verou. The web community is very fortunate that someone of your caliber has their hands in the clay of our medium. Keep up the good work!
Jens Törnell
5mo
With your work, you don't only affect the CSS community, but everyone using CSS. That includes every single person on this planet, with an internet connection. Kind of cool! Keep going! ⭐️
Kartikey Kumar
4mo
I can only imagine the amount of discussion that has to happen in CSS WG before finally getting your proposal accepted. Any change in CSS is going to impact so many developer's lives hopefully for the better, Congrats!
Matthew Dean
5mo
CSS adding Less.js functions, one function at a time.
Alex Danilo
5mo
When are we getting a 'for' loop? 😉
Deivid Marques
5mo
awesome, thank you 🙌🏼
Ingénieur technico co chez IVèS
5moThat's bad. CSS are supposed to be declarative not programmatic. CSS preprocessor are powerful enough to address that. To me that breaks the very design of a web page where HTML is about structure and semantic, CSS about display and JS about programmability. But I guess I am too old.