Component Overrides don't apply to variants

[Levi_Jones]

Anytime I use a variant with overrides applied the interactive component causes the variant to revert to its default state in the prototype.

I may be doing something wrong, but it feels like a bug.

[RichPeniche]

I have the exact same problem, @Levi_Jones.

I did an experiment where I removed the instance of a nesting component that contained the button which worked to get the different states of my buttons, but the content (icon + label) kept changing to the initial state, ignoring the overrides.

[Y_J_M_S]

Did any of you guys resolve this issue ? My main problem is with buttons and changing their CTAs

[matt_albert]

Any word on this? Basically I have a hover state button component but every instance reverts to the components default hover state color. How is this a bug?

[Jason_Coe]

Would be great to get this resolved. When I change a variant, i.e While hovering change button to hover variant it works well. The moment I go to my component library and make a subtle change, like the background colour, and publish I then go back to my main flow and accept the updates… at this point all my interactions have reset and I have to reapply the settings. I have done this so many times now that’s its making it a very longwinded exercise

[Goji_Labs]

I am having the same issue. I am creating an interactive sidebar, and my components have an icon and a title in them. The hover states work fine, but I also have an enabled state with an override that is not working. The enabled state will hold the changes to the copy, but not the icon that I want to change out. When clicking the enabled state will show my icon reverted to the default icon.

[Kojin_Journey]

Yes! I’m having the same issue and this a really serious bug! I can’t working with my library.

1. The first time update the variants component, all the changes instance in different design file will reset to default.

2. After first time reset, the variants instance will act as normal.

3. Only affect with the file using library, if within same file it won’t happen this bug.

Figma team please fix this soon as possible, cuz i cannot update anything cuz it will make all my file reset to default status.

[Ming]

I have the same problem，please fix this as soon as possible

[Jonathan_Slavuter]

+1 on this issue

[Martin_Hill]

I would love the functionality to be able to add hover states to varients in components… if they worked in prototype/presentation mode.

icons are reverting back to the original state in the library

I’m looking forward to seeing this one fixed

[Ian6]

Same issue! On hover Figma refuses to respect the color change.

[Aurelien_Marty]

Same issue too. It’s a real pain, since I can’t prototype interaction properly because of this bug. Please fix it!

[Jairo]

Guys!
Take a look at this topic!

Interactive component Hover bugs when changing the display Icon

Hello folks! This is a problem / Bug i find every now and then. But today it got to a really interesting point, and wanted to share with you to see if we can find out. Project: https://www.figma.com/file/Ux7CByq5QOEIZC96Lr52XV/Hover-Problem?node-id=0%3A1 Preview: Figma Background: I did the most basic hover interaction ever. I have an instance of an icon, wrapped inside an autolayout frame, then i created a new main component and it is where i usually apply the hover interactions. [image] …

Does the bug you are referring in this post have something to do with the one i am highlighting in my post?

In short:
From time to time i find a bug where i create a placeholder button and then i create multiple instances of it and change the icon of each instance.
The bug happens when after hover the icon color remains as hover.

In my topic i also provide a file where you can see the bug, but also a clone copy of the same button with the same hieriarchy on EVERYTHING, but the copy does not have this problem.

[Kenn]

My issue is not image related or anything. My issue is that if I turn off a hover state in my prototype instance, then I update any part of the component and re-publish…

Then it turns on the hover state again which I specifically told the instance that I do not want happening on that instance.

Really wish Figma had thought about UX when they built this. Frustrating that they do not seem to want to address this or see it as an issue sorry.

Any suggestions or workarounds that folks do?

So we just NOT do hover states in variants?

[Megan_Kuhn]

+1 this is a huge problem

[Niphat]

I still have this problem.

[Court_Kizer]

This is a huge and serious issue. It makes the entire idea of component libraries unusable. You have to go and rebuild the main component with the updated nested components which defeated the idea of components in the first place.

[Dave42]

I still have this problem

[Tara_Price2]

commenting again for attention

[N811]

Holy cow this is STILL happening!?

This bug needs to be a high priority fix and it has been YEARS!