RE: [css-variables] RE: CSS Variables in Last Call

> Given that this email doesn't appear to have any concrete comments at
> all, just a statement of general unease with something (unstated)
> about the spec, I'm not sure what I or the group is supposed to do
> about this.
>
> ~TJ

To be honest, I don't know either. But the fact I still feel highly uncomfortable with the spec is not a good sign. There are too many things I think are wrong, and I'm pretty sure we should think back about the use cases we want to support and what's the best way to support them. My intuition is that this spec is the wrong solution to them. 

This may be totally personal, or not. This is what the group should maybe try to find out.



On that matter, did someone take some *realworld* stylesheets, css polyfills and webcomponents-scoped styles to see how the css-variables spec would make them easier? 

I'm under the impression the spec took some road and continued ahead as far as it could, but the end result looks far from satisfying to me. I'm pretty sure that we could shift the lines toward what preprocessors do could make sense and at least cover properly that use case, something even preprocessors couldn't do completely since they're not dynamic on the page they live in. 

I feel like the current draft isn't going to evolve anytime soon into something I could use for polyfilling and web components styling purposes, and a lot of complexity arise for trying to support these use cases as a backdoor. If this is just not going to work, maybe we should refocus our attention on what may end up working (pure variables and computated expressions), and eventually start something else along the lines of the web components & polyfilling scenarios at a later time. I recently 

It is just an idea though, what do you think?

Received on Tuesday, 3 September 2013 20:37:52 UTC