When setting the variables for my library’s typography styles, I noticed that my text sizing variables were not showing up for ‘Line height’ even tho I had ‘Text content’ number scoping settings toggled on.
I then realized they are only showing for ‘Line height’ if I have ‘Show in all supported properties’ selected. Is this because it’s planned to add semantic text content scoping in the near future? I would expect that all my variables that have ‘Text content’ toggled on will appear for Line height.
It’s a small detail, but now I have all my text variables visible for properties in which I may not want them like effects, stroke and opacity.
I’m encountering the same issue. Took me a bit to figure out because even with everything selected, without having “Show in all supported properties selected”, it would not appear. A very minor thing, but it does somewhat break scoping because now the text content specific variables are flooding other number variable selectors, like gap, width, etc.
Same, line height variables are only visible if ‘show in all supported properties’ is selected.
As a workaround, I’ve found that once I’ve applied to a text style I can go back and descope to text only and it’s still defined on the text style. This means they are the same as unpublished in terms of their visibility to designers, but as long as they stick to styles it’s not a problem as they are powering the styles. In theory once the ‘bug’ is fixed I will have no extra work as will all be saved with a text-only scope already, they will just become exposed.
I just came across the exact same problem today, google searched: ‘“text content” doesn’t include line height in Figma variables’ and found this thread. +1 to needing this fixed. Thanks!
Hey everyone, thanks for flagging this and your feedback!
I confirm that it is not supported at this moment. Our team is aware of it that variables with the ‘Text content’ scope are showing up for any typography values, and for now we’d recommend that you don’t scope variables intended for typography. They plan to add a specific scope within the next month, though I’m not able to share the exact date as it may change if any problems are found before then.
When it goes live you should see it announced on our Release Notes or Twitter / ‘X’.
Thanks for your patience in the meantime!
@Celine_Figma if there is a way to communicate to all Figma users that this is not working? This would save us a lot of time trying to figure out what is happening and trying to fix it.
Amazing! Thanks for the update @Celine_Figma . And thanks to the Figma design/dev teams working on this. Seems to be working great so far. This feature will make navigating variables so much simpler for end users!
