CSS Variables in Firefox 31 – new syntax
1–10 of 54 posts
Re: CSS Variables in Firefox 31 – new syntax
#2I'm sure it'll be a real joy to use that for anyone who's been using Sass or Less (and who doesn't, these days...).
Re: CSS Variables in Firefox 31 – new syntax
#3That new syntax is astonishingly ugly and bizarre. I'm sure it'll be a real joy to use that for anyone who's been using Sass or Less (and who doesn't, these days...).
The "var()" function is just.. redundant. Or maybe I'm missing something?
Re: CSS Variables in Firefox 31 – new syntax
#4That new syntax is astonishingly ugly and bizarre. I'm sure it'll be a real joy to use that for anyone who's been using Sass or Less (and who doesn't, these days...).
Re: CSS Variables in Firefox 31 – new syntax
#5That new syntax is astonishingly ugly and bizarre. I'm sure it'll be a real joy to use that for anyone who's been using Sass or Less (and who doesn't, these days...).
Yeah, obviously they need to avoid conflicts but surely they could have found a single character to use as a prefix instead of "--", like "$" or "@". The "var()" function is just.. redundant. Or maybe I'm missing something?
http://lists.w3.org/Archives/Public/www-style/2014Mar/0261.h...
And later on the justification for not using $ or @:
http://lists.w3.org/Archives/Public/www-style/2014Mar/0400.h...
There's also the issue that this needs to be backwards compatible with parsers that don't support the syntax, and apparently because the variables cascade that makes it harder still. I agree it's ugly though.
Re: CSS Variables in Firefox 31 – new syntax
#6That new syntax is astonishingly ugly and bizarre. I'm sure it'll be a real joy to use that for anyone who's been using Sass or Less (and who doesn't, these days...).
`--` is a comment in many languages (sql, haskell, ..).
Re: CSS Variables in Firefox 31 – new syntax
#7Earlier quoted context omitted.
Yeah, obviously they need to avoid conflicts but surely they could have found a single character to use as a prefix instead of "--", like "$" or "@". The "var()" function is just.. redundant. Or maybe I'm missing something?
Here's the discussion where they changed from "var-" to "--": http://lists.w3.org/Archives/Public/www-style/2014Mar/0261.h... And later on the justification for not using $ or @: http://lists.w3.org/Archives/Public/www-style/2014Mar/0400.h... There's also the issue that this needs to be backwards compatible with parsers that don't support the syntax, and apparently because the variables cascade that makes it harder s…
"> As far as I understand, the main reason of why Tab's original idea of using `$` has eventually been dropped was some uncertainty about its possible extensibility for being used in property _names_ besides property _values_.
The reason it got dropped is that some people (including Tab) do believe we should reserve $ for mixins and other preprocessor-like operations which may potentially be added to the language at some point. e.g. futuristic things like:
@define apply-2d-transform(initial-scale, initial-rotation, ...) {
...
my-transform-scaling: $initial-scale;
my-transform-rotation: $initial-rotation;
...
transform:
scale(get(my-transform-scaling))
rotate(get(my-transform-rotation))
translate(get(my-transform-translation));
will-change[]:
transform;
}
.some-element {
$apply-2d-transform(...);
transition[]: transform 0.5s ease-in-out;
}
.some-element:hover {
my-transform-scale: 1.1;
}
but this syntax was just made for this example, final milage may look
completely different and/or offer different features)"Re: CSS Variables in Firefox 31 – new syntax
#8Re: CSS Variables in Firefox 31 – new syntax
#9[1] http://stackoverflow.com/questions/18466569/enable-experimen...