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

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.

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

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?

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.

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”?

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. 

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!

So ​@dvaliao how do we bring more attention to this issue? We’re using variable modes (driven by Token Studio) to create type styles (in addition to the modes setting spacing, border radius, etc), and having to explain to designers that what they see in the style menu in the right sidebar is not accurate seems to be a pretty big miss. If that’s also going to be true about spacing, border radius, padding, etc then the frustrations with the broader design team are only going to compound. 

Clearly there are a lot of folks frustrated by this; how do we help elevate this priority?

​@dvaliao My enterprise design system team is having this same issue and it has quickly become a blocker. Our executive reviews require accurate type and our engineers require accurate token references. We are having to detach type and manually override to display the correct styles even though the values are accurate.

This is a high-priority item for our team! How can we get this prioritized?

Hey All, thanks for your continued feedback! 

I’ve flagged this topic again to the team to advocate for its prioritization in the their future pipeline.