Skip to main content
May 9, 2024
Question

When I change a component's variants, text property reverts to default

  • May 9, 2024
  • 15 replies
  • 1939 views

I’ve been designing data tables using components and variants.

My setup is as such: Cell component is nested in a Row component, Row component is nested in a Table Component. Cell component has a text property and 2 variants for mobile/desktop. Row component has 2 variants for mobile/desktop.

When I change the row component to the “desktop” variant, which also switches the Cell component to its “desktop” variant, the text property gets reset by to its default, and I have to key in all the Cell text again.

Is there any way to avoid this?

Thanks!

This topic has been closed for replies.

15 replies

Jarek_Marciniak1
New Participant
April 2, 2025

I’m having the same issue. I’ve got multiple text components as my base text state. They are nested in other master components. If I change the nested text component version in one of these master components, say from H2 to H3, all instances of all components gets a hard text reset. It makes the text component a dead feature really, and is prone to some deadly errors while maintaining a design system.

ryanfromverow
New Member
June 22, 2025

Having this same issue with text properties

Gayani_S
Figmate
Community Support
June 23, 2025

Hey everyone, I’d appreciate if you could share a screen recording via Loom or Google drive. This will be helpful to reproduce this on our end. 

Alternatively, you can reach out to the support team via this form and share a file link with them. Please add support-share@figma.com as an Editor to your file (this won’t affect your billing at all). 

Thanks in advance!

PBA
New Member
August 6, 2025

Hi all,

I had the same issue but I managed to solve it.

What worked for me (hopefully will work for you too!) is that I had to rename all the instances to match across variants.

In my case, I had a drop-down menu with 4 different entries. I wanted the entries to change color when hovered or clicked. However, their text would also change to “Pending”, since that’s the text from the component.

As mentioned above, only when all elements where named the same (e.g. all texts are called “text”, all icons are called “icon”), then it worked for me, and hovering on “approved” would change the background color without changing the text inside.

Best of luck with you project!

Ticiane
New Member
January 9, 2026

Hello,
I’m having the same issue.
I have a nested components, and all the text layers are the same in the component, but when I use the pressed state in the prototype, the text resets to the component text:
gif
I just opened figma and noticed this bug