Skip to main content

@Junko3 This issue is still persistent today.


Actually there’s 2 issues here, depending how the component is built:



  1. Firstly a nested component that uses slots loses any override when using variables, this is not the case when changing from UI

  2. For components that have nested components in the master pre-made, without using placeholders, it is not possible to use DIFFERENT variables if the variant property is the same. In my example the blue instance has a light and dark variant. The property name is “blueProp”. Because the blue instance appears twice in the green component, the “blueProp” also appears twice in the nested component panel.


See attached video for these 2 problems.


Master with pre-nested instances:



  • No problem while using UI



  • Same setup but I cannot use different variables for different nested instances




Master with placeholders / slots:



  • No problem while using UI



  • Using variables breaks / loose overrides




I can provide the file if needed. Test with Figma Beta freshly restarted and the normal Figma.

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.

Screenshot 2024-04-27 at 7.23.25 AM

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.

I’m using variables to control instances (of other components inside main components), binding them to text, boolean and variant properties, including “boolean variants”. Switching between two variants through a variable resets any text property they share: the connection to that string variable breaks, as if it was overwritten.

Variables that were applied to variant properties of nested instances don't show up in their parent component's instances. They’re lost and need to be reassigned, contrary to all other types of properties – be it boolean variables to control visibility or string variables to edit text boxes, those variables show up in their parent’s property panel and remain intact. Why the disparity? I’ve filed a ticket and I’m replying to this post as it seems to be related to mine. I hope this gets solved asap, it’s been very frustrating.

+1

Reply


Terms & ConditionsCookie settings