I'm not sure turning CSS into a full blown language is a good idea. With all the cascading in place, it is already a bit hard to determine why certain styles are applied. Now with this, we will be spending more brain cells debugging CSS issues.

▲

lmm 6 hours ago | parent | next [-]

On the contrary, a lot of the reason CSS is confusing is because it's full of insane hacks people have to do to get the behaviour they want. A straight-up if statement is much simpler than many of the horrors I've seen.

▲

adgjlsfhk1 5 hours ago | parent | prev [-]

css definitely shouldn't have backwards branches (loops/recursive functions), but adding a little more power can clean up expression a ton and make reading/applying that much faster

	▲	lenkite 4 hours ago \| parent [-]
		I wish the "little more power" would add CSS modules. It would also be great if web components didn't require Javascript and could be configured with pure HTML and CSS. I will kiss the feet of the whatwg groups if they do this. PS: Would also love to have declarative template inclusion now that removal of XSLT has also removed this facility from the browser.