Swap instance property of nested components issue

[Huy_Nguyen]

I run into this issue when swapping the instance property of a nested component

Here is the link to my demo file.

I find some designers having the same/similar issues as mine. Does the new component properties feature works with nested components? Doesn't seem so

[Bruno_Barros]

I have exactly the same issue here.

[Gerardo_Cid]

Same issue. All our Design system is based on nested components, we would love to see Components Properties working with Nested components too.

[Slava_Bronevitskiy]

I have reported this as a bug through their form and with lots of debugging, research and bug isolation effort managed to break through their 1st line of defence (support) to the engineering team.

Now waiting for the response from the engineers…

[Huy_Nguyen]

Thank you for your hard work

This is the number one issue preventing us from using the new property features on our Design system.

[mrrobertstuart]

Same issue here – we’re experiencing this issue when nesting an instance-swappable icon button in another component.

Issues arise when viewing it in a prototype as the icon is set to change when clicking to another page, but doesn’t change at all when viewing the prototype.

[Matt_Brogan]

Hey we’re experiencing this issue.
Please fix.

[Michael_Lockwood]

Before finding this post, I posted about this same issue as a “Share an idea” topic.

Component Properties should have the power to control nested Components

I was excited for the new Component Properties and how they might simplify my components, but I haven’t been able to make much use of it because most of my components involve nested components, which the Component Properties can’t control. For example: Suppose you have a Modal component, which has within it a Button component. You may want the Modal component to have a Component Property for the Button’s CTA text - but that’s not possible. It is possible to override the visibility and text with…

Upvote if you like. Maybe if we push this problem from both sides, as “bug fix” and “new feature,” it’s more likely to happen? If a duplicate “Share an idea” exists, I can delete mine.

[Slava_Bronevitskiy]

Got a response. In my case the lost overrides issue happened due to the difference in the colors of the icon components (or variants).

If the main icon components (or their variants) have different fill colors, Figma won’t transfer the color override when swapping their instances.

[Huy_Nguyen]

I’m still so obsessed with this that I made another bug report Icon of an nested component resets color after changing variant

[Georgios_K]

I have waste so much time because of this

[Celestine]

I solved it by giving the icon vectors all the same name. Example: first icon is a contact icon and named the component “contact”, and name of icon itself is “Icon”. Second icon, component name is “cancel”, name of icon itself is “Icon”. It works for me