Satyajit Sahoo

For Numix, you already have a modified version. I would rather prefer to get it fixed in Xfwm rather than changing design decisions for Numix.

@lukasz1985 Yeah, fixing it in Xfwm will fix the issue for all themes, fixing in Numix only means an workaround.

@silvenon we cannot do that because then the following will not be correct: ```js const paragraph = css` font-size: 14px; `; const article = css` background-color: white; .${paragraph} { font-size:...

> I thought that it would be possible to detect `.${paragraph} {` vs `${paragraph};` and act accordingly It could be possible if we parse the CSS as it's constructed. But...

@ferdaber We did exactly the same previously. but it's not very useful because it's not possible to use interpolations etc. and it just becomes a fancier string interpolation. It's also...

> Can you elaborate why this method would make it impossible to use interpolations Because we can't support dynamic interpolations in the `css` tag, and will throw a syntax error...

I think `styled-components` could have been a nice solution to this problem, but there are several other CSS in JS libraries too. Which means that if developers start publishing code...

I don't think there's anything to disagree here. These are not opinions, but problems which prevent using CSS in JS library. ISTF is great, and I hope it'll solve most...

> Btw it'd be great to talk about how we can proceed with Sweetsour/ISTF. I'm planning to use it for React Native first to test out its constraints and practicality....

@eatsjobs need to wait for #227 for this