Skip to main content
Jeffrey_Kroonstuiver
New Member
May 29, 2026
Question

Increasing amount of bugs

  • May 29, 2026
  • 24 replies
  • 428 views

Hi,

Over de last few weeks our team is experiencing more and more inconvenient and work impeding bugs in Figma. Over the last few days we’ve been struggling to find workarounds for instances for which the ‘Variants could not be loaded’. It’s really awkward and unreliable if we design something and random things cause the designs to change. To name some that really affect our collaboration with other teams:

  • Instances of components sometimes appear empty (this seems to be related to slots?).
  • Changing properties for components with slots no longer work if the content within the slots was edited.
  • Placement of layers seems ‘off’, until the layer is selected and automatically restores its placement.
  • Instances of components that are inserted (Shift + i) are completely empty and void of layers.
  • Copying main components from our spec files to our UI kit causes the variants to become duplicated within resulting in twice the number of variants and causing conflicts. (I’ve raised a support ticket for this.)
  • Opening or reloading a design file causes some layers to change from filling the height to hugging the height or vise versa. (This, again, can most often be fixed by selecting the layer.)
  • Inability to edit text layers until I reload a design file.
  • Crashes of plugins when used with layers in slots, most notably Contrast.

I assume that a lot of work is being done for the upcoming Config, but I’ve lost so much time over the last 2 days in trying to deal with these issues. I would really appreciate if Figma can prioritize fixing their bugs before introducing new features.

24 replies

Guilherme Rosado
New Member
August 26, 2026

@adamsmasher 

 

Since we’re in a bug spree 🐞, here’s another:


Changes made to nested component instances that contain pre-populated slots can unexpectedly propagate to the main component.

 

These edits should remain local instance overrides, but slot content or nested component changes can leak into the source component without an explicit "Push changes to main component" action.

 

This behavior makes nested slot-based components unsafe to reuse because editing one instance can unintentionally change every instance linked to the source component.

Here’s the repro: 

 

Edit

I’ve managed to find an workaround, but I think it’s still a valid bug report. Let me know if you need anything

 

adamsmasher
Figmate
Figmate
August 29, 2026

Thanks for flagging this, ​@Guilherme Rosado - and no worries about the bug spree, we appreciate flagging issues when you find them!

 

This definitely sounds like it’s working backwards of what you’d expect. I watched your video where you reproduced the issue, and decided to make a ticket for you with our Technical Quality team so they can investigate. When you get the email notification for that, can you reply and share file links with us at support-share@figma.com with Edit access? This won’t affect your billing. Thanks for your patience, and let me know if you have any other questions!

Guilherme Rosado
New Member
August 29, 2026

Thanks for flagging this, ​@Guilherme Rosado - and no worries about the bug spree, we appreciate flagging issues when you find them!

 

This definitely sounds like it’s working backwards of what you’d expect. I watched your video where you reproduced the issue, and decided to make a ticket for you with our Technical Quality team so they can investigate. When you get the email notification for that, can you reply and share file links with us at support-share@figma.com with Edit access? This won’t affect your billing. Thanks for your patience, and let me know if you have any other questions!

Sure thing! :)

Btw, you guys are doing an awesome job.

adamsmasher
Figmate
Figmate
August 29, 2026

Thanks for the kind words, ​@Guilherme Rosado! Have a great day. 😊