Here are some thoughts I had after reading through the slides and gist:
- I don't think I'd often use
*prop
. I don't keep track of which properties/values need vendor prefixes (or nonstandard code) to work with the browsers I'm targeting. I use Autoprefixer, which uses data from the Can I Use? database. - A command that generates JSON with keys representing the variable names used in a .gcss file would be handy.
- I feel like I missed the point of storing style variables in JSON. One benefit is "different site themes"--but most of my projects include a "_variables.scss" file that could be swapped out--oh, but that would require recompiling scss. I see. I think I get it now. Never mind!
First off, that divergence between browser syntax is unacceptably insane. They're the one making our lives harder. Shakes head.
But moreover, that kind of complexity is way beyond *, so if you need that, use autoprefixer. But keep in mind how big and complex that tool is, and how much weight that adds if you want to do that sort of thing in the browser. Your other option is to manually specify those things and avoid the big library, especially since those cases are (hopefully) pretty limited. :)
However,
*
used in the value portion is a placeholder for the prefix expanded in the property portion, so if you do:You get:
I do have a plan to eventually special-case some simple examples of this cross-browser divergence insanity, like (notice the "full-screen" vs "fullscreen"):