Bug when switching variable modes in nested components

This is still broken when component instance is added to a frame it magically forgets some settings and/or fails to maintain its original interactions :(

Same issue. Nearly 2 years

Hi everyone, I wanted to weigh in on this thread.

Thank you for joining this discussion — we’ve continued to bring your experiences with this issue to our product team, and I checked in for the latest status. It’s still on our engineering team’s radar, but I don’t have a confirmed timeline for an update that I can share yet. I know this isn’t the news you were hoping for, and I understand how frustrating it can be to navigate an issue that’s been open this long.

Please know your reports and examples remain important in keeping this visible, and we’ll keep checking back for progress to share with you.

Thanks for the update ​@Tom Reem 

I think what I am experiencing is the same as others here except its manifesting in opposite ways. Hopefully my notes and supporting image assist.

1. Frame 8 contains an instance of the component “Button-Theme” seen below.
2. The frame has the “Dark” mode from Colours Theme - Primitive variable collection applied.
3. The frame’s fill is “2”
4. With Dark mode applied 2 should be near black, instead it is white. While not inherently clear in this image it is important to note that the button instance (@1.) is inheriting the Dark mode (a lighter blue and dark text).
5. Applying Dark mode to the component itself (also filled with 2) causes 2 to show the accurate fill colour. However, the variants don’t inherit the mode and still show the default “Light” colour scheme (white content on dark blue background).

Oh and just to be clear light and dark mode is left as auto on the component variants
 

 I mean i already lost the Hope at this moment on the bug be fixed

​@Tom Reem, I haven’t read the whole conversation, but I’d like to add an important point - this is not a problem of variables but nested components in another components. It happens even without variables. Let’s say you have a wrapper A component that contains an inner component B. When you change variant and text content of the inner component B, and then change variant of the wrapper component A (e.g., to mobile version of the component), the content of the inner component resets to default, dispite the fact that the component B itself switches correctly. This used to work perfectly before some (variables-related?) update 1 or 2 years ago.

I have been chasing a fix to the nested components / variables / text override issues and had this response which they confirm is a bug and they are trying to fix the issue - however it’s longstanding and there seems to be no resolution in sight at the moment: 

“Our engineering team has conducted a comprehensive investigation and confirmed that the problem you're facing is indeed related to a long-standing bug. I am very sorry to let you know that at this time, unfortunately, we do not have an estimated timeline for a resolution.”

Frustratingly, rather than confirming they have this bug publicly on their guidance pages or when you contact support, you have to go through a long winded support process before finding out ‘oh, yeah we know about that, sorry’.

I’m also having the same problem - it’s frustrating that Figma doesn’t have a fix for this yet. 

I’m wondering how you’re all bypassing the bug? Any advice to ensure that inputted content remains “sticky” if we change parent level settings? 

Theres not much you can do except build sub-optimal protoypes. I often avoid too much nesting now and I try not to mix variants and variables.

please fix, I’m having the same issue :(