(I, as author, did not close the mentioned thread.)
So since there is currently no option to de-/activate the additional graphics/icon of a button at the moment, I had to layout two separate button components: with and without icon. Hm…
That ensures a lot of work again, because I have to use different button versions everywhere on the website again and cannot simply use a central master element via parameter change.
Maybe there is a tricky cool coding solution, but in my view as a designer without coding enthusiasm, the component principle is not yet optimal, since I have to create a relatively complex and extensive script, whose parameters, type classes and correct syntax I have to know and write correctly down out of my head or have to copy from the forum or an own archive. In my opinion it’s still too far away from “Define the basic look & feel for this element and choose/click your needs of open parameters for every child”…
For me it remains a feature request to offer another “non-coding mechanics” here: A component (“ancestor element”) would ideally be an element, in which I can simply “lock” certain options like colors, fonts, format, etc and determine options of the elements as “open parameters” for every child (e.g. URL, textlabel, open new tab etc.). Without JSON scripting, just like a “master element” that inherits its locked options to the childs.