Closed n3t closed 2 years ago
Mhm, I'd like to avoid this because with v3 I want to keep the configuration settings separated from the translation (as much as possible).
What about a "predictable" class instead of a custom one?
For example, if you wanted to stylize the "analytics" block category, I could dynamically set the category itself as a class for the current block (or as a custom attribute).
Sure, it would solve the issue for me also, thanks. Separating language and settings is also great improvement :)
Sorry, just realized that description-only blocks does not have an category defined... I need this mainly for additional description blocks, so solution with category will not work :(
Sorry, I'd like to avoid this. I'll leave the issue open for now
I thought about this more but couldn't come up with a solution which respects the:
I want to keep the configuration settings separated from the translation (as much as possible).
A "stupid" solution would be to just create an empty span
element with an id, class, or custom attribute, for each section. Then you could retrieve the block-parent of that span using .closest()
:
var block1 = document.getElementById("span1").closest(".c-bl");
Hi,
it would be nice to have option to specify custom CSS class for each block. something like
Also for dynamic systems, where configuration of cookie consent could change by PHP generator, also custom class for main container would be nice, something like
Thanks for consideration...