Skip to main content
Magdalena_P
November 7, 2023
Solved

Major nested component bug

  • November 7, 2023
  • 17 replies
  • 1054 views

I have several components in my library that share the same problem.

When I change properties on an instance of the component, sometimes it resetts the text. Then I undo, and change the same property again, and now the text isn’t resetted anymore.

Since it only occurs randomly, and after undoing it works properly, it looks like a bug to me. But maybe someone elese had the same problem?

    This topic has been closed for replies.
    Best answer by Sanny

    Hi Everyone,

    I wanted to provide an update on this topic. After discussing with Figma’s support team, we’ve identified that the issue stems from the component creation process.

    Here’s the current workaround:

    • First, create the component.
    • Set your text properties.
    • Then, create the component variants.

    However, the downside is that if you add a text property afterward, you’ll need to recreate the component and all its variants from scratch.

    While this is a bit of a workaround, the Figma development team is aware of the issue and working on a more robust solution, as communicated by the support team.

    Cheers!

    17 replies

    Show previous replies
    Gayani_S
    Figmate
    Gayani_S
    Community Support
    August 15, 2024

    Hey @Walicki_Piotr, thank you for confirming this!

    I’ve just created a support ticket on your behalf. Your ticket number is #1094852, for reference. Please download Figma desktop app debug logs and share it with the team.

    Our support team usually takes up to 24 hours to reply back to emails - tends to be quicker than that in normal circumstances. However, please be aware that we are facing increased contact volume so there might be a delay.

    Appreciate your patience in the meantime!

    Sanny
    Sanny
    New Participant
    August 15, 2024

    Hey,

    Thank you for replying. I’m currently on Holiday, when I’m working again I will test it first thing.

    Cheers

    Gayani_S
    Figmate
    Gayani_S
    Community Support
    August 16, 2024

    Hey @Sanny, no worries! Enjoy your holiday and feel free to get back to me when you’re back.

    Thanks,
    Gayani

    Sanny
    Sanny
    New Participant
    September 2, 2024

    Hey @Gayani_S ,

    I’m back.

    I’ve investigated the issue, but none of the suggested solutions have resolved it.

    This bug is a major problem for our agency. We rely heavily on component libraries across all our projects to save time and maintain financial stability. Starting from scratch with every component isn’t feasible.

    Component-based systems are essential for designing digital products, and having to manually update each instance whenever a component changes is incredibly inefficient.

    We hope the product team prioritizes fixing this bug, as it’s directly impacting our profit margins in our industry.

    Cheers,
    Sanny

    ksn
    Figmate
    ksn
    Community Support
    September 3, 2024

    @Sanny - stepping in for @Gayani_S to assist. I did some digging and saw you actually wrote into support regarding this. One of our agents last sent you a response on 8/13 letting you know that they weren’t able to replicate the bug you reported, and requested a screen recording of the behavior you are seeing.

    Did you not receive this email? If so, let me know and I can get the conversation going again – hashing out this problem will need to be continued via email, since it may require more details about your design work (and we want to keep that private to yourself and support).

    Sanny
    Sanny
    New Participant
    September 4, 2024

    Hi,

    Thanks for stepping in to assist. I was on summer holiday, so I might have missed that email. However, I’m now back and in contact with the support team via email. We’ll continue the discussion there to resolve the issue.

    Thanks for the follow-up!

      Sanny
      SannyAnswer
      New Participant
      September 25, 2024

      Hi Everyone,

      I wanted to provide an update on this topic. After discussing with Figma’s support team, we’ve identified that the issue stems from the component creation process.

      Here’s the current workaround:

      • First, create the component.
      • Set your text properties.
      • Then, create the component variants.

      However, the downside is that if you add a text property afterward, you’ll need to recreate the component and all its variants from scratch.

      While this is a bit of a workaround, the Figma development team is aware of the issue and working on a more robust solution, as communicated by the support team.

      Cheers!

        Terms & ConditionsAccessibility statement