Text property changing text style

I have a similar issue.

I for example have a button component with primary, secondary, outline and ghost variants. The text of the button is bound to a text-property for easy editing. 

Now comes the bug: When I add an undeline on the ghost button text, all of a sudden all the other button text also has a underline. If I change text color on a hover state, all of a sudden all text changes color. I ran into this issue several times and only detaching the text-property solved it, which ment all the buttons in my design reset to the default button-text. 

Edit: I know realize that the button-text resetting to the default-text is also a bug. :(

Same. So annoying. Will need to detach my styles now until this is fixed.

Same problem on my side. So annoying, text properties are no longer usable as they stand.

Same here, hope this will be fixed soon!

Same here, @FigmaTeam do you know when this bug will be fixed?
 

Hey All, thanks for flagging this and apologies for the delayed reply! 

I passed this topic onto the team, and they confirmed that this is actually a bug related to multi-edit mode. This usually occurs when changing a property while the multi-edit-selected states have a mixed set of typography styles, causing it to incorrectly apply one of the typography styles to all the selected states.

As a temporary solution, make any of your text substring edits outside of multi-edit mode. Rest-assured, this is on the team’s radar for improvement in the future. 

I noticed this same exact issue with one of my components that has a Large and Small text size variant. I use the same Text Property regardless of the variant so that switching between Large and Small does not lose the copy I entered into the component. And that text field has Text Style applied (Base Medium for small text, Large Medium for large text) in the component. But if I link the text styles and then try linking the Text Property in a single variant, the text field gets overridden across ALL variants in my master component.

Just found that disconnecting the fill color all the way down to the hex code (for the desired variant you wish to change) and reconnecting it works. It’s not perfect but it works long enough for me to make the change I need and leave it. 

This bug really needs to get fixed asap. 

I think this error is tied to the Text Styles, and not to the multi-edit variant, or at least in my case it was. Or if the multi-edit variant has lingering effects after you use it, maybe that is also involved.

I have individual variables for each of the button sizes, for each of the typography fields (font family, font size, etc.). I realized I should just be using the same size as my Text Styles since they aligned so I went into my buttons and tied the button text to the relevant size body Text Style (small buttons got the small body Text Style, etc.). When I went to bold one of them it changed all of the variants to the same font settings as the variant I was on. If I was on a small button when I hit bold, everything turned small. If I was on a large button, everything turned large.

I went to disconnect the Text property of the component, bolded all of the fonts, and everything looked good. When I went to connect the Text property to the buttons again, the bolding went away and I was back to square one. Bolding one button’s text changed all variants again.

I went back to my individual typography variables, and had no issues, so I think it may be heavily tied to the Text Style, or at least in my case/testing.

I’m having the same issue and was not in multi-edit mode/have not used multi-edit recently.

I’m trying to update one variant within a component set to have text underlined. I have each text element within the component tied to a single style. When I override that variant (so overriding the style but remaining connected to it), it changes all of the variants.

This used to work correctly. A consumer of our design system just pointed out that its been changed in our library and no longer aligns with our guidelines. 

I wasn’t able to find a way to fix this, so we’re now having to add styles for links for each font weight, which adds unnecessary bloat to our libraries. 

Hey ​@heatherl 👋 Sorry to hear this is happening. Thanks for taking the time to flag this. If you have a moment,  you can share the bug report through our Support Hub or from within Figma by selecting the question mark icon  in the bottom-right corner of any page and selecting Contact support. This article includes some tips on what to include — What to share in a bug report to Figma Support. Let me know if run into any issues, I’m happy to help! – Jaycee

Dropping in to say that I am experiencing this as well. I’m working on a fulsome design system for a client. This isn’t looking good on me. 😕
No multi edit mode. But I did duplicate the first variant to make the second, third, etc. if this helps figure out the issue.

I’m still experiencing this issue. It’s causing a lot of disruption. Pretty much every single design system component ticket is being moved to a Blocked column.

I submitted a bug report like you’ve mentioned above. It was actually pretty difficult. Not an experience I thought I’d get from Figma. I had to nearly argue with an AI just to find the real bug report interface. It felt as if the community or us designers are not trustworthy enough to simply go to a bug report page. We have to jump through explanation hoops before we can do so...

I am pretty sure this issue (or at least my issue) is the text property tied the text layers. Breaking that connection seems to be a temp workaround, but you lose the text property. Reconnecting the text property brings back the issue.

I submitted a ticket (1911702 if you want to reference it). They were able to reproduce the bug, and replied with, “After checking with our engineering team, it appears that the problem you're facing is indeed related to a long-standing bug that our they are aware of. I am very sorry to let you know that at this time, unfortunately, we do not have an estimated timeline for a resolution.”

For what it is worth, the way my buttons are currently working is referencing the specific variables that compose the style, instead of the text style itself, and that seems to not throw any issues. I was just looking to simplify things. Detatching the text property works, but it wipes all of your button text tied to that component, so that is obviously not ideal.