- From: François REMY <francois.remy.dev@outlook.com>
- Date: Mon, 1 Jul 2013 19:35:09 +0200
- To: "Tab Atkins Jr." <jackalmage@gmail.com>, "Jon Rimmer" <jon.rimmer@gmail.com>
- Cc: "Simon Sapin" <simon.sapin@exyr.org>, "www-style list" <www-style@w3.org>
> [Tab Atkins giving a more formal proposal] My concern is that this does not solve the problem at all, because what do you do if you want to nest some newly-generated at-rules? Do you have to parse again their content, recursively? If you goal is to end up parsing things in JavaScript at the end, you're better do it once, and have all your data JSON formatted and easy to load via your prollyfill thereafter. Putting things the browser cannot possibly understand in the CSS is probably not a very good idea. This is just my personal point of view, but I believe we should restrict CSS post-processing to things that just cannot be done in the pre-processing world. Creating SVG via CSS is really on the edge because you can generate your data url using a preprocessor, but that's not super-cool either.
Received on Monday, 1 July 2013 17:35:38 UTC