Skip to main content
Ivica_Batinic1
Ivica_Batinic1
New Participant
September 22, 2026
Solved

Figma Dev Mode: Missing Token Values for Stroke Weight

Figma, could you please fix this ASAP? It’s frustrating that we can assign tokens to stroke weights, but they aren’t displayed in Dev Mode.

Also, where is this border-radius value coming from?

 

Celyn_L
Celyn_LSolution
Figmate
September 22, 2026

Hi ​@Ivica_Batinic1, Celyn from the Figma Community Support team here.

Thanks for flagging this and for including the screenshot. I understand that the variable assigned to the stroke weight isn’t appearing in Dev Mode, and that an unexpected border-radius value is being displayed.

I’ve opened a ticket on your behalf with our Technical Quality team so they can investigate further. Please check your email inbox for a message from me with your ticket number: #2145909.

Please reply directly to your ticket with a link to the impacted file, and invite support-share@figma.com with “Can View” access (this won’t impact your billing and will allow us to reproduce the issue and investigate further with Engineering).

The team will reach out with next steps and updates as soon as possible. Thanks for your patience while we look into this!

View in thread

1 reply

Celyn_L
Figmate
Celyn_LSolution
Figmate
September 22, 2026

Hi ​@Ivica_Batinic1, Celyn from the Figma Community Support team here.

Thanks for flagging this and for including the screenshot. I understand that the variable assigned to the stroke weight isn’t appearing in Dev Mode, and that an unexpected border-radius value is being displayed.

I’ve opened a ticket on your behalf with our Technical Quality team so they can investigate further. Please check your email inbox for a message from me with your ticket number: #2145909.

Please reply directly to your ticket with a link to the impacted file, and invite support-share@figma.com with “Can View” access (this won’t impact your billing and will allow us to reproduce the issue and investigate further with Engineering).

The team will reach out with next steps and updates as soon as possible. Thanks for your patience while we look into this!

Terms & ConditionsAccessibility statement