In pro 6.6.x I was able to use the following Twig in an element custom CSS:
$el {
padding: {{dc:p:setup.layout.content.padding}};
color: {{dc:p:setup.base-font-color}};
}
{% if p.setup.inline_links.custom == "1" %}
$el .x-text a,
$el p a {
color: {{dc:p:setup.inline_links.color.base}};
}
$el .x-text a:hover,
$el .x-text a:focus,
$el p a:hover,
$el p a:focus {
color: {{dc:p:setup.inline_links.color.alt}};
}
{% endif %}
And it was correctly outputting the CSS depending on the conditional from parameters.
However, updating to pro 6.7.2 (or pasting that code into a blank element in a fresh install) causes some issues:
The twig seems to break the processing of the CSS, and it ends up trying to put it in a css var, but also breaks a bunch of further css vars that want to be there, breaking a bunch of other params set up for the element.
Has Twig processing been removed from the custom CSS panel? It was great to have it there for more complex conditional styling options for complex components.
Cheers!