Skip to main content
Question

Typography/Size Variables: Styles don't respect applied mode for variables


Adam_Gordon

When applying text styles that have associated variables attached the values presented do not respect the applied mode. For instance I have a title that has a mode for Mobile (20px), and a mode for TV (40px), when i open up the style, the default mode (in this case mobile) is displayed instead of the TV mode size.

I have also observed this within grid layouts when applied it shows the default mode (26 columns). When in reality it is actually 24 columns, if you then detach the style it shows the correct number.

And when detached you can see it shows the correct value

Seems this was a major oversight, as it makes applying size variables pretty time consuming, as I have to check if I’ve chosen the correct size by clicking and opening up the variable list.

In short it seems to default to the first default mode, instead of respecting the chosen mode. It also only seems to affect styles.

Anyone else found this to be an issue?

17 replies

Paul_Dierksheide

Yes!! Having the same issue and came here to see if others were experiencing it. The only workaround we’ve found so far is to just add a description to the text styles with the other mode values, but it’s definitely not great.


Adam_Gordon
  • Author
  • New Participant
  • 6 replies
  • May 8, 2024

Ahhh thank you, I didn’t think about using the description!

I’ll use this as a workaround for now but it’s definitely frustrating that the values do not ripple down correctly when the mode has been selected. It makes it extremely difficult for those consuming the system to really use it correctly.


Adam_Gordon
  • Author
  • New Participant
  • 6 replies
  • June 4, 2024

Hoping to bump this thread as it’s quite frustrating and feels like a pretty big oversight.


dvaliao
Figmate
  • Community Support
  • 4603 replies
  • June 10, 2024

Hey All, so sorry for the trouble and delayed reply!

This is already on our team’s radar for improvement. Right now, this is expected behavior. The styles picker does not reflect modes for typography variables. The team plans to implement changes to make this less confusing.


hummh
  • New Participant
  • 11 replies
  • September 17, 2024

Hello,

when creating font variables with modes (e.g. device mode for desktop, tablet and mobile) and applying those variables to font styles, the preview of the font size is wrong. It always shows the size defined in the default mode. However the used size in the frame is correct, but it is super distracting that Figma shows the wrong font size …

Anyone experiencing the same issue? Is this a know bug?

The attached file shows example for multi dimensional modes or single modes. The issue happens in both cases (our initial assumption was the multi dimensional modes).

Figma shows wrong font variable preview.fig (563.4 KB)

Cheers & Thx
Harald


hummh
  • New Participant
  • 11 replies
  • September 19, 2024

Hello,
i found an old post from June that addresses the same problem.

In the meantime I found out this problem is not just related to font styles. It is a problem in all styles (e.g. effects). The preview always shows the default variable mode value, but never the actually used one.


hummh
  • New Participant
  • 11 replies
  • September 19, 2024

Hello,

are there any updates on this? We are facing the same issue.
It is super misleading if the wrong values are shown to designers using a design system.

See also
https://forum.figma.com/t/font-style-using-variables-with-modes-shows-wrong-value-in-style-preview/87107/4

BR & Thx
Harald


Adam_Gordon
  • Author
  • New Participant
  • 6 replies
  • September 19, 2024

Hey Harald, I haven’t heard anything back yet but it still persistent in the older version of Figma (I haven’t got the new UI yet). I’ve been using the above method and including the values in the description to at least tide us over until there is a fix. I am hoping that it won’t be too much longer though.


hummh
  • New Participant
  • 11 replies
  • September 20, 2024

Hello,

it’s definitely NOT solved in the new UI.

Harald


Lea.P
  • New Participant
  • 14 replies
  • October 9, 2024

Hello.
We also had feedback from our design system community about this bug. It’s super irritating when you work with different devices or densities.
Please fix it soon!
Thanks


Meet_Shah
  • 2 replies
  • October 14, 2024

Hey team, when can we expect a solution to this? This is super important as I’m working on a bi-lingual interface and this is super important.


Nicolas_Prieto

Hey, running trough the same issue at the moment. Is there any update on this? cc @dvaliao


Infectedcell

Hey!
Any news regarding this issue? It is already 6 mnths passed but the problem still exists.
Is there any workaround at this moment from Figma team?


rvx
  • New Member
  • 2 replies
  • January 31, 2025

The issue still remains very much unsolved.

It’s been 8 months since it has been on the “team’s radar”. Seeing how variables and styles are an integral part of software, I’m really hoping to hear an update on this soon.

 

Cheers.


hummh
  • New Participant
  • 11 replies
  • February 7, 2025

Is there any update on this? 

I am wondering how Figma can say variables are out of beta (aka production ready), but at the same time important things are missing:

  • Wrong variable preview
  • No library swapping support

Why is the ticket marked as “solved”?


dvaliao
Figmate
  • Community Support
  • 4603 replies
  • February 7, 2025

Sorry for the confusion, ​@hummh

My reply was marked as the best answer since it’s the only one so far with direct buy in from our Typography team.

While I wish I had an actual update to share, this is not high priority on the team’s current pipeline. It is on the team’s radar to improve in the future, but there is no specific timeline we can share on when/if variable preview will be rebuilt to include modes for typography variables or library swapping support. 


Stephen_Howe

That’s what is wrong with Figma, while customers are paying a lot of money Figma focusses on all the wrong items it seems.  All of these things are base functionalities for design systems and instead of putting focus on a new UI, Figma should focus on those base functionalities again.  For example we have designers in our company which use our central design system but they keep seeing the values from the default mode instead of the selected one.  One of the reasons why designers need to invest time in plugins like tokens studio because Figma seems to forget what Figma was built for!!! Nowadays we need so much workarounds in Figma, design systems should be their core focus!  We don’t care how styles and variables where built and that it’s difficult to fix, just make base functionality work!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings