Ok, that's cool. How long until we're able to use this and not have to worry about browser incompatibilities?
You can use it today with the help of http://cssnext.io
CSS Variables landing in Chrome 49
11–20 of 70 posts
Re: CSS Variables landing in Chrome 49
#12Earlier quoted context omitted.
~5 years depending on who you're targetting.
Pretty sad that in a world with living standards and silent updates, things that improve the state of the Web so vastly for developers still take so long to be widely available. (W3C doesn't even have a CR yet.) Less and Sass are nice, but the resulting CSS is full of repetition, thus hurting performance. Am I right in assuming that IE won't receive any more feature updates? Many enterprises will stay on Win 7 for a…
Given that Edge has pretty much completely replaced IE, then yes, it's unlikely IE will receive any more updates. And to make it worse, Microsoft doesn't seem to be updating Edge as much as they were promising, meaning that we could end up in the exact same situation as before.
Re: CSS Variables landing in Chrome 49
#13Re: CSS Variables landing in Chrome 49
#14[deleted]
Re: CSS Variables landing in Chrome 49
#15The syntax is verbose and ugly compared to SASS
I think a lot of people agree with you but there is a reason: http://www.xanthir.com/blog/b4KT0
Stupid decision, the should have used $foo (dollar sign for variables) like in Perl and PHP. It remind me decisions of standards based on XML (XLST, XML-Schema, RDF, etc).
Re: CSS Variables landing in Chrome 49
#16Just add native support for Sass and call it a day.
Re: CSS Variables landing in Chrome 49
#17Well, that was a long time coming. I was playing with a beta version of CSS Vars 4+ years ago, which was then removed and eventually replaced with this.
Re: CSS Variables landing in Chrome 49
#18I've wondered for years why we're using pre-processing to get variables into CSS. Given that there hasn't been a commonly advocated workflow that didn't include some sort of CSS processor (like LESS or SASS) in about a decade, it seems like somebody working on the standards would have realized that CSS needed variables, at the very least. So, it's cool that it's coming, though it's taken a lot longer than I reckon it…
The CSS team has people like this, who no longer make websites: https://www.w3.org/People/Bos/CSS-variables Thus they're disconnected from current web developers.
Meanwhile Smashing says something like 77% of audience uses SASS.
Re: CSS Variables landing in Chrome 49
#19Ok, that's cool. How long until we're able to use this and not have to worry about browser incompatibilities?
I have a plugin that adds the ability for CSS to retrieve variables and values from regular JS!
It works in every browser today, and even old browsers, INCLUDING IE8!
Re: CSS Variables landing in Chrome 49
#20I've wondered for years why we're using pre-processing to get variables into CSS. Given that there hasn't been a commonly advocated workflow that didn't include some sort of CSS processor (like LESS or SASS) in about a decade, it seems like somebody working on the standards would have realized that CSS needed variables, at the very least. So, it's cool that it's coming, though it's taken a lot longer than I reckon it…
The CSS team has people like this, who no longer make websites: https://www.w3.org/People/Bos/CSS-variables Thus they're disconnected from current web developers. Meanwhile Smashing says something like 77% of audience uses SASS.
Didn’t Firefox have actual SASS support for some time? I think at least the dev tools had support for SASS source maps, but I’m not sure if the browser actually had support.