Thanks for the suggestions, Jens. I'll do some experiments and see what
happens.
On Sunday, August 21, 2016, Jens wrote:
>
> Unfortunately, using a separate TextResource isn't quite what I'm looking
>> for. I want the best of both worlds. :)
>>
>
> Hm looking at the syntax of EQCSS again, it see
> Unfortunately, using a separate TextResource isn't quite what I'm looking
> for. I want the best of both worlds. :)
>
Hm looking at the syntax of EQCSS again, it seems that you have to fork GWT
anyways, because even if GSS would allow @element you would still need to
obfuscate the selector
Yeah, that's what I meant by GSS. EQCSS looks like a very powerful and
useful concept - I hope it does become genuine CSS some day.
Unfortunately, using a separate TextResource isn't quite what I'm looking
for. I want the best of both worlds. :)
On Sunday, August 21, 2016, Jens wrote:
> Its mor
Its more like that Closure Stylesheets does not recognize @element. Given
that its not a CSS spec but just a syntax for the element queries JS
library Closure Stylesheet probably won't implement support for it.
For now your best bet is to use a TextResource and inject your EQCSS
manually using
I am interesting in using element queries (see http://elementqueries.com/)
within GSS resources. Of course, GSS doesn't recognize the @element rules
and emits an error.
Does anyone has any suggestions on how I might get this working?
Thanks!
--
You received this message because you are subsc
