Skip to main content
Levi_Jones
Levi_Jones
New Member
May 2, 2021
Question

Component Overrides don't apply to variants

  • May 2, 2021
  • 23 replies
  • 3670 views

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.

    This topic has been closed for replies.

    23 replies

    Show previous replies
    Aurelien_Marty
    Aurelien_Marty
    May 10, 2022

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

    Jairo
    Jairo
    May 10, 2022

    Guys!
    Take a look at this topic!

    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
    July 25, 2023

    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
    Megan_Kuhn
    September 29, 2023

    +1 this is a huge problem

    Niphat
    Niphat
    March 4, 2024

    I still have this problem.

      Court_Kizer
      Court_Kizer
      New Participant
      April 8, 2024

      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
        Dave42
        May 2, 2024

        I still have this problem

        Tara_Price2
        Tara_Price2
        Active Member
        May 13, 2024

        commenting again for attention

        N811
        May 29, 2024

        Holy cow this is STILL happening!?

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

          Edward Blakeborough
          Edward Blakeborough
          New Member
          March 19, 2025

          So i have been reading through these feeds and I was wonder if it is the similar problem that i am having. If it is then this is something they need to really address… Here is a link to a video I created to try and explain my headache. I love that app but man this is brutal.

           

          https://drive.google.com/file/d/1pFF-E2NwxQYiC1AKpRqJVFfPy-TFH0ia/view?usp=drive_link

          Show more replies
          Terms & ConditionsAccessibility statement