Skip to main content
Alex_Prime
New Participant
April 17, 2024

Typography variables feedback

  • April 17, 2024
  • 23 replies
  • 1755 views
  1. Let users set a variable value in %. It is useful for line-height (also for border radius 😈)
  2. Add typography related items to Number scoping

23 replies

Tom-H
April 17, 2024

First of all I want to emphasize that I am very happy with the newly released typography variables! Here’s just a couple of variable related improvements I think would help make working with them a bit easier.

1. Change column width in Variables overview: Currently it’s not possible to drag the columns to change the width, within the variables overview modal. This would be great to allow seeing full variable names as sometimes they are longer than the fixed width of the first column.
2. Scoping for typography variables: Now when I have a Number variable, I can’t scope to to only show when determining typography related values like a line height or font size.
3. Moving a set of variables into a different collection: I’ve currently placed the different levels of variables into 3 collections for the different levels (1. Primitives, 2. Semantic, 3. Component). I want to move them into the same collection so I only have to set one mode per page to apply the right mode (Brand A, Brand B). Now I have to do this per collection (twice, in my case), even though the values are the same (Brand A, Brand B). Alternative could be somehow combining modes with the same name.

Curious if any of these are upcoming/on the radar.

April 17, 2024

I agree about the scoping it needs to be a fast follow.

Larry_Reynolds3
New Member
April 17, 2024

+100 Was about to post the same feedback. It took me a bit to figure out that I needed to keep “Show all…” checked in order to use my type vars at all.

John_Peele1
April 18, 2024

The lack of proper scoping for Typography variables is a HUGE oversight. I don’t know how Variables can come out of beta with this feature lacking. Just doesn’t make any sense.

Please add scoping for Typography variables!!!

Also, we need percentage-based line-height variables. 🙏

Ales_Horvatek
April 19, 2024

Percentage based values ASAP. It would speed up the workflow, you could just set a couple of line height variables (eg. 100%, 120%, 150%, …) and apply them to various font sizes. Right now if you have multiple font sizes you need a pixel based line-height value for each size 😔

April 19, 2024

100% agree on the scoping here. I cant get line height variable to show unless its set to all. Ideally as a quick fix if Figma could at least get numerics tied to at least a width or gap scope so they aren’t showing up everywhere.

Reiterate though, this was a great release! Really appreciate the drive and approach on how to apply this down through modes to breakpoints, this shows some good thought and understanding the scenarios out there.

Alice11
April 19, 2024

Same feedback! Glad I found this thread 🙂

Alice11
April 19, 2024

Tried to add % as a string which also didn’t work because it’s a # field

John_Peele1
April 19, 2024

Oddly enough, there seems to be some kind of smart detection going on with line height variables solely based on the presence of the words “line” and/or “height” in the variable name. See screenshot showing line height variables “properly” scoped.

Jaime_Lamb
New Member
April 19, 2024

Another issue with variable support in text styles is paragraph spacing. You can bind paragraph spacing to a variable, but you have to turn on “Show in all supported properties” rather than just turning on “Text content” for the variable’s scope. I generally want to set the paragraph spacing to the same variable as the font size, but I don’t want to see those variables everywhere.