Skip to main content
Question

Variants do not resize after updating component library


Quentin_Saubadu

Well I’m wondering what is happening here because this is the first time I see this problem:

  • I changed the height of my “lg” buttons from 48px to 56px
  • I also changed the radius from 16 to 24px
  • I published my library and updated it on me design file

     

What is happening:

  • The radius updated on all buttons
  • The height of the buttons did not change

 

I’m wondering if I did something wrong or if this is a known bug?

 

Thank you

3 replies

Tom Reem
Figmate
  • Figmate
  • 62 replies
  • June 4, 2025

Hey ​@Quentin_Saubadu, thanks for flagging this and laying out the steps so clearly. It looks like you’ve done everything correctly. I see what you mean about the resizing behavior in the screenshots you’ve provided.

 

I tested this on some ‘call to action’ buttons in a library in one of my files using the Figma Desktop App (version 125.4.9) — very similar in style to what you have with auto layout added, and the height and radius updates worked as expected on my end. Are you still seeing the issue?

 

If so, a couple things to double-check:

  • Are you using the browser or desktop version of Figma Design? If it’s the desktop app, try reloading and making sure it’s fully up to date.
  • Any chance there are overrides on the instances in your design file that might be preventing updates?

 

Let me know what you find — happy to dig in further if it’s still acting up!


Quentin_Saubadu

Hello ​@Tom Reem 👋

I managed to “fix” the problem by creating a height variable in my system and applying it to the button. I shouldn’t have to do that tho, I’m wondering what’s happening.

I’m on the desktop App, my version was updated (I verified before sending the message). Now my app is updated from yesterday but the bug is still here.

Also there is no overrides on this instance, I double checked.

 


Tom Reem
Figmate
  • Figmate
  • 62 replies
  • June 4, 2025

Hey ​@Quentin_Saubadu — thanks for confirming.

 

Glad to hear you’ve found a solution that gets you to the intended result. 🎯 That said, we definitely want to understand what’s driving this behavior so we can get to the root of it. 💯

 

I’ve shared your post with someone on our engineering team, and they’re interested in taking a closer look at the specific file + library setup to better diagnose what’s going on.

 

For a deeper investigation, could you please reach out to our Support team and include:

  • a full-size screen recording showing the steps leading to the issue (if possible)
  • a link to the affected file and any related libraries
  • make sure support-share@figma.com has been granted edit access to the file.

 

They’ll be able to take it from there! And of course, feel free to keep us posted here — always happy to stay looped in. 🙏🏻


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings