Figma Support Forum

Styles no longer show full style name

Hello,

Yesterday color and text styles would always show as “Text color / Primary” etc in the UI. Now it only shows the last name, “Primary”. This means a selection could show many different colors and they are all named “Primary”. Tried restarting Figma, but it did not help. Is this a new feature? Is there a option somewhere to show the entire style name?
image
image-1

9 Likes

+1, Makes all existing stuff unreadable. Is this intended or temporary/bug?

3 Likes

+1 same happening for text styles. I used to be able to see “Body / left” and now i only get “Ag / left” not able to recognise the style until i open the dropdown. if this is not a bug is pretty annoying imo

3 Likes

Is this a step in the direction of design tokens? If so it would be great with a heads up before it was implemented.

I’ll look into changing my colours to design-tokens tomorrow if this is intended behaviour.

+1, very unhandy

1 Like

Yeah this is brutal for our design system — for Color Styles (since we relied on those buckets for theming), but especially for how we handle Text Styles. We organized the different weights of our body text styles by size and now the UI is unusable…

For example: rather than seeing “Text M / Regular”, now you only see “Regular”. So you need to open the picker to see what size you’re actually using. Feels like a regression and hoping it’s something that can be rolled back or at least an opt-in setting.

In general, would be amazing to have even just a few days heads up on changes like this, today is going to be brutal answering questions from our team and trying to figure out how/if to address.

4 Likes

+1 Requesting rollback. Devs have to perform multiple clicks to confirm the name of the color & style, not ideal.

6 Likes

Yes! Although I’m not sure about the thinking behind the decision, I would like this to be rolled back as it complicates a lot of categorization.

When selecting multiple objects and trying to use the mixed selection panel to change/update colors, the process becomes more tedious.

3 Likes

Exactly on the same boat!

Not sure if the previous way was the best either since it could be hard to read sometimes as wel but I believe something along these lines would be much better

6 Likes

Nice suggestion!

imagine if the changelogs of Figma actually included a full list of changes. Maybe one day.

1 Like

+1, We have the same issue with one of our files only.

1 Like

Had to read this topic to realize the change, but it’s not welcome! Except if that means design tokens will be better supported, it needs to be rolled back. A better visual management of styles hierarchy would be welcome (more room to display styles names, better visual separation of folders…).

And in general a heads-up before changes is a minimum (don’t get me started on the library-sharing changes that were quietly pushed recently).

1 Like

Following this thread. This issue is bugging the hell out of me.

1 Like

We noticed to and now we have to rename all the styles to make it usable again. I could understand that this could help in some cases. But not if you already used it the other way. For us it’s better to redo this change @Figma_Support

1 Like

In hindsight, it’s the same naming convention as the components (a component instance inserted in a file only displays the last level of the folder hierarchy). There’s some logic to it, and it can make things cleaner, but that means changing previous naming paradigms.

2 Likes

One more confirmation for the Fimga team. This change really confused our entire team and makes it really hard to work with shared text styles. Appreciated if you could explain if this is intended or just a mistake? It also seems impossible to currently change or remove a Text Style from the group it is in. :exploding_head:

1 Like

@Josh @Figma_Support anybody? Again, so hard to get in touch…

Hey everyone we’ll be reverting this which should go live on Monday. Apologies for the confusion here.

9 Likes

This is a general issue with Figma. We build stuff specifically within the system but then they make a fundamental change that totally breaks the previous one (and it just pops in without any heads up or anything). Dunno, I get that some of this is par for the course but so many instances where I invest tons of time getting things set up and then a few months later have to redo everything to match a change that didn’t take into consideration how much pain it would cause users. But anyways, yea upvote for this - we need a reliable way to both organize AND view styles.

2 Likes