Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect Application of Resolved Values for Typography Styles with Variable References #3189

Open
UdayHyma opened this issue Oct 24, 2024 · 1 comment

Comments

@UdayHyma
Copy link
Collaborator

UdayHyma commented Oct 24, 2024

Describe the Bug
When using the "resolved values" option for typography, the expected behavior is that the actual font name and weight (raw values) should appear in the design. However, when typography styles use variable references (such as "Brand Font" and "tt_font_bold"), the output in the Figma design panel displays token names instead of resolved values, even though raw values are expected.

In addition, users have noted that this issue is reproducible under the following scenarios:

When "Apply to Selection" is enabled, the typography tokens do not apply as expected in synced typography size variables, causing the raw values to appear incorrectly in the right property panel.

Steps to Reproduce the Behavior
1.Create typography styles in the design tool using variable references for font and weight.
2.Apply the "resolved values" option to a selected text or element in Figma.
3.With "Apply to Selection" enabled, check the properties panel to see if the raw values appear as expected.

Expected Behavior
The "resolved values" option should consistently display the actual font name and weight rather than token names, even when "Apply to Selection" is enabled. Typography styles should sync and display properly in Figma’s property panel according to the set variable references.

@SamIam4Hyma
Copy link
Collaborator

@UdayHyma great job labelling this one!! 🫶 I'm going to add a new label for these apply token settings which were missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📥 Triage
Development

No branches or pull requests

4 participants