Switch variants in nested components bug

I also want to add that any nested instances and the parent instance with the same property name will have this issues. Red, Green and Blue are difference components.

@Federico_Fala Hi! I moved your comments to a new, seaprate topic, since it was older and not necessarily caused by the same issue (i understand it’s very similar).

I will consult the support team to see if they have feedback, suggestions, or if something seems buggy.

I am seeing this exact same issue. I have a component that changes orientation through a variant for responsive breakpoints. If I change the component manually in the UI all of the overrides are kept. If I use the variable it resets all of the overrides.

Hello, any update on this?

we need to use slots in a list component and a card component to make it flexible. Assigning variables to the text in the content component that will be inserted in the slot is reverting back to the original text values of the component when switching from english to arabic using the variable mode.

Following for updates! There seems to be no logical method to follow in setting up components and variable properties that ensures content overrides remain.

I see many responses suggesting layer naming to be consistent, but in most examples, people are designing their components with consistent layer names and still seeing content reset to default when switching variant – especially when nested inside another component. This is a huge bugbear in a design system.